Introduction to Dynamic Status
Quick introduction to the module key capabilities
You will find status on all modules: Risks, Policies, Projects, Exceptions, Etc. They helps us to quickly understand how items are performing, for example: Too Many Failed Audits, Review Expired, OK, Etc.
In important aspect of statuses is inheritance. You can inherit statuses from related modules. If you defined a Third Party under Organization / Third Parties module and you linked that Third Party to the Risk Module, you can on the Third Party module inherit the status of your Risk module. You could then set a status on your Third Party when its associated Risks statuses are "High Risk".
While eramba ships with a set of "System" statuses that cover the most common situations on any module you can create your own custom status based on your conditions. Every module in eramba has a "Status" option on the top bar where you can see what status exist and create your own status.
The conditions you can use to create statuses are grouped into three:
- Fields: you can compare the fields on the module item. For example: If owner is "Empty" and "Title" includes "Test" ...
- Functions: return a numeric value based on the item or its related items. For example: Return the number of audits for this control, return the number of risks for this asset, Etc.
- Related Status: return the number of items with a related status. For example: return the number of child audits where the status is "Failed"
You have hundreds of combinations for you to use and create your own statuses.
Statuses will be displayed when the conditions you defined match and hidden when they don't. In both cases you can trigger notifications. So for example you can create a status that triggers when a Risk Review has been completed but has no attachments linked to it (indicating no evidence has perhaps been included on the review). You can then create a "Warning" notification (an email or REST call) that will trigger to the "Reviewer" of that "review" to notify them about the situation.
This notifications can also be REST calls, letting you trigger web-hooks to other systems based on changes and conditions defined by you on eramba.
You can also run filters against your status, this allows you to search, for example, all controls that match the status X or Y. You can create these filters and saved them so they can be then automatically sent to you by email (filter will be as CSV or PDF) regularly (every week, etc).
Multiple charts use status for graphics - a typical chart that comes on every module is "items grouped by status over time". This allows you to show over time how items in a module behave. For example how many "Failed Controls" over time, "Expired Risks", Etc.