Request to allow removal of Comonent/Applications/Versions etc. by Admin Hot

by Yan Li on July 10, 2017

The request coming from some Oppt feedbacks. Customer complained that it's not easy to maintain a manageable/clear environment without a removal feature internal of DA though they could understand that Audit is very crucial here. 

  • After some rounds of discussion with some Oppts, most customers do expect to have the removal feature for Components, Applications, Versions etc. in DA. The removal of objects in DA can only be granted to users with special priviledge (like Admin) in order to make sure that the data integrity for Audit. 

    Personally, I do think the feature is valuable in particular for customers who trial our product at the first min. They will make some mistakes and yes, they can just inactive some objects but when they create new objects with the same name, the request will be blocked. Reference to the Administration of CM, a role with Adminitration should be allowed to remove those useless data. Of course, the removal action should be logged into the historial repository.

    Appreciated if you can consider this in the future release.

     

    Thanks

    Very Best Regards.

    Ideas

  • Please login to view any attachments.

  • This is a key governance feature required by highly regulated large enterprise like Financial, Telecom, Government and Defense industry. If the administrator can remove the component, application or version, there will be no audit trail of the exact files and versions which are used to deploy the application.
    Matthew Ong Commented by Matthew Ong October 26, 2017
    Top 50 Reviewer  -  

    This is a key governance feature required by highly regulated large enterprise like Financial, Telecom, Government and Defense industry. If the administrator can remove the component, application or version, there will be no audit trail of the exact files and versions which are used to deploy the application.

     

Print