Workflow
The Workflow module enables administrators to build and maintain dynamic, task-driven workflows that enforce business processes for metadata management. Workflows consist of stages containing tasks that route requests through review, approval, and deployment processes.

Workflow module showing workflow builder and task management
Overview
The Workflow module is comprised of two main components:
- Workflow Tasks - Individual operations assigned to stages
- Workflow Builder - Visual workflow designer for creating and managing workflows
Workflows enforce your organization's metadata governance by: - Routing requests through defined approval chains - Validating data quality at each stage - Automating notifications and escalations - Ensuring compliance with business rules - Deploying approved changes systematically
Quick Links
Workflow Tasks
Tasks are individual operations that define actions within workflow stages. Each task combines an action type with configuration for security, notifications, and custom logic.

Workflow Tasks management screen
Task Components
| Component | Description | Options |
|---|---|---|
| Name | Task identifier | User-defined text |
| Description | Task purpose | Optional text |
| Action | Task operation type | Review, Approve, Validate, Deploy, Notify, Custom |
| Email Template | Notification template | From Email Templates |
| Security Group | Assigned group | Review/Approve only |
| Custom Function | Logic Builder script | Custom action only |
| # of Approvals | Required approvals | Review/Approve only |
Task Actions
Review
Assigns review responsibilities to users/groups: - Validates request data - Checks business rules - Can modify request lines - Provides feedback
Approve
Final authorization for requests: - Approves/rejects changes - Escalation handling - Cannot modify data - Final decision point
Validate
Automated data validation: - Runs validation scripts - Checks data quality - Enforces business rules - No user interaction
Deploy
Sends metadata to target systems: - Direct deployment - File generation - Interface tables - Multi-environment support
Notify
Sends notifications without action: - Status updates - Escalation alerts - Information only - No approval required
Custom
Executes Logic Builder scripts: - Complex business logic - Integration calls - Data transformation - Custom processing
Creating Tasks

Task Properties dialog for creating new tasks
- Navigate to Workflow → Tasks
- Click the + icon
- Configure task properties:
| Property | Required | Description |
|---|---|---|
| Task Name | Yes | Unique identifier |
| Description | No | Task purpose |
| Action | Yes | Select action type |
| Allow Requestor to Review/Approve | No | Requestor can act on own request |
| Allow Reviewer to Cancel Lines | No | Reviewer can cancel request lines |
| Email Template | No | Notification template |
| Security Group | Conditional | Required for Review/Approve |
| # of Approvals | Conditional | For Review/Approve actions |
| Custom Function | Conditional | Required for Custom action |
- Click Save
Editing Tasks
- Right-click on task row
- Select Edit Properties
- Modify configuration
- Click Save
Task Dependencies
Changes to tasks don't affect in-flight requests. Existing requests maintain their original task configuration.
Deleting Tasks
- Right-click on task row
- Select Delete Task
- Confirm deletion
Deletion Impact
Ensure task is not assigned to any active workflow stages before deletion.
Workflow Builder
The Workflow Builder provides a visual interface for creating and managing workflows. Workflows consist of stages arranged in sequence, with each stage containing one or more tasks.

Workflow Builder showing visual workflow with stages
Workflow Structure
graph LR
A[Start] --> B[Create]
B --> C[Review]
C --> D[Approve]
D --> E[Deploy]
E --> F[End]
C -->|Reject| B
D -->|Reject| B
Workflow Properties
Click the green Start node to view workflow properties:

Workflow Properties configuration
| Property | Description | Impact |
|---|---|---|
| Workflow Code | System identifier | Unique code |
| Name | Display name | User-visible |
| Priority | Workflow priority | From lookup table |
| Description | Workflow purpose | Documentation |
| Security Class | Access control | Who can use workflow |
| Enabled | Active status | Workflow availability |
| Visible | Display in dropdown | Request page visibility |
| Require Comments for Rejection | Mandatory rejection notes | Audit trail |
| Require Comments for Recall | Mandatory recall notes | Documentation |
| Restrict Recall | Limit recall ability | Only current stage actors |
| On Submit Logic Scripts | Validation/processing | Runs at submission |
Creating Workflows

Workflow Properties dialog for new workflow
- Navigate to Workflow → Builder
- Click the + icon
- Configure workflow:
Workflow Code: FIN_STANDARD_APPROVAL
Name: Financial Standard Approval
Priority: Medium
Description: Standard financial metadata approval workflow
Security Class: FIN_USERS
Enabled: ✓
Visible: ✓
Require Comments for Rejection: ✓
Require Comments for Recall: ✓
Restrict Recall: â–¡
On Submit Logic Script: VALIDATE_FIN_REQUEST
- Click Save
Restrict Recall Behavior
- Unchecked: Any user with workflow access can recall
- Checked: Only requestor, reviewers, and approvers of current stage can recall
Editing Workflows

