Usability improvements for the Web Admin Suite
The following usability improvements for the Web Admin Suite have been made.
Option to copy script name to clipboard (#649960)
The icon Copy name has been added to the table on the Scripts page to allow copying the name of a script to the clipboard.
This functionality is only supported in environments using HTTPS or on localhost.
Consistent button styling (#657507)
The styling of the primary buttons to save changes and update the respective entities has been adjusted. These buttons now have a blue text and border, and a white background. This enhances user experience by aligning the button colors with the buttons' functions, providing a clear visual distinction between different types of actions:
- Blue with border and background: creation actions on the main page, such as adding a new entity
- Blue with border: standard submit actions, such as saving changes
- Red with border: potentially dangerous operations, such as deletions or discarding changes
- Black without border: standard cancel actions, such as cancelling edits
Handling of list and table fields improved (#661210)
The display of child fields of fields of the type List and Columns has been improved. Child fields are now displayed below their parent fields with an indention to visually indicate their relationship to the parent field. Therefore, the user can see at a glance which fields belong together.
On update, the fields are automatically reordered accordingly.
This structure is also kept when ordering the fields manually using drag-and-drop or the arrow buttons:
- Moving a parent field will change the position of all its child fields as well.
- Child fields can only be moved within the set of child fields which belong to the same parent.
The order in the Web Client can be overwritten by the Position setting.
Search by single case ID (#663046)
The Case administration page has been enhanced to bypass the index and search directly on the database when looking for a single case by its ID, i.e. when the only search criterion is Single ID. This allows the administrator to find and delete broken cases which could not be indexed.
Javadoc added to Troubleshooting page (#663181)
The Javadoc which holds the information about the ConSol CM API is now available from the Troubleshooting page. It can be accessed by clicking the respective link in the Further information panel. This enhancement provides users with easy access to detailed API documentation, facilitating more efficient scripting.
Integrations script renamed to "Webhook" (#663741)
The script type previously known as Integration has been renamed to Webhook to make its purpose transparent.
Client configuration page adjusted (#664179)
The possibility to select a template for a CM/Track configuration has been removed from the New client configuration dialog of the Client configurations page because such configurations should not be created there anymore:
- CM/Track V2 has been removed, see End of support for CM/Track V2 (#663261).
- CM/Track V3 configurations should be created on the Portal configurations page.
The New configuration button remains available to allow the users to create configurations for custom REST clients.
This change does not affect the display of existing configurations.
Enhanced display of JVM RAM consumption (#664460)
The dashboard has been enhanced with the new tile JVM Process RAM which shows the RAM used by the JVM process. This includes the full memory footprint of the Java process, including the Metaspace and the JVM itself. The previously available tile JVM RAM has been renamed to JVM Heap RAM to better convey its meaning, which is the RAM consumption of the application. This aligns the values shown on the dashboard with the values provided by the operating system.
Deprecated methods removed from autocomplete script template (#664670)
The template which is inserted automatically when creating a new script of the type Text autocomplete has been enhanced. The deprecated methods onEditDisplayEntered have been removed from the template because they are not needed for new autocomplete fields, which have the field type Autocomplete.