Feature Release Note | Camms.Risk Incident Management, October 2020

Owned by amani imtiyas
Last updated: Nov 15, 2022
5 min read

Camms is pleased to announce the October Feature Release for Camms.Risk Incident Management. 

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

List of release items:

1. Default zoom level for location maps

The default zoom level setting currently available for the Location Analysis area, has been extended to the location pop-up map within an incident; making it more convenient for users.

How to configure this?

  • Set the zoom level in Camms.Incident > Framework > Miscellaneous Settings and click Save.

Note: The zoom level can be set by increasing or decreasing the bar. The zoom level is represented as a scale for meters per pixels. 

Figure 1.1: Set zoom level under miscellaneous settings

How will it work?

  • The zoom level will apply to the Bing map pin drop within the following areas of the application: 

    Location field configured within the Incident object:

Note: In the location dropdown where a location is not selected, and ‘please select’ is the default placeholder text, you will be prompted to share your current location, and if agreed upon the map will zoom into your location. If the current location is blocked, then the map will zoom into the map of Australia.

  • Location Analysis tab within Incident Dashboards – The zoom would apply to the location’s longitude and latitude coordinates provided within Camms.Incident > Framework > Incident Settings > Miscellaneous Settings.

2. New dropdown list type which functions based on API calls

A new dropdown type has been introduced that can generate a suggestive list of values based on an API call. This enables a powerful capability to show any list of values in a dropdown, depending on specific conditions, with the options list being populated via an API. 

How to configure this?

Note: To utilise this feature, you will first need to have the API functionality enabled in Camms.Risk Incident, and a suitable API available. Please contact Camms if you are interested in exploring this option.

  • A new field type has been introduced as ‘API based dropdown’. This field type must be selected within the field configuration pop-up in Camms.Incident > Framework > Incident Settings > Object configuration. This field type will provide the ability to populate list values based on the response of an API call.

  • The field type can be assigned to a custom field within any object—both standard and custom objects.

  • A custom API notification trigger can be configured in Camms.Incident > Framework > Incident Settings > Notifications.

  • An API notification requires to be setup only for ‘Custom’ notification types. The Trigger Type requires to be ‘Custom triggers’.

    • API notifications can be setup for all incident types and for a specific object for which the field is configured, in order to receive a value from an API call. Therefore, for the purpose of this feature the ‘Object’ must be for which the dropdown is configured. 

    • The notification template has to be configured first as per the point below, for the notification method ‘API’. In the event there aren’t any notification templates created, the active tick box will remain disabled. 

    • API notifications can be triggered on ‘On Change’, ‘On Save’, and ‘Open’. For this feature, the trigger type must be ‘Open’. This is because the API call will trigger a request when clicked to open the dropdown to select a value.

    • The field for which the dropdown is configured requires to be selected from the ‘Fields’ dropdown.

    • Custom triggers can be setup for the API request and response. For this feature within the ‘Response Trigger Criteria Configurations’, the following syntax requires to be included for each API-based dropdown.

  • A custom API notification template requires to be configured for the API notification within Camms.Incident > Framework > Incident Settings > Notification Template.

  • A notification template requires to be configured for the API notification method, for ‘Custom’ notification types. 

  • The API body requires to be configured within the template. The API body consists of General API information, such as the request type and the API URL. For this feature, the request type would be ‘Get’. The API URL of your external application must be included.

  • The API body will further include a Parameters section, where the parameters required to be passed in the API can to be configured. The parameters for this feature would be the parent list field values, and/or other fields by which the list value requires to be filtered by.

  • The API response body requires to be configured to include the response result. For this feature, within the ‘Response Body’, the response should define the notation type that the response result must be received. The following syntax requires to be included for ALL API-based dropdowns:
    Success,object#data.<API response results need to refer relevant API documentation> 

  • Separate notification templates and notification triggers must be configured for each API-based dropdown.

How will it work? 

  • When you open an API dropdown to select a value, an API call will be triggered (based on the API notification configured), which will then populate a list of values into the dropdown. 

  • Dropdown values will be populated based on the selection of one or more parent dropdown value selection. This filtration will be developed into the API Get request. 

  • If the response of the API calls has no values, the dropdown will display ‘No data found’. 

Should you have any queries or require a bespoke API solution with regards to configuring this feature, please feel free to get in touch with Camms via email at support@cammsgroup.com.

Â