Follow

AMP 2016 Q2 Release Notes

AMP 2016.6.0 Release Notes

 

Key Component/s Release Note
PD-3592 Reports Only System Administrator users were able to view the button to download reports. This issue was fixed and patched to production.
PD-3547 "File Management Security" New settings are now available to prevent file uploads of any kind in AMP. This applies both to files that are automatically uploaded via spiders and testing with toolbars and files that are manually uploaded. When enabled, all pages where files can be uploaded will have the file upload interface disabled. Note that this will prevent thumbnails from being added to the system. To enable this setting, contact AMP Support.
PD-3511 Reports When using the Alchemy toolbar for testing, the severity and status for each violation was not being displayed in the reports as expected. This issue was fixed and patched to production.
PD-3470 "Alchemy User Interface & Experience" Some of the filters in the Alchemy toolbars were not working correctly. This issue was fixed and patched to production.
PD-3407 "Patterns & Globals Reports User Interface & Experience" Pattern thumbnails were not showing up in the Violations Instances report. This issue was fixed and patched to production.
PD-3372 "Authentication Security" Customers can now enable Two-Factor Authentication for their AMP instances. When enabled, all users will be required to enter a passcode sent to them via email at the time of authentication, in addition to to their username and password. To enable this feature, please contact AMP support.
PD-3194 "Best Practices User Interface & Experience" The data table on the Best Practices tab in AMP was previously sorted by Best Practice name, by default. The default sort has been changed to Media Type.
PD-3102 "Accessibility Best Practices" Accessibility issues on the Best Practice details pages were resolved.
PD-2991 "Organization Administration Users & Roles" System administrators and organization administrators can now bulk upload new users to their organizations. The new "Bulk Upload Users" option is available in the Administration tab. Admins can upload a CSV with all users listed, along with their email address, full name, and licenses that should be enabled for them. These users will receive an email from the system to login and set their password.
PD-1907 "Authentication Security" All log data from AMP is now being saved, redundantly, to a location outside of AMP. This includes data about access attempts, actions within the system and other data that is already logged about system usage.
PD-1881 "Performance & Scalability Search" New indexing functionality has been implemented to improve the performance of searches, filtering and other functionality that allows users to find data in the system.

AMP 2016.5.0 Release Notes

 

