What's New
This page provides a brief overview of the user-facing new features and improvements in the latest version of the Sign-Off Module.
For bug fixes and developer-facing changes, see our Changelog.
Note on issue keys
Each update is referenced with an issue key which is an internal reference. You can quote this to ActiveViam support if you have any questions about an item listed below.
4.0.0
Summary
-
Improvements in the way sample workflows are defined:
- Activiti signals are no longer used; the roll-back action is now used instead.
- User tasks have been added for adjustment operations (requests for adjustment creation and deletion) to use Activiti for the permissioning of these operations instead of logic coded in Java.
- Permissioning: the concept of ‘initiating user’ has been introduced:
- Only the user who initiates a given sign-off process instance can perform adjustments, and request approval operations on that instance.
- A technical user in now defined for actions like roll-back. Roll-back can be performed by the technical user and by the initiating user.
- We now rely on the Activiti process instance variables to handle the permissioning instead of retrieving the current user from the Spring Security context.
-
Deleting individual adjustments is now possible:
- Previously, adjustments could only be deleted in bulk when a signal was triggered. See Discarding Adjustments.
-
Upgrade to ActivePivot 5.10.6
-
Upgrade to ActiveUI 5.0.6
-
Renaming of module signoff-core to workflow-core
New features
Ability to delete individual adjustments: The deletion of individual adjustments can now be requested. Previously, adjustments could only be deleted in bulk when a signal was triggered.
4.0.0 Alpha
Summary
-
Improvements in the way sample workflows are defined:
- Activiti signals are no longer used; the roll-back action is now used instead.
- User tasks have been added for adjustment operations (requests for adjustment creation and deletion) to use Activiti for the permissioning of these operations instead of logic coded in Java.
- Permissioning: the concept of ‘initiating user’ has been introduced:
- Only the user who initiates a given sign-off process instance can perform adjustments, and request approval operations on that instance.
- A technical user in now defined for actions like roll-back. Roll-back can be performed by the technical user and by the initiating user.
- We now rely on the Activiti process instance variables to handle the permissioning instead of retrieving the current user from the Spring Security context.
-
Deleting individual adjustments is now possible:
- Previously, adjustments could only be deleted in bulk when a signal was triggered. See Discarding Adjustments.
-
Upgrade to ActivePivot 5.10.6
New features
Ability to delete individual adjustments: The deletion of individual adjustments can now be requested. Previously, adjustments could only be deleted in bulk when a signal was triggered.
3.1
Summary
- Recurring adjustments : Recurring adjustments are now loaded when a sign-off task is initiated.
- Roll-back feature : During the execution of a sign-off workflow, it is now possible to go back to the initiate state from any point in the workflow.
- Datastore/cubes: Two new hierarchies have been added to the adjustments executions cube: [validFrom] and [validTo], to provide the validity period of the corresponding adjustments definitions
New features
Adjustments
-
Recurring adjustments are now supported: when a sign-off task is initiated, the recurring adjustments valid for the current as of date are executed. See Recurring Adjustments
-
A roll-back feature is now available from the sign-off workflow: at any point of the sign-off workflow, it is possible to go back to the initiate state of a sign-off task to start the sign-off process again. See Rollback
Improvements
- Adjustments widget: The valid from and valid to dates are now present in the Adjustments widget.
3.1.0 Alpha
This is an Alpha release of the sign-off module. It is not meant to be used in a production system.
The following features are not implemented yet:
- roll-back of a sign-off process instance
- execution of persisted adjustments
Known issues
| Issue Key | Details |
|---|---|
| [SO-158] | Adjustment status hierarchy has to be on rows in Adjustments dashboard |
| [SO-153] | Cube level adjustments can only now be done on specific table (example in Adjustments bookmarks) |
| [SO-155] | In bookmarks, storytelling won’t work if ID of target bookmark changes |
| [SO-157] | Adjustments on scope for tasks that cover more than two desks won’t work directly |
Fixed issues
n/a
New features
Adjustments
-
The support for adjustments is now more comprehensive: new tables have been added to the application database and to the audit database to persist adjustments and provide an audit trail.
-
In the Application database, two new tables have been added: ADJUSTMENTDEFINITION and ADJUSTMENTEXECUTION
3.0.0
Changes
-
The Sign-Off Module has been upgraded to ActivePivot 5.9.6.
-
The Sign-Off Module now supports the connection to multiple application servers.
-
A list implementation of adjustments support has been provided.
Known issues
| Issue Key | Details |
|---|---|
| [SO-106] | UI link to documentation is broken. |
| [SO-20] | The Sign-Off Toolbox does not change to slicing date after the previous asOfDate filter is removed. |
| The Compute action to compute difference, average, and sum for selected columns is not working, due to the upgrade to ActiveUI 4.3.13. As a workaround, create calculated measures manually. |
2.3.0
The Sign-Off Module has been repackaged to make its customization easier.
Known issues
| Issue Key | Details |
|---|---|
| [SO-20] | The Sign-off Toolbox does not change to slicing date after the previous asOfDate filter is removed. |
| The Compute action to compute difference, average, and sum for selected columns is not working, due to the upgrade to ActiveUI 4.3.13. As a workaround, create calculated measures manually. |
2.2.0
Fixed Issues
The following issues have been fixed in 2.2.0:
| Issue Key | Details |
|---|---|
| [SO‑19] | Primary key collisions in tables for history objects have been fixed. Unit tests that could fail intermittently now pass. |
Changes
For historical records (records that extend the abstract class AHistoryRecordEntity), the primary key has been changed: it now uses the new HistoryRecordId class as implementation of the primary key. This avoids primary key collisions that could happen with database table definitions of previous versions of the Sign-Off Module.
Known issues
| Issue Key | Details |
|---|---|
| [SO–20] | The Sign-off Toolbox does not change to slicing date after the previous asOfDate filter is removed. |
| The Compute action to compute difference, average, and sum for selected columns is not working, due to the upgrade to ActiveUI 4.3.13. This will be fixed in the next release. As a workaround, create calculated measures manually. |
2.1.0
New features
4-eyes KPI workflow
A sample workflow with automated approval at initiation when the KPIs associated to a sign-off task all have a status of “1” (i.e. the status of the KPI is green).
For details, see Customizing sign-off backend
Fixed Issues
The following issues have all been fixed in 2.1.0:
-
Sign-off is now available for the previous asOfDates (change it using content editor).
-
Sign-off Tasks Definition widget now checks after any updates are performed on the table to update the state of the button.
Known issues
Synchronisation between database transactions
The synchronisation of transactions between the application database,
the audit log database and the Activiti database needs to be improved.
With the current implementation of database transactions, some unit
tests might fail intermittently due to the fact that the successive
operations performed in these tests are done within a very short time
frame.
Slicing date in Sign-Off Toolbox
Sign-off Toolbox does not change to slicing date after previous asOfDate filter is removed.
2.0.0
New features
Completely restructured application
The Sign-Off Module has been rewritten from scratch with a new, more modular architecture. The sign-off back end is now a standalone component and the sign-off UI has been put into its own SDK
For details, see What is the Sign-Off Module
Known issues
Sign-off is only possible for the latest asOfDate
(Sign-off for previous dates will be added to the next release)
Error in Sign-off Tasks Definition widget when clicking an action button
Instability sometimes occurs if no sign-off tasks are selected in the Sign-off Tasks Definition widget, clicking the action button (Archive/Delete/Publish) picks up the latest selected sign-off task and causes an error.