If you haven't started using Amplify's Cost feature, now is the time to do it. Our latest enhancements guarantee that you will be able to work with costs with the same ease as benefits.
The multiple costs per category feature impacts the Cost integrations functionality. As a result, your integrations will need to be updated. Please see the revised knowledge base article for more information.
Add a cost profile
Just like a benefit, you will now be able to add a cost profile, from the Cost sub-menu.
Add multiple costs per category
Unlike previous versions, you will now have the ability to create multiple costs under a cost category.
All cost profiles can be accessed from within the Cost submenu.
Archive and Restore costs
Since costs have their own existence, it will now be possible to archive and restore a cost profile.
The Cost tab will now allow you to access a cost quickly by typing in its name in the filter box. It is also possible to access archived costs.
Bulk upload cost profiles
You will now be able to create cost profiles or update existing cost profiles via integrations.
- Fields required to be mapped while creating costs: Parent initiative, name(of the cost), owner and cost category
- Fields required to be mapped while updating costs: ID, name or external ID as identifier lookup
Export Data from Ledger to Excel Spreadsheet
You can now export data from the benefit or the cost ledger to an Excel file. We have introduced a new button labelled Export to Excel in the Ledger view.
'Properties' is the First Tab
The Properties page provides our users with a quick and easy way to view and update the basic properties of initiatives. We have decided to make this the first tab on the initiative dashboard and make it visible at all times so that you will be able to access it without configuring it. Properties will be the left-most tab for all initiatives and it will not be possible to hide it.
Please note that you will still be able to set another dashboard as the default landing tab on the initiative dashboard. The configuration settings are the same. We have just removed Properties dashboard from the list of Available Dashboards from the administration settings.
More Granular Permissions
We have added a few specific permissions for Roles that will empower you to control access to business cases, goals and scenarios.
Read more about permissions here.
|AMP- 8767||Benefit integration on one of our sites did not go through because financial year resolution was added as 'FINANCIAL YEAR' in the excel sheet. The acceptable format is 'FINANCIAL_YEAR'. But this was not clear in the error text. We have rephrased the error text with clear guidance for users.|
|AMP- 8460||The date when the Microsoft Excel file used for integrations is displayed at two places: on the edit integrations form, and below the Use Previous option once you select the previously used file. This was showing incorrectly. We have corrected it.|
|AMP- 8739||"Active" column of the baseline table was displayed as "Show Updates". We have fixed this.|
|AMP- 8851||If there are more than one layer of approvals, the email that is sent when one layer is completely approved shows translation error. This will be seen only by our users that use the translated version. We have fixed this.|
|AMP-8854||The translation 'estimate_at_completion' was still being used in place of 'forecast' in Amplify and this caused some issues. We have replaced it with 'forecast' wherever applicable.|
|AMP-8746||Report titles showed invalid characters.|
|AMP-8817||An error in views caused tables not to load. We have fixed the views.|
|AMP-8841||Invalid fields indicating fields without translation [missing.activerecord..."translation] available for mapping in benefit integration which causes an error. We have removed these.|
|AMP-8864||The notification that displays on the top of the interface when a benefit is being updated never disappeared even if you dismissed it and moved on to another screen. It returned when you navigated back. We have fixed this.|
|AMP-8476||The inputs on the adjust data screens are grouped by year, but this is the calendar year, not the financial year. We have changed it so that the inputs are grouped by financial year.|
|AMP-8851||The email sent when one layer is completely approved in a sequential approval workflow, showed a translation error.|
|AMP- 8876||Expand All function of the Reporting Dashboard did not work if the rows in the grid were grouped by multiple columns. We have fixed this.|
|AMP - 8863||Baseline costs become double the Budget on Investment Dashboard. This is fixed.|