Idea is for a Purge Robot that can be used in a Workflow. Needs the ability to purge the primary business object for Advanced Lifecycle Workflows as well as Resulting Objects for Change Notices/Tasks.
Needs to accomplish a simultaneous Purge of WTParts and associated CAD so the BuildHistoryLink does not prevent a Purge.
Release Workflow is a logical event at which to perform a Purge because when something gets Released you should no longer need all of the iterations that led up to the Version to be Released.
Batch Purge leaves a latest version at the pre-Release State (at least I can't seem to get rid of them). Scheduled Purge may remove wanted Versions pre-Release.
No Purge seems to equate to exponential storage consumption.
Also useful for purge would be the ability to have an if statement capability. For example: If latest iteration of latest version is released, then purge non-latest iterations.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.