Camms is pleased to bring you the Quarterly Product Release Note for Camms.Connect.

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 3rd December 2022 and will be available in your Live instance on 17th December 2022.


List of items

1. APIs for Camms.Risk Compliance Solution

2. APIs for Camms.Risk Compliance solution

3. APIs for Camms.Risk Controls Management Solution

4. APIs for Camms.Risk Audit Solution

5. Introducing the Slack Connector


1. APIs for Camms.Risk Compliance Solution

You can now retrieve data related to Authority Document details, Linkages, and Standard and Custom Objects using the below APIs.

Type

Name

Description

GET

/api/v1/AuthorityDocumentDetail

This API will let you export Authority Document details from the Camms.Risk Compliance product.

GET

/api/v1/AuthorityDocumentLinkageList

This API will let you export Authority Document Linkages such as Project, Risk, Hierarchy, Obligation, Authority Document, Policy, Incident, and Controls.

GET

/api/v1/AuthorityDocument

This API will let you export a set of frequently used data fields related to Authority Document details from the Camms.Risk Compliance product.

GET

/api/v1/AuthorityDocumentObjectDetail

This API will let you export Standard and Custom Object data from the Camms.Risk Compliance product.


2. APIs for Camms.Risk Compliance solution

You can now retrieve data related to Policy details and Linkages using the below APIs.

Type

Name

Description

GET

/api/v1/Policy

This API will let you export a set of frequently used data fields related to Policy details from the Camms.Risk Compliance product.

GET

/api/v1/PolicyLinkageList

This API will let you export Policy Linkages such as Project, Risk, Hierarchy, Obligation, Authority Document, Policy, Incident, and Controls.


3. APIs for Camms.Risk Controls Management Solution

You can now retrieve data related to Control details and Linkages using the below APIs.

Type

Name

Description

GET

/api/v1/ControlDetails

This API will let you retrieve data related to Control details from the Camms.Risk Controls Management product.

GET

/api/v1/ControlFieldInfo

This API will let you retrieve data related to Control field configurations from the Camms.Risk Controls Management product.

GET

/api/v1/ControlLinkageList

This API will let you export Control Linkages such as Project, Risk, Hierarchy, Obligation, Authority Document, Policy, Incident, and Controls.


4. APIs for Camms.Risk Audit Solution

You can now retrieve data related to Audit linkages using the below APIs.

Type

Name

Description

GET

/api/v1/AuditLinkageList

This API will let you export Audit Linkages such as Risk and Controls from the Camms.Risk Audit product 


5. Introducing the Slack Connector

You now have the capability to integrate your organisation's Slack messaging platform with Camms using our latest out-of-the-box Slack connector. This will provide you the capability to replicate notifications generated through our Camms Product Suit (Project, Incident, Risk, Audit, Strategy) as an instant message to a Slack bot application configured in your organisation's Slack messaging platform.

Figure 5.1: How notifications from Camms are displayed in the Slack bot application

Figure 5.2: An extended view of the notification received in Slack by Camms

You will require to create a Slack bot application inside your team's or organisation's Slack messaging platform and send the Slack API token to Camms, to configure the integration between Camms and the Slack messaging platform.

Listed below are the steps taken to configure the Slack Connector for your environment.

  • STEP 01 : Create the Slack bot application in your Slack messaging platform and share the API token with Camms.

Figure 5.3 : API token of the Slack bot app to be shared with Camms

  • STEP 02 : Copy the member ID available for each staff member and update the 'Slack ID' field available in the staff details page.

Figure 5.4: Slack member ID

Figure 5.5: Slack ID field in the staff details page