- Case Manager i56 Release Notes
- What's New
- Known Issues
- Issues Fixed in Case Manager i56.5 (General Availability)
- Issues Fixed in Case Manager i56.6
- Issues Fixed in Case Manager i56.7
- Issues Fixed in Case Manager i56.8
- Issues Fixed in Case Manager i56.9
- Issues Fixed in Case Manager i56.10
- Issues Fixed in Case Manager i56.11
- Issues Fixed in Case Manager i56.12
- Get Started with Case Manager
- Configure Case Manager Settings
- Investigate a Security Incident
- Manually Create an Incident
- Edit an Incident
- Delete an Incident
- Manually Assign an Incident to a Queue, Assignee, Priority, or Status
- Manually Add an Entity
- Manually Add an Artifact
- Delete an Entity or Artifact
- Add Advanced Analytics Evidence to a Case Manager Incident
- Manage Tasks During an Investigation
- Send Messages from an Incident
- Filter Incidents
- Search for an Incident
- Sort Incidents
- Export Incidents
PrevNext
Issues Fixed in Case Manager i56.10
Issue ID | Description |
---|---|
SOAR-12827 | Fixed an issue with custom roles where you could not view Case Manager Metrics even if you had the View Metrics permission. In addition, the View Metrics permission was duplicated under both Core and Analytics. If you had the Core View Metrics permission, you couldn't view Case Manager Metrics. Now, the View Metrics permission is under Analytics only. |
PLT-12642 | Fixed an issue where if you assigned incidents, you saw multiple values for the same person. In addition, if you logged in to Exabeam and varied the letter case of your username, like Barbara_salazar or barbara_Salazar, Exabeam created a different user for each variation. |