Camms is pleased to bring you the Quarterly Product Release Note for Camms.Risk Incident.
This quarter we've got a number of exciting new features and enhancements to improve your user experience within the system, which will be available in your Test environment on 11th March 2023 and will be available in your Live instance on 25th March 2023.
1. Incident Status color swap in the Incident Register
2. Improvements to the Add New button in the Linkage object.
3. Introducing Preview Information and a Submission Progress bar
4. A warning message to improve the submission process
5. Introducing push notifications
6. Improvements to the field-wise Action popup and Action grid in the Action object
7. Improvements to the Incident Settings page filters
1. Incident Status color swap in the Incident Register |
This modification will include a minor update to a previous release of last year, related to the status colors in the Incident Register. Now the 'Open' status will be depicted in light blue, and the 'Closed' status will be depicted in dark blue.
Figure 1: Incident status in register
2. Improvements to the Add New button in the Linkage object |
The 'Add New' button in the Linkage object and field wise links button, will be made consistent with the Document and Action objects. It will be placed at the center of the Linkage grid, when in an empty state, and at the top-right corner when there are records available within the grid.
Figure 2,1: Add New button alignment in Linkage Object at empty state
Figure 2,2: Add New button alignment in Linkage Object with records
3. Introducing Preview Information and a Submission Progress bar |
A new section will be introduced at the top of each Incident Record, which will include some critical information, along with a progress bar, which will help indicate the submission percentage completion of an Incident Record that is in a Draft state.
There are 3 main requirements covered within this modification as explained below.
Figure 3: Preview information at the top of Incident records
Introduction of a new Standard field type ‘Incident Submitted Date’
A new standard field type called ‘Incident Submitted Date’ will be introduced and it will be available for configuration within any preferred objects except in Document, Linkage, Task and Action Objects. By configuring this field type, users will be able to capture the Incident Submission date within the configured field in the object.
How do you configure this?
- This can be configured via Mega Menu > Framework > Incident Settings > Object Configuration > Select the required Object > Add a new field or select an existing field > Select standard field type as ‘Incident Submitted Date.’ The options ‘editable’, ‘Required in Save’ and ‘Required in Submit’ will be unticked and disabled within Object Configuration as this will be a Read only (Un-editable) field.
How does this work?
- The field configured with the new standard field type Incident Submitted Date will be visible in the specific object(s) that it has been configured in. This field will be auto populated with the submission date as soon as the record is submitted. This will be a Read-Only field and will not be editable. It will capture the very first Submission Date and will not capture the Resubmission Date.
- The field(s) configured with the new standard field type ‘Incident Submitted Date’ and the Incident Submitted Date field in the Incident Details bar, will not be updated with the Submitted Date and Time, when submitted if the Incident Record is not in a ‘Draft’ status. The Submission button configured within Open records, does not mean an Incident Submission, and is more like an object-wise submission. Field(s) with the new standard field type ‘Incident Submitted Date’ if configured in such a scenario, will be displayed as a blank and uneditable. And the Incident Submitted Date field in the Incident Details bar will be displayed as ‘N/A’, even after an object-wise submission is done.
If there are multiple fields Submission Date fields configured across the same workflow, the same submission date will be displayed in all those fields.
Note: If you currently have a custom date to facilitate a submission date within the Submit Object or any other object and would like to replace this with the new field Incident Submission Date Field type being released, please contact Camms via a support ticket and we can do a data transfer task in order to transfer any data from your current field to the new one. |
Introduction of an Incident Progress Details Bar
How does this work?
An Incident Details Bar will be introduced displaying the below critical details of the Incident record:
- Incident Type
- Incident Status
- Incident Reported Date
- Incident Submitted Date – This will be displayed only if it the field with the Incident Submitted Field type is made visible in the relevant object in Object Configuration.
Only the standard fields corresponding to Incident Type, Incident Status, Incident Reported Date, and field with field type Incident Submitted Date will be considered.
Label names of these fields will be similar to the label name given for the relevant standard fields by the user in the workflow (value fetched from the description of the field in object configuration).
Note: This Details bar will not be shown while adding a new incident. It will only be shown after the incident created. |
Introduction of an Incident Submission Progress Bar alongside the Incident Progress Details Bar
A Submission Progress bar will be introduced alongside the Incident Details progress bar. This will indicate to the users how far they have progressed in terms of filling the required details for the Incident draft creation and how much is left for the record to be complete and ready for submission.
How do you configure this?
- A new setting called ‘Show Submission Progress Bar when Incident is in Draft status’ will be introduced within Miscellaneous setting. The Submission Progress Bar will only be displayed within the Draft Incident creation page if the below conditions are met:
- The new setting ‘Show Submission Progress Bar when Incident is in Draft status’ has been configured via Mega Menu > Framework > Incident Settings > Miscellaneous Settings.
Note: This setting ‘Show Submission Progress Bar when Incident is in Draft status’ miscellaneous setting will only show as enabled and unticked if the setting ‘Save Incidents as Draft until submission’ is ticked. Otherwise, it will be unticked and disabled. - A ‘Submit’ button is configured via Mega menu > Framework> Incident Settings > Object Configuration > Select a specific object > ‘Enable Submit Button’ in at least one object of the specific workflow.
- The new setting ‘Show Submission Progress Bar when Incident is in Draft status’ has been configured via Mega Menu > Framework > Incident Settings > Miscellaneous Settings.
How does this work?
The logic for the Submission Progress Bar is explained with an example as per below:
Object 1 | Object 2 | Object 3 | Object 4 | |
Name of object | Incident Details | Investigation | Injury | Submission |
Contains a Submit button | No | No | No | Yes |
No. of 'Required in Submit' fields | 5 | 3 | 2 | - |
- As per the above, the Submission Object is the first object with the submit record button and is configured as the 4th object in the workflow.
- Since there are 4 objects including the submission, each object will contain a percentage of 100/4.
- Initially, the submission progress bar will be 0% and if all mandatory fields in an object is filled it will show as 25% (100/4)
- If mandatory fields (Fields configured as ‘Required in submit’ of all 4 tabs are filled, then submission progress will be 100%.
- If there is a new object added from a decision point for any field in the workflow, then the calculation logic of the submission progress bar will change accordingly, increasing the ‘Number of objects with at least one field with ‘Required in Submit’ and ‘Visible’ including the submission object’ till the very first object with the Submission Button.
Note: If the field triggering the decision point is not added as ‘Required in Submit’, then the additional objects will not be shown and thereby will not be included in the calculation. |
- When Submission Progress is 100%, a label will be shown as ‘Ready for Submission’ in Green next to the ‘Submit Record’ button.
- Objects that do not have any fields that have been configured as 'Required in Submit' are not considered for the Submission progress calculation.
- Document, Linkage, Task and Action Objects will be excluded from this calculation.
- The Submission Progress Bar will only be displayed when the record is at Draft Status. Once the Record is submitted and converted to ‘Open’ status, it will not be displayed.
An in-app Contextual Learning video is now available for this feature for public cloud customers.
Contact cammscollege@cammsgroup.com for further information.
4. A warning message to improve the submission process |
A new warning message will be introduced to alert users that the Draft Incident Record has not yet been submitted, when you try to navigate to a different page.
How does this work?
A new warning message will be introduced which will be displayed when users navigate away from the Incident creation page prior to submitting the record. This will help alert the users that the record has not yet been submitted. This message will only be displayed for Draft records when the draft functionality is enabled. This message will not be displayed for records at ‘Open’, ‘Closed’ or any other state.
Below listed are a few instances in which the warning message will be displayed when the user tries to navigate from the draft incident creation page:
- Return button within the draft incident record page.
- Left Hand Side Quick Access Menu icons.
- Mega Menu icons
- Home icon
- Support icon
- Profile icon
- Product Navigation icon
Figure 4: Warning message alerting users that the draft record has not yet been submitted
5. Introducing push notifications |
This new feature will let you configure and send push notifications to remind/notify a predefined set of users for defined actions. This will initially need to be enabled via an Internal Setting.
How do you configure this?
- Once the Internal Setting is enabled, a new setting named ‘Activate all active Push Triggers in Incident and Compliance’ will be available within Incident Miscellaneous Settings accessed via Mega menu > Framework > Incident Settings.
- Push Notification will also be added as an option within the dropdown of the setting ‘Notification Method’ accessed via- Mega menu > Framework > Incident Settings > Miscellaneous Settings.
- Once these configurations are enabled, the option ‘Push Notifications’ will be displayed next to the option ‘Email’ in ‘Notification Templates’. Upon selecting this tick box, users will be allowed to configure a Push Notification Body within a template. This will contain snippets that can be configured within the Push Notification Body.
- Once the template is configured for Push Notification, the required templates can be selected and configured within ‘Notification’ like email configurations.
How does this work?
Once the above configurations are in place, push notifications will be triggered as per the configured scenarios.
Note: This modification is applicable to Incident Mobile users only. Please refer the Releasee Note of Camms.Risk Incident Mobile Application for further details. |
6. Improvements to the field-wise Action popup and Action grid in the Action object |
Actions for the incident records can be created via the Action Object or via field wise Action popup in the current application. This modification will allow users to easily identify if the actions were created via the Action object or a specific field. Two new columns ‘Object Name’ and ‘Field Name’ will be introduced within the Action grid in the Action object to easily identify the field, which the action was created against.
How do you configure this?
- Field wise actions can be configured via Mega Menu > Framework > Incident Settings > Object Configuration > Select a specific object > Select a specific field name > select the tick box ‘Enable Action Creation.'
Figure 6.1: Configuration of field wise action creation via Object Configuration
- Two new fields called ‘Object name’ and ‘Field name’ will be introduced within the Action Register Configuration area. This can be accessed via Mega Menu > Framework > Incident Settings > Register Configuration > Action Object. These fields will be unticked for visibility by default. However, users will be able to configure them as ‘visible’ if required.
Figure 6.2: Introduction of two new fields within Action Register Configuration
How does this work?
- Users will be able to continue to create field wise actions as per the existing process. However, only the specific actions created via the field will be displayed within the field wise action popup going forward. It will no longer display the actions created via the other fields as before.
- Furthermore, two additional columns called ‘Object name’ and ‘Field name’ can now be configured within the Action grid in the Action Object and the Incident Action Register. Using these columns, users can easily identify if the actions were created via the Action object or a specific field.
Example:
Action created via | Detail displayed withing the object name column | Detail displayed within the field name column |
Action object | Action | - |
Incident Title field in the Incident object | Incident | Incident Title |
Figure 6.3: Two new columns within Action Object
7. Improvements to the Incident Settings page filters |
The filters within the Incident Settings pages accessed via Mega Menu > Framework > Incident Settings will be simplified to only have the ‘Contains’ search filter. This will allow users to easily filter the required details.
Note: This will only be applicable to the main settings and not for any additional grids within the settings. |
Figure 7: Incident settings filters
Additional Note: Click here to view a list of issues that we are currently aware of and working to resolve |
