We have redesigned our registers to present information visually, rather than as a plain list of items. Initiatives, Benefits, and RAID Registers will now feature a card layout, where each card represents a child object at that level.
Ability to Lock Past Actuals
We have received support cases where users inadvertently modified an actual value recorded in the past which caused problems with the overall planning and forecasting. Whenever a user attempts to update actuals, the systems will disable the preconfigured past actual fields for editing.
A setting has been added to the Site Settings tab by which Administrators can now configure the number of past periods in the respective benefit resolution which will be editable. For example, if the ledger or benefit resolution is Monthly, a setting of 12 periods will allow the last 12 months to be edited. All future periods following the current period will always be editable.
The Benefits Plan tab, as well as the Ledger, will be controlled by this setting. Read more here.
Search Function on the Filters Sidebar of the Table View
A search box has been placed within the Filters list of the table view, making it easy for you to search the columns that you want to filter.
Custom Fields Grouped by Core Objects
We have modified the way custom fields are displayed in the Columns selection list of the Reporting Dashboard.
In version 20.3.0, we had introduced a change where a custom field mapped to multiple objects were displayed as separate columns on the Reporting Dashboard. This was done to resolve the duplication issue that some of our customers faced.
However, when a custom field displayed several times, it created confusion even though it only meant that the same field was mapped to different objects. For example, in the below screenshot(of version 20.3.0) you can see the custom field 'Capex/Opex /Working Capital' listed multiple times as it is mapped to different benefit and initiative classifications.
To avoid this confusion, custom fields in the Columns selection list are now further grouped by the core objects they are mapped to.
|AMP-28||In the previous versions, the My Accounts page did not show the Hierarchy button. You can now see the Hierarchy button on this page.|
|AMP-30||Registers will now show the Amplify ID of core objects.|
|AMP-37||When a task is set to 100% for the first time, its completion date is recorded.|
|AMP-42||The Properties tab is made configurable again. We reverted the change that made Properties a separate fixed tab to address the feedback received about displaying the Properties tab as a fixed tab. It will be possible to turn the Properties dashboard off.|
|AMP-44||It will now Power BI dashboards can be the only dashboard on your instance. Previously it was required that at least one built-in dashboard is enabled for the customised Power BI dashboards to be configured. It was not possible to disable all built-in dashboards and enable only the customised Power BI dashboard.|
|AMP-51||A search function is made available on the Filters sidebar.|
|AMP-53||Updating RAID data via integrations caused errors at some customer sites. Parent initiatives were replaced with a null value and the risk dashboard did not show breadcrumbs while the history showed that the parent initiative was blanked out as a result of the update operation. We have fixed this.|
|AMP-55||Previously, it was impossible for a user to restart the stage-gate process because the Restart button is visible only if the user has Admin privileges. We have made some modifications to this behaviour. From this version onward, an initiative owner or a user with no admin privileges will be able to restart the process.|