Exception management workflow versus flow designer in Configuration Compliance

Starting with Configuration Compliance (CC) v13.0, if you are deploying CC for the first time, the flow designer for approving exception requests in exception management is enabled by default. If you are an existing CC user, the default option is workflow.

表 : 1. Workflow versus flow designer

Considerations	Workflow	Flow designer
Version	Prior to v13.0 of CC.	Starting from v13.0 of CC.
Default option	Default option if you are an existing CC user.	Default option for new CC users starting from v13.0.
Setting the approval process	Exception management includes exception requests along with exception rules.	Includes defining various levels and adding different approvers for different use cases. Easier to implement than the workflow. Exception management includes exception requests along with exception rules.
Upgrading to flow designer	You can upgrade to flow designer from workflow. However, existing requests can only be approved using the workflow.	Flow designer is enabled by default.
System property sn_vulc.flow_designer_activation	If you have been using the workflow for exception management prior to v13.0, the system property is set to false. To activate the flow designer, set this property to true. 注: You cannot revert to using the workflow after activating the flow designer.	If you are using CC for the first time for v13.0 or later, the system property value is set to true by default.
Approval rules module	After setting the system property to true, the Enable module approval rules scheduled job runs within 24 hours. This scheduled job enables the Approval rules module. To activate this module instantly, run this job manually.	If you have deployed CC for the first time from CC v13.0, this module is available by default.
Approval levels	Provides the option to set only two levels of approvers.	Provides multiple options such as setting any number of configurations, approver levels, and dynamically adding approvers for each rule.