When the Limits Module creates an evaluation task to check the KPIs of limits with intraday polling frequency for exceptions, previous evaluation tasks are not cleared, resulting in a memory leak.
If a single limit definition applies to multiple locations, the Exception tab will only show the last breach. For example, if a wildcard limit has breaches on two locations, only the measure value of the last breach is displayed in the tab.
File Upload results in a JSON parsing error when the same file is selected more than one time. As a workaround, add another Limit Inventory widget onto your dashboard and upload the same file.
Calculated measures need to be included in Pivot Table Query in order to view a Limit’s KPI in the Pivot Table. See Measures for more on how to create a query for Limits on calculated measures.
You can download the following zipped distribution files:
UI source code
UI build
Source files to build the module
Sample bookmarks
Maven repository required to build the project and run the tests. The ActiveViam 5.10.9 Maven repository files can be downloaded from here
Summary
Separate Limit Change and Exception workflows: Multiple fixes to the evaluation functionality of Limits.
Publishing Calculated Measures: Calculated Measures can now be published to the Cube. For more information, see Publishing a Calculated Measure.
Breach and alert reports: Breach and alert reports are now split into separate files per KPI. The file name format is: “/alert_{kpiName}_{lastUpdateTimeStamp}.csv”
Sample limits and bookmarks: We have created new sample limits that correlate with our sample data for FRTB, as well as added bookmarks tailored for these limits, which can be added to your deployment.
When the Limits Module creates an evaluation task to check the KPIs of limits with intraday polling frequency for exceptions, previous evaluation tasks are not cleared, resulting in a memory leak.
If a single limit definition applies to multiple locations, the Exception tab will only show the last breach. For example, if a wildcard limit has breaches on two locations, only the measure value of the last breach is displayed in the tab.
File Upload results in a JSON parsing error when the same file is selected more than one time. As a workaround, add another Limit Inventory widget onto your dashboard and upload the same file.
Calculated measures need to be included in Pivot Table Query in order to view a Limit’s KPI in the Pivot Table. See Measures for more on how to create a query for Limits on calculated measures.
Replaced the Breach and Warning workflow dropdowns with an Exception workflow dropdown within the Limits Drawer UI. For more information, see Create a new limit in the UI.
You can download the following zipped distribution files:
UI source code
UI build
Source files to build the module
Maven repository required to build the project and run the tests. The ActiveViam 5.10.9 Maven repository files can be downloaded from here
Summary
Separate Limit Change and Exception workflows: Redesigned the workflow to separate the limit change/update/delete workflow and the limit exception/breach/warning workflow. The Limit Change workflow now has Straight-through and four-eyes options. The Limit Exception workflow handles the breach and warning events. The workflow associated with exceptions is defined in the application.yml property file.
Exception UI: The Exception and Exception Audit tabs have been added to the Limits Drawer to help you investigate warnings and breaches. See Manage exceptions for details.
Performance improvements: Many performance improvements have been implemented to improve the startup time and KPI query time. More can be read in the Performance page.
Added integration tests: Added scopeTests, flowTests, KPIValueTests and ETLTests.
Creator can now approve the limit: The user who created the limit can now approve it if canTheApproverBeTheSameAsTheCreator in limits.properties is set to true. The default value for this property is false.
To make sure your limit workflow works as expected, please discard any previous testing data in the datastore and activiti databases. On top of the workflow name changes, the reference implementation now has the Role_Users by default to be able to create the limit definition instead of Role_Managers.
File upload results in a JSON parsing error when the same file is selected more than one time. As a workaround, add another Limit Inventory widget onto your dashboard and upload the same file.
Calculated measures need to be included in Pivot Table Query in order to view a Limit’s KPI in the Pivot Table. See Measures for more on how to create a query for Limits on calculated measures.
When a limit’s draft status is PENDING_DELETION, Approve and Reject buttons are displayed in the Limits Drawer. For details on configuring these buttons, see Configuring workflow action buttons.
The Limit Definition Datastore now contains new fields for a Limit’s Draft State and Draft Status. These Draft fields are used to move a Limit along a workflow without modifying the Limit’s current status. For example, if a Limit is approved and then edited, the Limit will still be valid until the changes are approved.
You can download the following zipped distribution files:
UI source code
UI build
Source files to build the module
Maven repository required to build the project and run the tests. The ActiveViam 5.10.9 Maven repository files can be downloaded from here
Summary
Remove hardcoded AsOfDate from KPIUtils: We now properly read in the AsOfDate properties map from limits.properties
New workflow names : The workflows have been renamed. - Straight through: no approval needed, created in approved state. - Four eyes: previously called single eye. One person creates the workflow, another person approves. - Six eyes: previously called 4 eyes. One person creates the workflow, two people approve.
note
To make sure your limit workflow works as expected, please discard any previous testing data in the datastore and activiti databases. On top of the workflow name changes, the reference implementation now has the Role_Users by default to be able to create the limit definition instead of Role_Managers.
Added property to specify the URL of the Limits Module: Limits now supports being run from any location; previously Limits was assumed to be running at localhost.
Audit trail screen : New audit trail screen is available in the Limits Inventory Widget. For more information, see Viewing the audit history
Added validation to Limit Definition: Limit Definitions are validated when loaded through CSV or File Upload.
Ui changes : Upgrade to AUI 5.0.11, Acc-sdk 5.0.7, added Audit trail tab in Limits Inventory, enabled Lazyloading for Limits Inventory Widget, numerous bug fixes, added column sorting to the Limits Inventory Widget, enabled Storytelling, better error handling.
Provided AP 5.9 LookupPostProcessor: Added AP 5.9 LookupPostProcessor Module to limits-lookup-postprocessors
Limits on Calculated Measures: Limits can now be created on Calculated Measures via File Upload.
Workflow after editing and deleting a limit: After editing or deleting a limit in the Limits Inventory Widget, the workflow is triggered. Editing triggers the Limit Change Workflow, deleting triggers the Straight through workflow and an audit record is created in the audit database.
Roles: All the KPIs created by the Limits module now have LIM_ROLE as the owner and viewer.
Calculated measures need to be included in Pivot Table Query in order to view a Limit’s KPI in the Pivot Table. See Measures for more on how to create a query Limits on calculated measures.
The Six Eyes workflow is not working as expected. The limit goes into the Approved state once the Examiner approved it, instead of pending approval until the Approver review.
For the Limits Inventory view, the sort only works on the first column. To sort on other columns, you can change the table column order to put the desired column first and then sort.
Added validation of Limit Definitions. When loading a Limit Definition, the validity of Server, Cube, Measure, and Scope Keys (Cube Level Members) parameters are checked within the given Server.
Added Audit screen to the Limits Inventory Widget drawer. Additionally, there is a new optional setting to set on the UI side limits_inventory-widget.server.params.auditTrailNodeColors, which allows users to map their workflow statuses to three timeline colors.
Added better exception handling, which will let the user know if there are certain levels which need to be part of the query running inside of the Limits Inventory Widget table.
Fixed the warning of the Greater Than KPI status. The warning level on a Greater Than limit now triggers a breach when the limit utilization is within the defined percentage.
Fixed bug where the Absolute Value Indicator value was being set by the Warning Threshold. Also, amber status logic was being applied incorrectly to KPIs.
You can download the following zipped distribution files:
UI source code
UI build
Source files to build the module
Maven repository required to build the project and run the tests. The ActiveViam 5.10.7 Maven repository files can be downloaded from here
Summary
UX re-design: Based on feedback from demos we have redesigned the UX of the Limits Module. Limits creation screen based on UX design
Limits edit and delete. Approval screen
Upgrade: to ActivePivot 5.10.7 and ActiveUI 5.0.7.
Amber support: Amber support has been added through the use of warningThreshold field. This lets you specify a percent of the limit value where the KPI should show amber status. For more information, see Create a New Limit.
New KPI Types: Previously, all limits were interpreted as “Greater Than”. Now, through the KPI Type field, you can specify “Less Than”, “Between”, and “Not Between”. For more information, see Create a New Limit.
AlertTask output modifications: AlertTask outputFile as well as AlertDefinition store fields have been re-organized and new fields have been added.
Replace per-limit AsOfDate: AsOfDate (the date that limits should be evaluated on in AlertTasks) is now set globally via AsOfDateTuplePublisher.
Use Start Date and End Date: Limit Start Date and End Date are now used to determine limit values at runtime. The Limits Module has the AsOfDate in the AsOfDate datastore, which is uploaded from the AsOfDate.csv file. All limit evaluations against the business cubes, such as MRA and FRTB, are based on the AsOfDate. At the start of the business day, the Limits Module expects that a new AsOfDate.csv file is uploaded through Data Connectors, to roll the date.
Removed property cube.rest.path: Instead, the cube.rest.path should be appended to the REST path defined in the acc.url.map property.
Currently, you can only edit a limit from the UI when the limit is in initiated state. In such cases, the limit change workflow does not start after the update.
Currently, only explicit Limit Scopes are support for evaluating Alerts. Evaluating an Alert Task using the /evaluate endpoint for a given KPI, if an underlying Limit’s Scope contains Wildcards, causes the evaluation to fail for that Limit.
Levels are not a unique identifier in a Cube. Two levels of the same name can refer to different data. In this case a Limit’s Scope defined on a level could have multiple meanings.
Limits upload error handling occurs when the measure name is incorrect. The Limits module currently doesn’t produce an error message when a measure name is incorrect.
Deleting a Limit Definition from within the Limits Inventory will cause the corresponding KPI to be removed from the Server even if other Limit Definitions use that KPI. Creating a dummy Limit Definition through the Limits Inventory will re-create all KPIs (including the deleted one) which will fix this issue.
AsOfDate removed from limit input files; replaced by global AsOfDate value. Start Date and End Date are now used in evaluation of limit values at runtime
For Between and Not Between KPI’s, setting a Warning Threshold has been disabled. Between and Not Between Limits with a Warning Threshold value will be rejected when loading a file.
Support Multiple ActivePivot Instances : The Limits Module now supports multiple ActivePivot instances. Clients can use one Limits Module to monitor and create KPI in Limits Inventory Dashboard, such as monitoring LIM and FRTB in one place.
On-Demand Limits Monitoring/change : LimitEvaluation restful endpoint is available for clients to trigger the evaluation on demand. The result is written into alert csv files with timestamps and exposed in the Breach Count measure.
Trend Analysis of Limits: By including AsOfDate hierarchy in the business cubes, users can now analyze KPI goal changes over a period of time.
Fixed bug where the rule message display would not reset when the rule was deleted.
0.2 Alpha
Support multiple AP servers
Change the way alert evaluation works. Intra-day observation frequency runs every 20 seconds by default. Other observation frequencies are required to invoke by client’s alert orchestrator.
0.1
Initial release
Input file formats for the CSV files that can be used by clients as input to the ActivePivot Limits Module Reference Implementation.
Limits definition files need to be replaced with the organization’s data.