...
This quarter we've got a number of exciting new features and enhancements to improve your user experience within the system, which was deployed to your Test environment on 20th March 2021 and will be deployed to your Live instance on 3rd April 2021.
1. Inheriting permissions from the parent object for an embedded documents object
This enhancement will enable the permission of the parent object to be inherited instead of depending on permissions for the full 'Document Object'.
...
This will then enable the documents object to be accessed via a ‘Documents’ button.
...
How does this work?
Prior to this feature enhancement, documents were able to be added/edited/deleted via the ‘Document’ button, only if you were given permission to the Document object in the workflow. Now, the Document object accessed via the ‘Documents’ button, will inherit the permission of the parent object (i.e. the object in which the Document object is configured in), as well as the Document object.
If you do not have permission to the Document object, the ‘Documents’ button will work within the parent object by inheriting the permission of the parent object.
If you have permission to both objects, the union of both permissions are considered and the higher permission will take effect.
Example 1: If the parent object (Incident Details), has add, edit, read-only permissions, and the Document object has only read-only permission, you will be able to add, edit documents via the parent object, based on the parent's object permission.
Example 2: If the parent object (Incident Details), has only read-only permission, and the Document object has add, edit, delete permissions, you will be able to add, edit, delete documents in the parent object, based on the document’s object permission.
Documents added via the ‘Documents’ button can be viewed within the document object, configured to that field and within the documents object, based on the permission. However, it will not be visible if the document object is configured to any other fields in other objects.
Example 3: The Document object is configured for the field ‘Incident Title’ in the Incident object, as well as for the field ‘Investigation Status’ in the Investigation object. Documents uploaded against the ‘Incident Title’ field cannot be seen within the document object for the ‘Investigation Status’ field. But documents uploaded for both fields can be visible in the Documents object.
...
| Info |
|---|
Important Note:
|
2. Tracking the history of changes to users, user roles, and notifications
This enhancement will let you track and display the history of changes in the Incident Settings pages for Users, User Roles, Standard Roles and Notification settings.
...
| Info |
|---|
Notes:
|
3. Removing the redundant incident my quick update menu item
The Incident My Quick Update menu item has been removed as it duplicates the elements and capabilities available in the My Quick Update page. You can now access all assigned items under the ‘My Quick Update’ menu.
...
| Info |
|---|
Note: If you have selected the ‘Incident Quick Update’ option for the above configuration, you will be directed to the ‘My Quick Update’ page on submitting an Incident record. |
...
4. Enhancements to the Incident Master Report
4.1 Updates to the report title of the report
The existing report title of the Incident Master Report has been changed to provide a clear definition of the report.
New Format: <Incident Code> Record Details
...
4.2 Depicting a hyphen for blank fields in the report
The Incident Master Report has been modified to depict a hyphen '-' instead of 'N/A' text, for fields with no data entered in the Camms.Risk Incident application.
...