Camms is pleased to bring you the Quarterly Product Update Notification for the Camms Incident Mobile Application.
This quarter we've got exciting enhancements to improve your user experience within the system, which will be available in your Test environment on 08th October 2023 and will be available in your Live environment on 29th October 2023.
2. Displaying the Incident Code and Title
3. Ability to add Tasks to an Object
4. Restricting Biometric for Deactivated/ Deleted Users
1. Group Headers |
Group headers are user interface elements used to categorize and organize content within a larger section or page of an application. They are typically designed to be expandable and collapsible, allowing users to control the visibility of the content associated with each header. These group headers serve as visual aids to help users navigate and manage information effectively, especially in scenarios where there is a need to present a substantial amount of data in a structured way.
- Expandable and Collapsible Behavior
- User-Friendly Navigation
- Handling Complex Data Structures
- Space Optimization
- Visual Consistency
Figure 1
Figure 2
2. Displaying the Incident Code and Title |
Displaying the Incident Code and Title in a separate section consistently throughout a workflow or application interface is a design choice that can offer several benefits, including clarity, context, and user-friendly navigation.
By featuring the incident code and title prominently in a dedicated section, users have a constant reference point as they navigate through various objects within the workflow. This consistency aids in orientation and ensures that users always know which incident they are currently working on. The incident code and title serve as a clear and unambiguous identifier for the incident. It helps users distinguish between different incidents.
- Consistency Across the Workflow
- Clear Identification
Figure 3
Figure 4
3. Ability to add Tasks to an Object |
The ability to add tasks to an object, specifically in the context of an incident details area, is a valuable feature that enhances organization, productivity, and collaboration.
The Inclusion of a "Tasks" object within the incident details area integrates task management directly into the workflow. This allows users to seamlessly create, assign, track, and complete tasks related to the incident, all from a central location.
Figure 5
Figure 6
Figure 7
4. Restricting Biometric for Deactivated/ Deleted Users |
Restricting biometric for Deactivated or Deleted users is an important security measure that ensures only authorized individuals can use biometric authentication to access a system or application.
When a user is deactivated or deleted from the system, their access rights are revoked. This typically happens for various reasons, such as an employee leaving the organization, a breach of security policies, or any other scenario where their access should be terminated.
Restricting biometric access for deactivated or deleted users through session timeouts and biometric data revocation is a fundamental security practice. It helps protect sensitive systems and data from unauthorized access while ensuring that biometric access remains a secure authentication method for active and authorized users. Proper handling of biometric data, communication with users, and compliance with legal requirements are essential aspects of implementing such a system behavior.
- Behavior: session time out, biometrics will be revoked, and another user can enable biometrics.
Figure 8
Figure 9
