Snowflake versus In-memory Features: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 20: | Line 20: | ||
||Queue analysis to identify bottlenecks, Four eyes principle for compliance violations (and other new presets) | ||Queue analysis to identify bottlenecks, Four eyes principle for compliance violations (and other new presets) | ||
|style="text-align:center;"|X | |style="text-align:center;"|X | ||
|Planned in PA 2023. | |Planned in PA 2023.6 | ||
|- | |- | ||
||Machine learning based prediction | ||Machine learning based prediction | ||
Revision as of 00:01, 15 October 2023
This page describes differences in available features between in-memory and Snowflake dashboards.
| Feature | In-memory | Snowflake |
|---|---|---|
| Event filtering based on event attributes and expressions (by any criteria) | Only by event types | X |
| Filter rules can be defined for measures and dimensions | X | |
| Dynamic event type mapping (allows to set event type for each chart/flowchart) | X | |
| Queue analysis to identify bottlenecks, Four eyes principle for compliance violations (and other new presets) | X | Planned in PA 2023.6 |
| Machine learning based prediction | X | Planned in future |
| Notifications and alerts to initiate corrective actions | X | Planned in future |
| Calculated attributes to create reusable measures | X | Planned in future |
| Case level permissions for detailed access control | X | Planned in future |
| Dropdown list for custom parameter selection | X | Planned in future |
| Custom aggregations defined using expressions | X | Planned in future |