Feature Release Note | Camms.Connect, November 2020
- amani imtiyas (Unlicensed)
Camms is pleased to announce the November Feature Release for Camms.Connect.
This was released on 14th November 2020 and includes the following new features and enhancements to improve your user experience within the system.
1. Extending APIs for Project Outbound Connectors |
The below Project Outbound Connectors are new additions to our existing Project API connector Library.
Type | Name | Description |
|---|---|---|
GET | /api/v1/Assessments | Gets a set of common fields from the Assessment Object for all Projects or a specific Project and Object. |
GET | /api/v1/Assessmentdetails | Gets all (standard and custom) data fields from the Assessment Object for all Projects or a specific Project and Object. |
2. Extending APIs for Risk Outbound Connectors |
The below Risk Outbound Connectors are new additions to our existing Risk API connector Library.
Type | Name | Description |
|---|---|---|
GET | /api/v1/RiskAction | Gets a set of common data fields for all Risk actions available in the database or for a specific Risk Code. |
GET | /api/v1/RiskCategory | Gets a set of common data fields for all Risk categories available in the database or for a specific Risk Code. |
GET | /api/v1/RiskControl | Gets a set of common data fields for all Risk Controls available in the database or for a specific Risk Code. |
GET | /api/v1/RiskTreatment | Gets a set of common data fields for all Risk Treatments available in the database or for a specific Risk Code. |
3. Extending the Incident API Library with Inbound Connectors |
These APIs enable to insert data to our Camms.Risk Incident module. These Incident inbound connectors will be additions to our existing Incident API connector Library.
Type | Name | Description |
|---|---|---|
POST | api/v1/IncidentObjectDetail | Create an incident by adding data for all mandatory configured fields in the incident details object of Camms.Incident. |
POST | api/v1/IncidentCustomObjectDetail | Insert values for fields configured in the custom object of the Camms.incident workflow. |
4. Action and Task Outbound Connectors |
These APIs enable to read Action and Task data from Camms.Strategy. The below table shows a list of connectors which lets you export data.
Type | Name | Description |
|---|---|---|
GET | api/v1/Action | Gets all standard field data from Strategy Action for a specific Action or all Actions. |
GET | api/v1/ActionTarget | Gets all periods and target information for a specific Action or all Actions. |
GET | api/v1/ActionFilter | Gets all Action filter information for a specific Action or all Actions. |
GET | api/v1/ActionTask | Gets all standard field data from the Task area for a specific Action Task or all Action Tasks. |
GET | api/v1/ActionTask/TaskResponsibleOfficers | Gets responsible officer information for a specific Action Task or all Action Tasks. |
5. Additional features for the existing Incident Outbound API |
Additional filtering options are introduced to the api/v1/IncidentList and api/v1/IncidentDetails Outbound APIs.
Filter by Incident Status – Open, Closed Draft
Filter by Start date (Incident reported date), End date
Included a Unique ID/ Import key for org units and staff fields in the Incident API.
Linkage path – This will show the navigation from its root node to the linked node.
|
E.g. "linkedItemPath": "Root Node > Node 1_Level1 > Node2_level2 > Node3_Level3"
Included a linked Incident ID and Incident code details for /api/v1/ActionList and /api/v1/IncidentActionDetails Outbound APIs.
/api/v1/ActionList
|
/api/v1/IncidentActionDetails
|
