Welcome to the Known Issues page for the Q4 Feature Release for Camms.Risk Incident. Here, you will find a list of issues that we are currently aware of and working to resolve. Issues will be prioritised based on the Urgency and Impact to our customers. We are committed to addressing them as quickly as possible, with regular updates made to this page for your visibility. We appreciate your patience and understanding as we work to deliver the best possible solution for you. If you encounter any additional issues, please don't hesitate to report them to us through our Camms Support Email (support@cammsgroup.com).
ID | Description | Type | Status | Alternative SolutionComment |
1 | Conditionally shown field not visible in Review Object permission area when "Visible" is unticked in object configuration | S3 | Open | Will be fixed before the live release.
|
2 | The system keeps loading when a condition is applied to a group header in a custom Incident object in a custom workflow | S3 | Issue Fixing |
|
3 | When a condition is applied and satisfied to a hide field, both the field used for the condition and the field that the condition is applied to become hidden. | S3 | Issue Fixing |
|
4 | Dependency records are not captured in the dependency popup in field value configuration for already existing conditions in the field value configuration | S3 | Open | |
5 | Cancel button behavior is not functioning when the user clicks on the close icon and outside the conditional warning alert popup | S3 | Open | |
6 | On change behaviour is not working for Incident records for the already existing conditions in the field value configuration | S3 | Issue Fixing | |
7 | Duplicate records captured in the history popup when a condition is satisfied to show or hide a field from another object. | S3 | Open | |
8 | Unable to save uncheck and save visible setting for a conditional field from Field Configuration Details popup | S3 | Open |