Important Update: Community URLs redirect issues are partially resolved. Learn More. .

cancel
Showing results for 
Search instead for 
Did you mean: 
BenjaminBlinn
Archer Employee
Archer Employee

The RSA Archer User Experience (UX) team has been very busy over the last few months, listening to customer feedback 6.x user interface the and working to incorporate that feedback into our design plans. During our last UX Working Group meeting, we outlined the UX priorities which resulted in positive feedback and validated that we were moving in the right direction.

 

Based on our most recent Voice of the Customer survey, customer feedback on the challenges in using RSA Archer falls into the following three categories:

 

  1. extra time/clicks getting to my target page
  2. Navigational challenges
  3. Lack of customization 

 

With RSA Archer Release 6.3, we’ve continued our efforts to optimize the User Experience.

 

First, we are working to address the “extra time/clicks” and “navigation” feedback. In RSA Archer, users spend the bulk of their time on Record pages. We’ve heard customers comment on this issue: “In 5.x, we had Save and Apply buttons that gave us the flexibility to save the record and stay on the page, or save the record and close it automatically. However, in 6.x, we only have a single button – Save -- which saves the record and keeps the user on the page. To move away from the record, the mouse needs to be moved over to the Close button.” 

 

You spoke. We listened and delivered. In Release 6.3, we introduced the “Save and Close” button on the Record page (and in Manage Packaging). We plan to implement the “Save and Close” button ubiquitously across RSA Archer in future releases. 

 

Second, we’re addressing color customization within RSA Archer. In 5.x, the Admin had 200+ levers to pull to change the appearance of the User Interface from the background color of tabs to the shape of the buttons. In 6.x, we swung the pendulum in the opposite direction and tried to make customization easier by providing only a primary and secondary color option. 

 

Again, you spoke and we listened and delivered. In Release 6.3, we’ve  added some color customizations. One of the biggest issues customers had was difficulty seeing content on the screen, particularly on a Record page. In  Release 6.3, Admins can place a customized color border around the controls to make them easier to see. Release 6.3 also provides customization in the following areas: 

 

  • Background color of the Main Navigation menu 
  • Background color of the Footer, 
  • Change the color of the section text header, 
  • Change the background of the Administration Menu.

 

Finally, we heard our customers talk about challenges with the layout on the Record and Questionnaire pages in 6.x. In 5.x, the field name and field name controls were both left aligned, which made everything line up consistently. In 6.x, field names were moved to be right aligned, but the field name controls continued to be left aligned. Release 6.3 adds an option for “Field Name Alignment” under the Appearance Menu, providing 5.x or 6.x layout options.

 

The RSA Archer UX team will continue to listen and improves the user experience. We appreciate customer feedback and encourage our customers to join the User Experience (UX) Working Group meetings. 

 

RSA Archer Release 6.3 includes new use cases for Regulatory & Corporate Compliance Management, updates to existing Business Resiliency use cases and Public Sector Solutions use cases, and enhancements for usability and stability of the RSA Archer Platform. RSA Archer’s two newest use cases, RSA Archer Data Governance and RSA Archer Privacy Program Management, are designed to help support customer processes for data protection and addressing applicable privacy directives, such as GDPR. Updates to RSA Archer Business Resiliency use cases are designed to help improve organizations’ ability to manage disruptions and crises. Enhancements to the RSA Archer Platform include a system administration dashboard, bulk record operations, and direct to edit capabilities.

 

8 Comments