in Envizi™ ESG Suite, you can enable account data approvals and customize
the approval workflow settings to suit your organizational data governance policies.
Before you begin
You can request to have all of your historical account records with a start period before a
specified date to be bulk approved. This step is required only if you have a large amount of
historical account data that was captured in IBM® ESG Suite before the
enablement of the account data approvals feature.
If you require historical account records to be bulk approved, advise your IBM support team or IBM partner of the historical data
approval date at any time after the approvals feature is enabled. If you do not request historical
data to be approved, an approval status needs to be manually set for all existing records so that
the records are correctly accounted for in the approved percent calculation for downstream
reporting.
About this task
Use the following procedure to enable account data approvals and configure approval settings to
suit your organizational data governance policies.
Procedure
-
Enable the account data approvals feature in the
page.
The account data approvals settings become visible in the Account
Data Approval Preferences page.
- Click and configure the following settings:
- Approval workflow type
- Select either a 2-step review and approval workflow, which is the
default, or a 1-step approval only workflow. The 2-step workflow enables the
Pending Review and Reviewed workflow steps that are hidden in the
1-step workflow.
- Review process bypass
- You can select this option to enable approvers to bypass the
Pending Review and
Reviewed workflow steps. This option is visible only if you select the
2-step review and approval workflow.
- Separation of duties
- You can enforce separation of duties so that each of the following actions must be performed by
a different user:
- Record creation
- Record reviewer
- Record approver
- Flag settings
- By default, all account records that are created after the approvals feature is enabled are
assigned the
Created status. If you have large volumes of automated data that are
uploaded by file, you can choose to have a different default approval status for the data by
changing the following flag settings. For example, to automatically approve data that is uploaded by
file, use the following settings:
- Set Flag manually captured records to Yes.
- Set Default approval status flagged records to
Created.
- Set Default approval status non-flagged records to
Approved.