Issue IDComponent(s)Release Note
PD-3415 Reports
Patterns
Thumbnails were not being displayed on the View Pattern screen. This issue was fixed and patched to production.
PD-3407 Reports
Patterns
Pattern thumbnails were not showing up in the Violations Instances report. This issue was fixed and patched to production.
PD-3387 Accessibility
Best Practices
The alternative text for the new severity indicators on Best Practices was updated to more easily indicate the severity scale to non-sighted users.
PD-3384 Security A secure caching policy has been enabled for AMP, so all content served over SSL will now have caching disabled.
PD-3383 Security Apache configurations were modified to protect sensitive user and session data in the Apache header response.
PD-3382 Security The TRACE method in the Apache server configuration can be used to launch cross-site scripting (XSS) attacks against web clients. This is enabled by default but is not necessary for AMP usage. The installation documents for AMP have been updated to include guidance on disabling the TRACE method in the Apache configuration.
PD-3381 Security Autocomplete has been disabled for the AMP password field for all browsers that support disabling of the autocomplete feature on form fields. Browsers that do NOT support disabling of autocomplete and therefore continue to have this functionality are: Internet Explorer versions 11 and higher, Firefox versions 30 or higher, and Chrome versions 34 or higher.
PD-3380 Security AMP currently uses persistent cookies which are kept alive for 2 weeks from the last AMP visit. Organizations now have an option to use session cookies rather than persistent cookies if their security policies require this.
PD-3370 Best Practices Some users were unexpectedly seeing Best Practices that were in an "In Review" state. This issue was fixed and patched so only system administrators can see this Best Practices, as expected.
PD-3369 Best Practices
UI/UX
The "Organization Standards Only" filter on Best Practices was not working as expected for some users. When selected all standards were being displayed, including those not enabled for the organization in the Organization Testing Control. This has been fixed.
PD-3366 UI/UX
Modules
Some of the filters on the Modules report were not working in Internet Explorer. This issue was fixed and patched to production.
PD-3356 Security Security issues identified during periodic PCI security scanning and penetration testing were resolved.
PD-3353 Modules
Reports
UI/UX
The Report Modules report was not displaying the Thumbnails column by default. This was modified to display the column by default, as expected, and this fix was patched to production.
PD-3339 Modules
Reports
UI/UX
Some of the combo boxes in the filter bar of the Report Modules report were not working properly in Internet Explorer 11. This issue was resolved and patched to production immediately.
PD-3338 Best Practices
Patterns
When severities were customized for an organization, the severity for patterns was not updating to display the customized severity. Rather the default severity was always displayed.
PD-3335 Licenses and Packaging
UI/UX
When a user's AMP license has expired, the user will now see a message letting them know their license is expired. Previously no message was displayed but the user was unable to perform some tasks they could typically perform
PD-3319 Reports
UI/UX
The "Severity" column in the Violations Instances report was not displaying the severity for each violation. This issue was fixed and patched to production.
PD-3311 Reports
Modules
The "Location" column in the Report Modules report was displaying the same value as the "Name" column. This data was being populated in the database identically when spidering a site or when testing with Alchemy. The logic for automatically saving this data has been changed so future spiders and testing with Alchemy will save the module URL in the "Location" column and the page title in the "Name" column and the reports displaying this data will reflect this change. Reports for previously run testing will continue to display the data that was saved at the time the test was run.
PD-3308 Accessibility
Best Practices
Accessibility improvements were made to the Best Practices details page to make the page more functional for assistive technology users.
PD-3307 Automated Testing The user agent used to emulate iPhone 6 when spidering a site was actually coming across as having emulated an iPad.
PD-3283 Best Practices
UI/UX
Instructional text was added to the form for customizing severity to make it more clear how the user could customize the severity scale for their organization.
PD-3251 Alchemy Alchemy was not recognizing elements with an ARIA role of "heading" as heading elements in the heading-related Best Practices. This has been fixed so not only elements marked up with heading tags but also elements marked up with tags having an ARIA role of "heading" will be recognized as header elements and tested as such.
PD-3206 AMP Toolbars Some users were getting an error message when opening the AMP Toolbar for Firefox. This issue was resolved and patched.
PD-3155 Use Cases
Accessibility
In the "Report Use Cases" area there was an issue with keyboard accessibility on some of the dialog boxes.
PD-3126 Automated Testing Support for Robot.txt files was added to AMP. If a robot.txt file exists, automated testing in AMP will no longer include any of the URLs listed in the robot.txt file.
PD-3125 Automated Testing During the automated testing process the AMP spider will now ignore any links on pages that include the nofollow meta tag.
PD-3102 Accessibility
Best Practices
Accessibility issues on the Best Practice details pages were resolved.
PD-3082 Authentication
Security
Per recommendations from third party security testing, the AMP authentication process has been adjusted to disable accounts after a certain number of consecutive failed login attempts.
PD-3039 Best Practices
Organization Administration
Organizations can now customize the severity scale for Best Practices in AMP and map the default severities in AMP to their customized severities. When this is done the severities displayed anywhere in AMP will use the customized severities for the organization instead of the default values. The values can be numerical (e.g. 1, 2, 3, 4) or alphanumeric (e.g. High, Medium, Low).
PD-2944 Manual Testing
UI/UX
When users marked manual testing as complete in the manual testing tree, the user was not given any confirmation that the testing was completed. Now when completing the testing, the user will be redirected to the modules list which will now indicate that the testing has been completed.
PD-2919 Projects
UI/UX
The breadcrumbs on project pages were linking to the incorrect pages for system administrator users only.

AMP 2016.4.0 Release Notes

