Camms.Risk Incident Management | October 2023
- amani imtiyas
Camms is pleased to bring you the Quarterly Product Update Notification for the Camms.Risk Incident Management.
This quarter we've got exciting enhancements to improve your user experience within the system, which will be available in your Test environment on 08th October 2023 and will be available in your Live environment on 29th October 2023.
1. Introduction of Audit trail for Document and Linkage Objects |
|---|
An audit trail has now been introduced within the Documents and Linkage Objects of the Incident Workflows, allowing to maintain a track of the history of changes made to the records.
How does this work?
All users with permission to the Document or the Linkage Object will be able to view the Audit trail via the History button newly introduced within the Documents and Linkage Object.
Upon clicking the History button, an initial popup will be loaded with the basic information such as the Username, Date/ Time stamp and summary of the activities that have taken place.
Upon clicking the hyperlinks within the History Summary Popup, another popup will be displayed with further tabs named Summary, Current Representation and Previous Representation which will provide detailed information on the activities taking place within the Objects.
The overall functionality is similar to the audit trail feature within the rest of the objects.
2. Addition of a 'Getting Started' Icon on the Left-Hand side Quick Access Menu |
|---|
Getting Started, page will be introduced as a new option within the Left-Hand Side Menu, allowing users to navigate into this page easily.
This provides easy access to the page without consistently navigating through the Mega Menu > Workspace.
3. Introduction of a Searchable and Expandable Hierarchy Tree Filter in Registers |
|---|
Hierarchy filter within the Incident Registers will now be introduced as a searchable Expandable Tree type filter allowing users to select multiple nodes in one go.
How do you configure this?
The' HierarchyID' field should be configured as Searchable in Incident Settings > Register Configuration.
How does this work?
An expandable tree-type filter will be displayed upon clicking on the Hierarchy filter in the Incident Register. This will initially display the Standard and Custom Hierarchy types configured within the application, which, when further expanded, will display the relevant parent nodes and child nodes.
Users can now search for the required parent/ child nodes and select multiple nodes within different hierarchy types to easily filter out the required records within the register.
Note: We regret to inform you that the introduction of a Searchable and Expandable Hierarchy Tree Filter in Registers will not be included in the Quarter 3 Live Feature release. This decision is driven by our commitment to ensuring a seamless user experience. In light of this, we are actively working on an alternative solution, and you can expect this feature to be part of our upcoming Feature Release.
Thank you for your understanding and patience as we continue to enhance our platform.
4. Eliminating the need to set a due date on the action if the Status is configured as 'Ongoing' and 'Deferred' |
|---|
With this modification, users will be able to create or edit an Action without having to mandatorily fill in an End Date if the status of the action is ‘Ongoing’ or ‘Deferred.’
I.e., Despite the field ‘End Date’ being configured as a mandatory field, users will be allowed to leave the field blank for these two statuses.
The status ‘Ongoing’ means that the Action is required to be always continued and the status ‘Deferred’ means the Action is no longer required/ applicable. Therefore, the end date is no longer a mandatory field for the two statuses and users can continue to fill them if required.
5. Return Button Enhancements |
|---|
A series of improvements have been made to the functionality of the 'Return' button within Incident records.
When the ‘Return’ button is clicked in an Incident record, the user will be navigated to the incident register which has the same incident type connected in the register configuration.
If there are multiple registers with the same incident type, then the user will be returned to the register which has the same 'Description’ as the incident type. This will be done only if the incident type with the same 'Description’ is linked to the register to be returned to. In other cases, the user will be returned to the first register found with the incident type connected in the register configuration.
If a user opens an incident record from a specific incident register, upon clicking ‘Return,’ the user will be returned to the specific incident register from which the incident record was opened.
Records opened via My Quick Update and Dashboard will be opened in a new tab. Therefore, if the ‘Return’ button is clicked within that record, the user will be returned to the register connected to the type of record as per the above explained functionality.
If the ‘Return’ button is clicked from a Portal record, the user will be returned to the portal register if a portal register exists.