Workflow Template ID support for Demands

• Default Off (Configuration implementation required)

Who: Customer Admins, Demand Managers

Requirements: Configure ‘ats_config’ to achieve different stages based on the workflow template. Further, configure your desired workflow templates in your ‘demand_workflow_config’ settings.

What's new: This release introduces the ‘workflow_template_id’ field to external demand APIs and file ingestion schemas for CSV and XML formats. Previously, external systems couldn't set or update workflow templates for demands, limiting integration capabilities. Now, you can assign specific workflow templates to different demand types directly from your external HRIS or ERP systems. This maintains consistency across platforms and allows you to control which pipeline stages/stage views appear for specific workflows.

How it works: Include the workflow_template_id in your CSV or XML upload, or pass workflowTemplateId in your API request body when creating or updating a demand. The system applies the template and automatically updates the demand's pipeline stage views based on your configuration.