Edit Workflow Properties dialog
- Right-click on green Start node
- Select Edit Properties
- Modify configuration
- Click Save
Deleting Workflows
- Select workflow from dropdown
- Click Actions button
- Select Delete Workflow
- Confirm deletion
Active Requests
Cannot delete workflows with pending requests. Complete or cancel all requests first.
Workflow Stages
Stages define the sequence of operations in a workflow. Each stage contains tasks that must be completed before progression.

Workflow with multiple stages configured
Stage Properties
| Property | Description | Example |
|---|---|---|
| Stage # | Execution order | 10, 20, 30... |
| Name | Stage identifier | Review, Approve, Deploy |
| Description | Stage purpose | Technical review by IT |
| Action | Stage operation | Review, Approve, Validate, Deploy, Notify, Custom |
| Freeze | Lock additions | Reviewer can only edit properties |
Adding Stages

Stage Properties dialog for adding stages
- Select workflow from dropdown
- Click Actions → Create Stage
- Configure stage:
Stage #: 20
Name: Technical Review
Description: IT department technical review
Action: Review
Freeze: â–¡ (Allows adding members)
- Click Save
Stage Numbering
Use increments of 10 (10, 20, 30) to allow inserting stages later without renumbering.
Assigning Tasks to Stages

Assign Tasks dialog showing available tasks
- Click on stage node in workflow
- Click Actions → Assign Task
- Select tasks to assign
- Click Save
Multi-Environment Deployment
For multi-environment configurations, create deployment stages for each environment:
Example: Three-Tier Deployment
- Create Deploy Stages:
- Stage 40: Deploy to Development
- Stage 50: Deploy to UAT
-
Stage 60: Deploy to Production
-
Create Deploy Tasks:
- Task: Deploy_DEV (Environment: Development)
- Task: Deploy_UAT (Environment: UAT)
-
Task: Deploy_PROD (Environment: Production)
-
Assign Tasks to Stages:
- Assign Deploy_DEV to Stage 40
- Assign Deploy_UAT to Stage 50
- Assign Deploy_PROD to Stage 60
Editing Stage Tasks

