- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Flow Approval System Properties
New in the Yokohama release, we introduced 4 additional system properties that greatly improve approval auditing. These new system properties give you more control over how approvals are tracked, especially in complex workflows involving delegation, impersonation, or inactive users and groups.
Let’s walk through each property with real-world use cases to help you decide how to configure them for your environment.
Showing Approver Names in Audit History
Property: com.glide.hub.flow.approval.show_approver_name_in_audit
Use Case:
A flow is triggered by a service desk agent, but the actual approval is done by a team lead. Without this property, the audit trail misleadingly shows the agent as the approver.
Set to true to ensure the audit log reflects the actual approver, not just the flow initiator.
Best for: Clear accountability in multi-user workflows.
Highlighting Role-Based Approvals
Property: com.glide.hub.flow.approval.show_higher_role_audit_comment
Use Case:
A senior manager approves a request because their role grants them override permissions. You want the audit log to reflect that this wasn’t a standard approval.
Set to true to add a comment like:
“XY approved, permission granted by role.”
Best for: Environments with tiered or escalated approval paths.
Tracking Delegate Approvals
Property: com.glide.hub.flow.approval.show_delegate_audit_comment
Use Case:
A VP is on vacation, and their delegate approves a budget request. You want the audit trail to show that the delegate acted on behalf of the VP.
Set to true to log:
“XY approved the task as delegate of YZ.”
Best for: Teams with formal delegation policies.
Capturing Impersonation Details
Property: com.glide.hub.flow.approval.show_impersonate_audit_comment
Use Case:
An admin impersonates a user to troubleshoot a workflow and accidentally approves a task. You need to know this wasn’t the user’s own action.
Set to true to log:
“System Administrator approved the task by impersonating XY.”
Best for: Admin-heavy environments or sandbox testing.