Once a Workflow Profile has loaded data and the Profile is no longer needed, how should it be managed?

Once a Workflow Profile has loaded data and the Profile is no longer needed, how should it be managed?

• A. Delete the Workflow Profile
• B. Hide the Workflow Profile
• C. Move to DO_NOT_USE Structure
• D. Move to Another Workflow Profile Cube Root Hierarchy

Answer: (C)

This question tests how to retire a Workflow Profile after it has loaded data without losing history or cluttering your active structures. Deleting would remove the profile and its associated data permanently, which makes future reference, audits, or reinstatement difficult or impossible. Hiding can obscure the profile from casual users, but it isn’t a robust governance solution because visibility can be re-enabled or permissions can change, allowing reuse or confusion. Moving the profile to the DO_NOT_USE Structure is the best practice. This reserved area is specifically meant for items that should no longer be active in day-to-day workflows but must be retained for traceability, auditing, or potential reactivation. It keeps the active workspace clean and safe from accidental reuse while preserving the historical context and relationships. Reclassifying to another active Cube Root would keep it in a usable state somewhere else, which defeats the purpose of decommissioning.

This question tests how to retire a Workflow Profile after it has loaded data without losing history or cluttering your active structures. Deleting would remove the profile and its associated data permanently, which makes future reference, audits, or reinstatement difficult or impossible. Hiding can obscure the profile from casual users, but it isn’t a robust governance solution because visibility can be re-enabled or permissions can change, allowing reuse or confusion.

Moving the profile to the DO_NOT_USE Structure is the best practice. This reserved area is specifically meant for items that should no longer be active in day-to-day workflows but must be retained for traceability, auditing, or potential reactivation. It keeps the active workspace clean and safe from accidental reuse while preserving the historical context and relationships. Reclassifying to another active Cube Root would keep it in a usable state somewhere else, which defeats the purpose of decommissioning.