SSB IDComponent(s)Detailed Release Note
PD-3077 Testing: Spiders Automated tests in AMP can now be set to emulate Internet Explorer or Chrome, in addition to the previously available browser emulation options.
PD-3054 Authentication SSB University When users selected the "University" tab in self-hosted instances of AMP, they were not logged in to University as expected.
PD-3039 Best Practices Organizations can now customize the severity scale for Best Practices in AMP and map the default severities in AMP to their customized severities. When this is done the severities displayed anywhere in AMP will use the customized severities for the organization instead of the default values. The values can be numerical (e.g. 1, 2, 3, 4) or alphanumeric (e.g. High, Medium, Low).
PD-3031 Best Practices User Experience Breadcrumbs on Best Practice test pages were updated to more clearly indicate the user's location in the system.
PD-2995 Best Practices User Experience The Best Practice detail pages were redesigned to more clearly organize data about the Best Practices and to more prominently identify the severity, noticeability and tractability ratings for the Best Practice. If severity is customized for the organization, the severity displayed on this page will be the customized score.
PD-2994 User Experience The filter bar that now appears on data pages, such as the Best Practices list or the Violations Instances report, can now be collapsed and expanded to free up more room for display of the data when the filters are not actively being used.
PD-2993 User Experience Best Practices Standards The Standards filter available on the Best Practices page and many of the violations reports now allows multi-select.
PD-2983 Best Practices Media Types A media type detail page has been added to the Best Practices area to provide users with more detailed information about accessibility considerations related to the media type.
PD-2979 Alchemy Reporting When testing with Alchemy, the browser used to test will be saved with the testing results in the AMP report.
PD-2966 Dashboards User Experience When a user removes all widgets from their dashboard a message will now be displayed to make it clear to the user why their dashboard is empty.
PD-2944 Testing: Manual User Experience When users marked manual testing as complete in the manual testing tree, the user was not given any confirmation that the testing was completed. Now when completing the testing, the user will be redirected to the modules list which will now indicate that the testing has been completed.
PD-2943 Reporting Users can now add a "module location" column to the Violations Instances report.
PD-2933 Alchemy Reporting When testing with Alchemy, a screenshot of each module tested with the toolbar will automatically be saved to the report.
PD-2929 Standards Best Practices User Experience The Standards filter that appears on the Best Practices list and other pages has been updated to allow users to view and filter by standards enabled for the organization only or all standards.
PD-2889 Best Practices User Experience Users can now customize the columns of data that appear on the Best Practices page, and they can download the filtered and customized list of Best Practices to an Excel report.
PD-2885 Best Practices Standards User Experience The display and filtering of Best Practices and Standards throughout the system has been improved to make it more clear which Standards are being evaluated by the organization.
PD-2880 Best Practices User Experience The widths of the columns on the newly-redesigned Best Practices table have been adjusted to give more room to the columns with the most data.
PD-2867 Reporting Performance & Scalability Performance improvements were made to the bulk actions functionality on various lists in the system.
PD-2864 Reporting User Experience The Modules report has been redesigned to include sorting, filtering, and customized display of data columns. The customized and filtered lists can also be downloaded to Excel.
PD-2855 Testing: General User Experience A broken link on the test creation wizard was fixed.
PD-2852 AMP for Mobile Reporting User Experience When selecting a report to save AMP for Mobile results users were previously able to select reports that did not have mobile Best Practices enabled for them. The reports are now limited only to those that are setup for mobile testing.
PD-1917 Alchemy User Experience When testing with Alchemy users were previously required to first select a report for testing results to be saved to. Furthermore, they were forced to select the report when navigating to every new page to be tested. Now Alchemy will automatically evaluate the domain being tested and will save to the last report used for testing on that domain. If no testing has been done on that domain, Alchemy will save to the users default report to ensure testing results are not lost. If the user has access to multiple organizations in AMP, the user will still be prompted to select a report so Alchemy tests against the appropriate set of standards and Best Practices.
PD-1913 Alchemy Testing Modes User Experience A new Page Structure testing mode has been added to Alchemy. This mode includes all automatic tests for the page structure media type, as well as the manual tests. The manual tests are now guided with testing steps and highlighting on the page that walk users through the testing in a more user-friendly way.
PD-1912 Best Practices User Experience The breadcrumbs on the Best Practices pages have been updated to more accurately reflect the user's location within this area of the system.

 

View the latest What's New article for more information on exciting new features.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Level Access Support
www.levelaccess.com | 800.889.9659
© 2005 - 2018 - Level Access All rights reserved.
Privacy | Security | Credits | License