Edit task properties from within stage
- Select stage node
- Right-click on task in grid
- Select Edit Properties
- Modify task configuration
- Click Save
Workflow Examples
Standard Approval Workflow
graph LR
A[Start] --> B[Stage 10: Create]
B --> C[Stage 20: Review]
C --> D[Stage 30: Approve]
D --> E[Stage 40: Deploy]
E --> F[End]
Configuration:
| Stage | Action | Task | Security Group | Email Template |
|---|---|---|---|---|
| 10 | Create | - | - | REQ_Submitted |
| 20 | Review | Technical_Review | IT_Reviewers | REV_Task_Assigned |
| 30 | Approve | Final_Approval | FIN_Approvers | APP_Approval_Required |
| 40 | Deploy | Deploy_Production | - | DEP_Success |
Parallel Review Workflow
graph LR
A[Start] --> B[Create]
B --> C[Technical Review]
B --> D[Business Review]
C --> E[Consolidate]
D --> E
E --> F[Approve]
F --> G[Deploy]
Configuration:
| Stage | Action | Tasks | Notes |
|---|---|---|---|
| 10 | Create | - | Request creation |
| 20 | Review | Tech_Review, Bus_Review | Parallel tasks |
| 30 | Review | Consolidate_Review | Merge feedback |
| 40 | Approve | Final_Approval | Single approval |
| 50 | Deploy | Deploy_All | All environments |
Validation-Heavy Workflow
graph LR
A[Start] --> B[Create]
B --> C[Validate]
C -->|Pass| D[Review]
C -->|Fail| B
D --> E[Approve]
E --> F[Deploy]
Configuration:
| Stage | Action | Task | Script | On Failure |
|---|---|---|---|---|
| 10 | Create | - | - | - |
| 15 | Validate | Data_Validation | VALIDATE_ALL | Return to Create |
| 20 | Review | Review_Valid_Data | - | - |
| 30 | Approve | Approve_Changes | - | - |
| 40 | Deploy | Deploy_Metadata | - | - |
Task Configuration Examples
Review Task with Multiple Approvals
Name: Committee_Review
Action: Review
Security Group: Review_Committee
# of Approvals: 3
Email Template: REV_Committee_Required
Allow Requestor to Review: No
Allow Reviewer to Cancel Lines: Yes
Custom Validation Task
Name: Complex_Validation
Action: Custom
Custom Function: VALIDATE_COMPLEX_RULES
Email Template: VAL_Results
Description: Runs complex cross-dimensional validations
Notification-Only Task
Name: Stakeholder_Notification
Action: Notify
Email Template: NOTIFY_Stakeholders
Security Group: All_Stakeholders
Description: Informs stakeholders of pending changes
Best Practices
1. Workflow Design
- Keep It Simple - Start with basic workflows and add complexity as needed
- Clear Naming - Use descriptive names for workflows and stages
- Document Purpose - Maintain descriptions for all components
- Logical Flow - Ensure stages follow business logic
- Test Thoroughly - Validate in non-production first
2. Task Management
- Reusable Tasks - Create generic tasks for multiple workflows
- Consistent Naming - Use prefixes (REV_, APP_, DEP_)
- Template Association - Always assign email templates
- Security Groups - Define clear group responsibilities
- Approval Counts - Set appropriate approval thresholds
3. Stage Configuration
- Number Spacing - Use increments of 10 for flexibility
- Action Alignment - Match stage action to task actions
- Freeze Judiciously - Only freeze when necessary
- Validation Early - Place validation stages early
- Deploy Last - Deployment should be final stage
4. Performance Optimization
- Limit Stages - Keep workflows under 10 stages
- Efficient Scripts - Optimize Logic Builder scripts
- Parallel Tasks - Use parallel reviews when possible
- Batch Deployments - Group deployments for efficiency
- Archive Old Workflows - Disable rather than delete
Troubleshooting
Common Issues
| Issue | Cause | Solution |
|---|---|---|
| Workflow not visible | Not enabled or visible | Check workflow properties |
| Task not executing | Security group not assigned | Verify task security configuration |
| Email not sent | Template not assigned | Check task email template |
| Cannot delete workflow | Active requests exist | Complete or cancel pending requests |
| Stage order wrong | Stage # not sequential | Review and adjust stage numbers |
| Approval stuck | Insufficient approvers available | Check group membership |
| Custom task fails | Script error | Debug in Logic Builder |
Workflow Monitoring
Monitor workflow execution:
- Dashboard - View request status
- Audit Trail - Track stage transitions
- Email Logs - Verify notifications
- Error Logs - Check for failures
Testing Workflows
- Create Test Request - Use test data
- Progress Through Stages - Verify each stage
- Test Rejections - Ensure proper routing
- Verify Notifications - Check email delivery
- Validate Deployment - Confirm target updates
Important Considerations
In-Flight Requests
Workflow changes don't affect existing requests. A snapshot of the workflow is taken at request creation.
Security Context
Task security is evaluated at runtime based on current group membership, not snapshot.
Emergency Changes
Keep an "Emergency Approval" workflow with minimal stages for urgent changes.
Multi-Environment Workflows
Configuration Components
- Shell Applications - Logical representations of non-production apps
- Environments - Define deployment tiers (DEV, UAT, PROD)
- Deploy Stages - One per environment
- Deploy Tasks - Environment-specific tasks
- Environment Mapping - Link applications to environments
Example: Three-Tier Deployment
graph LR
A[Create] --> B[Review]
B --> C[Approve]
C --> D[Deploy DEV]
D --> E[Deploy UAT]
E --> F[Deploy PROD]
Configuration Steps:
- Create environments with deployment order
- Create shell applications for UAT/DEV
- Add deploy stages to workflow
- Create deploy tasks per environment
- Map applications to environments
Integration Points
Email Templates
Tasks use email templates for notifications: - Assign templates to tasks - Use variable tags for dynamic content - Configure success/failure templates
Logic Builder
Custom tasks and validation scripts: - Pre/post processing scripts - Complex validation logic - Integration with external systems
Security
Workflow security integration: - Security classes control workflow access - Groups assigned to review/approve tasks - Member-level security respected
Deployment Manager
Deploy tasks trigger deployment: - Direct deployment to target - File generation - Interface table updates
Related Topics
- Email Templates - Configure task notifications
- Security Groups - Assign to review/approve tasks
- Logic Builder - Create custom task scripts
- Deployment Manager - Configure deployment tasks
- Multi-Environment Setup - Deploy to multiple tiers
