There is standard functionality for the cancellation of an Investment deletion request.
When a Project Investment instance record is marked for deletion, that investment can be deleted upon the successful execution of the 'Delete Investments' job. If the end-user wants to cancel the deletion of the Project Investment instance record before the job executes, the Clarity application will allow the end-user to select the Project Investment instance record and upon clicking the 'Cancel Deletion' button the Purge Flag will be reset and the investment will not be deleted.
This button does not appear on the Application list page or any other Non-Project Investment Object (NPIO) List View. Assets, Applications, Ideas, Other Work, Products, Services. Therefore, all NPIO instance records marked for deletion cannot be cancelled as expected.
Steps to Reproduce:
These steps are specific to the 'Application' Object, but the issue persists for all NPIO List Views.
- Login to a Clarity system with a user that has global Application - Edit - All right.
- Navigate to Portfolio Management-> Applications.
- Select one of the Application displayed and click the Mark for Deletion button.
- Attempt to cancel the deletion request just made.
Expected Result: I should see a 'Cancel Deletion' button for all NPIO object List View pages.
Actual Result: But Instead I do not see the 'Cancel Deletion' button on the List View.
This is caused by CLRT-20328
The 'Purge Flag' attribute is available for configuration on the Non-Project Investment Objects through Studio, however this attribute does not allow for end-user editing through the Clarity application user interface.
If it is really necessary to prevent an NPIO record instance from being deleted, reset the PURGE_FLAG to zero on the INV_INVESTMENTS record. Be sure to fully test this change in a development / test environment before implementing in a production environment.
It is also recommended to place restricted access on the 'Delete Investments' job so that it is not scheduled for automatic execution and so that only specific end-users will have the ability to actually execute the job.
This is resolved in CA PPM 12.1.1