Walter.Koller
Level 12
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Email to a Friend
- Printer Friendly Page
- Report Inappropriate Content
01-09-21
10:47 AM
Status:
New
After some time processes might not be needed anymore, because have been replaced by other processes, they become obsolete or maybe it was a one time activity only. It would be helpful if a deployed release could be rolled back (ie removed / deleted) from an enviornment.
In case of complex business processes, several BP processes and VBO might have been needed for its automation. Those dependencies between BP processes, VBO, queues, environment variables, schedules, ... are packaged into one release file and deployed into production.
When this buisness process automation is not needed anymore, the environment should be cleaned from not needed objects and configuration.
Currently this has to be done manually, for each object individually.
It would be much more convenient if there would be a rollback feature so all objects that are part of a release package could be removed at once. Of course with dependency check and warnings if necessary
In case of complex business processes, several BP processes and VBO might have been needed for its automation. Those dependencies between BP processes, VBO, queues, environment variables, schedules, ... are packaged into one release file and deployed into production.
When this buisness process automation is not needed anymore, the environment should be cleaned from not needed objects and configuration.
Currently this has to be done manually, for each object individually.
It would be much more convenient if there would be a rollback feature so all objects that are part of a release package could be removed at once. Of course with dependency check and warnings if necessary
5 Comments
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.