- 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
Known Issues
SOAR-12695 | If you upgrade from Case Manager i53.5 or earlier, custom parsers don't work correctly and you can't ingest data from your incident feeds. Starting with parsers in i53.5, all hyphens, colons, or semicolons in incident type names were replaced with underscores. If your custom parser refers to a custom incident type with hyphens, colons, or semicolons, the Case Manager Parsing Engine can't parse logs for that incident type. To resolve this issue:
|
SOAR-12718 | When you manually run the Send Template Email action from an incident's workbench, you encounter a Failed to send email error because the action was incorrectly deprecated. To resolve this issue, use the Notify by Email action instead. |