CAMMS is pleased to announce the April Feature Release for cammsincident.

This was released on 26th June 2020 and includes the following new features and enhancements to improve your user experience within the system. 

1. Improvements to Incident emails 

1.1 Emails based on type and category 

Administrators can now configure email notifications to be sent out for all triggers, based on the Incident Type and/or Category, under the Notifications area accessed via Framework>Incident Settings, you will find two new configurations appearing for any selection made from the ‘Trigger Criteria’ option as below, for the Notification type ‘Incident’.

This will namely be Type and Category which are 2 dependent controls. The functionality will be as below;

1. Type: This will be a multi-select field listing all types created from ‘Incident Type’ area, accessed via cammsrisk>Framework>Incident Settings area. This will not be selected by default which will work as ‘Show All’ scenario, where all types are considered for the trigger. Here, you will be able to select which types the notification should be triggered from.
   
   
2. Category: This will be a multi-select tree field, which will list all categories (both primary and underlying child categories) created from the ‘Category’ area, which can be accessed via cammsrisk>Framework>Incident Settings area. This will not be selected by default, which will work as ‘Select All’ scenario, where all categories are considered for the trigger. here, you will be able to select which categories the notification should be triggered from. This is dependent on the ‘Type’ field above which the categories listed will be shown and grouped, by the type with which it's linked to, as selected from the ‘Type ’field. Any categories which are not associated with a type will be listed under ‘Other’

• The logical relationship between the Type and Category selections will be an 'AND' logic, whereas the relationship between separate options selected in the same field will be an 'OR'. What this means is, for example, you have made configurations as seen below;
  
  
   Image 1.1 (b): Category selection 

This will mean that the trigger will send notifications out when a new incident is created of type ‘Incident’ AND category ‘Asset’.

If you have made configurations as below;

This will mean that the trigger will send notifications out when a new incident is created of type ‘Incident’ AND category is either ‘Asset’ OR ‘Hazard’

• For any trigger, if no selection is made, this will be considered as the ‘Select All’ scenario, where notifications will be triggered for any type and category. 
• This will be available for all trigger criteria for the notification type ‘Incident’. 

Notes:

• CAMMS will be implementing the same feature above for other notification types as well in the future as a part of the road map. Stay tuned for updates via Aha!

1.2 Emails on changes to category

Administrators can now configure email notifications to be sent out when the incident category is updated. 

• Under Notifications area, accessed via Framework>Incident Settings, for the notification type ‘Incident’, a new trigger criteria ‘Category Change’ is now introduced, which will be triggered for open records whenever a change is done to the values selected for the standard Incident Category field. Image 1.2 (a): New trigger  
  
  

• A new snippet to support the above trigger is also introduced to the Notification Template area, accessed via cammsrisk>Framework>Incident settings under the notification type ‘Incident’ as [PreviousIncidentCategory] which when used, will show the immediate previous category/s for the record, prior to the change. 

Important Note:

Minor usability improvements have been made to the notifications area in general as below; 

• Changes made to the standard terminology for 'Email Notifications' and 'Email Templates' area previously existed, which can be accessed via cammsrisk>Framework>Incident settings to read as Notifications and Notification Templates respectively. 
• Introducing an option to make a configured notification active as an Email notification, also with a similar ability to mark a template created as an Email template

1.3 Trigger emails based on action status changes

Administrators can now configure email notifications to be sent out for action, based on action statuses and changes to the status 

• Under Notifications area, which can be accessed via Framework>Incident Settings, for the notification type ‘Action’ a new trigger criteria is now introduced as ‘According to Action Status’ which when selected will give an option of selecting from the available action statuses.
  
  
• This will be available as a multi-select field listing all statuses for actions. Multiple values can be selected and set up from here. This would mean that a notification will be triggered for actions with the selected statuses in incident.

Image 1.3 (a): New Trigger for action statuses  

• You also have a new snippet to support the above trigger, in the Notification Template area which can be accessed via cammsrisk>Framework>Incident settings under the notification type ‘Action’ as [PreviousActionStatus]. This will show the immediate previous status of the action prior to the change. 

Image 1.3 (b): New Snippet   

1.4  Ability to send out consolidated notifications

Administrators can now configure email notifications to be sent out in a consolidated fashion in bulk for the below two triggers, which can be accessed via the Notifications area in cammsrisk>Framework>Incident Settings>Notification type ‘Action.’

1. Action Status Change 
2. According to Action Status 

• When the above triggers are selected, an additional tick box configuration ‘Send Consolidated emails’ will be available when enabled. Instead of individual emails, notifications will be sent out in bulk as one email per recipient at a pre-defined time.  

 Image 1.4 (a): New configuration

For example, if the ‘Action Status Change’ trigger is set to be sent consolidated for the action responsible officer, and five actions had statuses updated today, instead of five separate emails, a single email will be sent to the responsible officer with details of all five, at a pre-defined time in the day.

• A new setting is introduced to the Miscellaneous settings area, accessed via cammsrisk>Framework>Incident Settings area titled ‘Time for Bulk Emails in Incident’. Now you have the option of setting the time which all notifications to be sent in bulk will be sent. This will be set to 00:00 by default. Emails are generally received within 1 hour of the set time.
  
  Note: The time considered here will be as per the timezone for the server and not your current system time, as such, configuration will need to be done as per the timezone pertaining to the region the servers are hosted. Please reach out to CAMMS Support should you need our assistance in setting this up.

• We have introduced a new snippet to support the above feature in the Notification Template area, accessed via cammsrisk>Framework>Incident settings under the notification type ‘Action’ as [ActionList] which when used will show a list with all actions being notified on. As the consolidated notifications combine several notifications together, we recommend only using the above snippet, when using this feature. 

• The [ActionList] snippet, when used in the template used in a consolidated notification, will show a table with all records triggered by the notification, with the below fields as columns. The actions shown within the table, will be sorted by the ‘Overdue Days’ column from high to low 

1. Title -  The title of the record with which the action is linked with. For incident actions this will be the incident title. 
2. Action Name – Name of the action. 
3. Previous Action Status – The status before the immediate last status change.
4. Status – Current action status. 
5. Percent Completed – Action completed percentage. 
6. Overdue Days – Number of days by which the action is overdue. This will follow the below logic in determining the number of days.

• Actions with statuses ‘Completed’, ‘Deferred’   and/or ‘Ongoing’ – this will be zero
• Others – the number of days by which the ‘End date’ for the action has passed the current system date

Note:

CAMMS will be continuously working towards improving and extending the feature to other notification types and triggers as a part of the road map. Stay tuned for the updates through Aha!

2. Hide tabs for which users don't have view permissions

• As part of our continuous improvements to usability and security within cammsincident, we have enhanced how the user permissions, which can be accessed via cammsrisk>Framework>Incident Settings>User Roles, work. 
• Previously, users for whom a workflow-based role was assigned, if they didn't have any permissions for a particular tab (i.e. not even a ‘Read Only’ permission) the user would still able to see the name of the tab, which when clicked would notify them that did not have access to view that tab;

This has been improved so if an assigned user has no view permissions to a tab/object, the object will not be visible at all for that user. Permission must be given in the assigned user roles, for any user to see a tab/object, even if it's ‘Read Only’ or ‘Edit.  

Image 2 (b): ‘View’ permissions are not given for the ‘Quality Control’ object

Note: 

This change is applicable to all new and previous data available in the system, therefore post release, if any tabs shown to you, that you didn’t have permission to view when clicked, will now be completely hidden to you unless a view or edit permission is given.