- The cost profile now supports standard attributes, Name, Ownership, Cost Group, and Cost
- Category Costs now support custom fields on their profile
- Properties are captured directly from the profile
- The Cost sub-menu allows access to cost profiles
- New configuration options to allow for the Budget, Actual, or Forecast to be toggled per Cost
Cost Profile supporting standard attributes, name, ownership, cost group, and cost category
A Cost is defined by the group and category classification it belongs to. It can have an owner and its own custom fields. Properties are captured directly from the profile.
Custom fields mappable to costs
Custom fields can be mapped to costs and used as reporting groups, enabling you to filter specific costs on the investment dashboard.
Sub-menu for accessing costs
You can view all costs enabled for the current initiative classification on the Cost sub-menu. Select any cost profile and enter data.
New configuration options
Costs now have configuration options which allow for the Budget, Actual, or Forecast to be toggled per cost.
Ability to Fast-load RAID Items
RAID Items, except external dependencies, can now be imported into Amplify using the integrations feature. The procedure is the same as with the existing integrations. You can import standard as well as custom fields.
Enhanced Excel Export Performance
If you use Table View a lot, you will experience improved performance in this version. Our performance enhancements ensure that everything happens fast. Views are loaded in a flash, filter and column fields respond immediately, and the Export function can extract up to 10,000 rows at one go.
Filter Open or Closed RAID Items
We have added a new filter option in the register that will allow you to filter RAID items based on their status. By default, the RAID register will only show items in 'Open' status. To view closed items, uncheck the filter option.
Baseline Process in the Background
Baseline process now works in the background so if you are baselining at a top hierarchical level, you can continue doing other tasks while Amplify finishes creating the baseline. This new design enhancement makes sure that you can only create a second baseline after Amplify finished creating the first one in the background.
Custom Email Notifications
In response to requests from several of our customers, we have improved the translations feature to enable you to personalise the standard text included in Amplify's email notifications.
|AMP- 8692||Initiative showed up multiple time on Process Dashboard for one of our customers. This issue has been fixed.|
|AMP- 8442||The new RAID Item form had an issue when switching to another classification that has rating enabled. We have fixed this issue in this release.|
|AMP- 8236||Mostly reported on Amplify demo instance, some initiatives go into a continuous recalculating state and remain stuck in that state. The root cause has been attributed to the system being unable to recalculate the net present value if the Initiative Start and End Dates are modified to a separate date range that does not overlap with the previous range. This issue has been fixed.|
|AMP - 8724||Comments entered by the requestor displayed in place of Assessment Criteria on the stage-gate approval widget. A translation error was reported by one of our customers because of the above error. We have fixed this. You will now see the Assessment Criteria in a collapsible panel below which the user comments will be displayed.|
|AMP - 8709||If an initiative property field was updated after firing the Initiative Quick Print Report, the updated value was not getting saved. To fix this issue, we have designed the Initiative Quick Print to open in a new tab.|
|AMP - 8771||When a translated benefit series label was used in integrations, the values did not get imported even if the integration completed successfully. This issue is fixed.|
|AMP - 8770||When there are two or more initiatives with identical names it is difficult to differentiate which entry belongs to which initiative because all entries display under the same initiative header. We have fixed this. Initiatives will be grouped based on their IDs and not names on the ledger.|