Standard life cycles will continue to be supported after the Classic Workflow interface is deprecated. However, standard life cycles do not support all of the functionality that Unity life cycles support, and newly created life cycles are Unity life cycles by default.
You can convert a standard life cycle to a Unity life cycle in order to use the enhanced features available.
The following limitations must be carefully considered before converting a standard life cycle to a Unity life cycle:
- Any actions or rules in other life cycles that reference the life cycle being converted must be manually updated after the new Unity life cycle has been created in order to point to the new life cycle.
- Unity life cycles do not support Work Folders. If a standard life cycle uses a Work Folder, you must create a Portfolio Type in order to find related items in the Unity life cycle. A Portfolio Type can be created from an existing Work Folder. For more information, see Configuring Portfolio Types.
- Unity life cycles do not support the use of VBScripts. You can configure and use Unity scripts to replace VBScripts. To verify if a life cycle uses VBScripts, click the Advanced Options tab in the Properties pane and confirm if a VBScript is selected in the VB Script to Execute on Selected Document drop-down list. For more information about using Unity scripts, see Unity Project.