Camms is pleased to bring you the Quarterly Product Release Notification 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 11th September 2021 and will be available in your Live instance on 25th September 2021.
1. APIs for Camms.Risk Audit module |
A new set of Camms.Risk Audit Outbound APIs are introduced to export audit recommendation details, hierarchy linkage details, and secondary responsible officer details.
Type | Name | Description |
GET | /api/v1/AuditBoard | Exports details of the secondary responsible officer of an audit record |
GET | /api/v1/AuditHierarchy | Exports hierarchy linkage details of an audit record |
GET | /api/v1/AuditRecommendationDetails | Exports data from the audit recommendation details page of the Camms.Risk Audit module |
2. APIs for Camms.Risk Survey module |
A new addition to the survey response API will be introduced to the existing Survey API library. This will allow you to retrieve response related information from a survey.
Type | Name | Description |
GET | /api/SurveyResponseDetail | This feature will let you export survey response data of a given survey. This API will provide the below information:
|
3. API for Position based responsibility transfer |
An existing/new position-based HR integration will let admin users transfer responsibilities from one position of code to another position code.
Type | Name | Description |
| POST | /api/v1/positionbasedstaffdelegation | Will let you transfer responsibilities from one position to another position via an API |
4. API based SCIM Integration |
System for Cross-domain Identity Management (SCIM), makes user data more secure and simplifies the user experience by automating the user identity lifecycle management process.
With SCIM, user identities can be created either directly in a tool like Okta or imported from external systems like HR software or Active Directory. This enables IT departments to automate the provisioning or deprovisioning process, while having a single system to manage permissions and groups. Since data is transferred automatically, the risk of errors are reduced.
IT departments no longer need to develop and constantly update custom integrations that connect company directories to various external tools and apps. Employees outside of an IT division can take advantage of the single sign-on (SSO) option to streamline their own workflows and reduce the need to reach out to IT for password resets.
Listed below is an example of setting up an SCIM for the Azure AD platform:
STEP 1: In the Azure Portal, click 'Enterprise applications' from the left panel.
Figure 4.1
STEP 2: Navigate to 'Create your own application'.
Figure 4.2
STEP 3: In the right-side panel, enter a name for the application and select the Non-gallery application option and click the 'Create' button.
Figure 4.3
STEP 4: After the application creation, navigate to the provisioning section and select 'Automatic' from the 'Provisioning Mode' dropdown.
Figure 4.4
STEP 5: Following the selection of automatic provision mode, you would need to enter admin credentials to setup the connection. The URL and Token details will be provided by the Camms.Connect Team.
Tenant URL
Secret Token
Click 'Test connection' and you will receive a success message as shown in Figure 4.6.
Figure 4.5
Figure 4.6
STEP 6: Under 'Mappings', click 'Provision Azure Active Directory User'. Apply the same settings shown in the figures below.
Figure 4.7
STEP 7: Add the below attribute mappings as shown in the figures below.
Figure 4.8
Figure 4.9
STEP 8: Add users to the app, which will automatically synchronise every 40 minutes.
Figure 4.10
Figure 4.11
STEP 9: If there is a necessity to sync a record immediately, it can be done via the 'Provision on demand' option. Navigate to 'Provisioning' and Click 'Provision on demand'.
Figure 4.12
