Workflow

workflow is a powerful automation feature in turbine that enables you to create dynamic, conditional logic for controlling how application records are presented and behave every application in swimlane turbine has a workflow every applet also has a workflow workflow is a series of conditional decision points and resulting actions that automate the presentation of record fields and layout you build the workflow like a tree, with one or more branches each branch is conditional and can consist of multiple conditions and actions activity on individual records catalyzes workflow execution key concepts workflow a tree like structure of conditions and actions that automate record presentation conditions decision points that evaluate field values and determine which path the workflow follows actions operations that modify field visibility, editability, requirements, values, and layout stages groups of conditions and actions that execute together branches conditional paths in the workflow tree that execute based on condition evaluation what is workflow? workflow is a series of conditional decision points and resulting actions that automate the presentation of record fields and layout you build the workflow like a tree, with one or more branches each branch is conditional and can consist of multiple conditions and actions purpose workflow enables you to dynamically control field visibility show or hide fields based on record data modify field editability make fields read only or editable based on conditions set field requirements make fields required or optional dynamically automate field values set field values automatically based on conditions control layout presentation show, hide, collapse, or expand sections filter selection options dynamically filter dropdown/selection field options control time tracking enable or disable time tracking for records when workflow executes workflow is triggered by various record activities opening a new record form when a user opens a form to create a new record saving a new record when a record is saved for the first time opening an existing record when a user opens an existing record modifying an existing record when field values change in an existing record record creation by playbook when a playbook creates a new record record modification by playbook when a playbook modifies an existing record record creation by remote client when a remote client tool or script creates a record record modification by remote client when a remote client tool or script modifies a record workflow components turbine workflow consists of conditions decision points in the workflow workflow actions singular items to be accomplished by workflow conditions conditions are decision points in the workflow that evaluate field values and determine which path the workflow follows each condition tests a specific field against criteria using operators condition types field based conditions evaluate field values (equals, contains, greater than, etc ) reference field conditions evaluate referenced record fields or record counts default actions condition always evaluates to true (used for unconditional actions) condition evaluation and logic all conditions must be true for the stage to execute or logic any condition being true causes the stage to execute nested conditions conditions can be grouped and nested for complex logic for detailed information on creating and configuring conditions, see docid\ cize3fnskdgv7 jge 4u2 actions actions are operations that modify record presentation and behavior each action performs a specific task when its associated conditions are met available action types the following action types are available in the workflow action dropdown set field value automatically set a field's value enter a value directly or use field references in text fields for date fields, you can set specific dates or use date modifiers (previous, current, next) only executes once per workflow run set field read/write make fields read only or editable states lock (read only) or edit (write) cannot be applied to history, json, created/updated dates, created/updated by fields set field required/optional make fields required or optional states required or optional cannot be applied to history, reference, comments, attachments, json, created/updated dates, created/updated by fields filter selection options dynamically filter available options in selection fields filters values list fields based on conditions modify layout show, hide, collapse, or expand fields and sections for sections show, hide, collapse, expand for fields show, hide only can be applied to all fields and sections trigger notification send notifications when conditions are met configure notification templates and recipients can be used to alert users about record state changes trigger integration execute integration actions when conditions are met run integration tasks as part of workflow execution available within repeat stages for iterative integration execution export and email record export a record using a formatted export template and email it select an export template to format the record configure email recipients and subject useful for generating reports or sending formatted record data toggle time tracking for record enable or disable time tracking for records enable or disable time tracking for the record controls whether time can be tracked on the record for detailed information on configuring actions, see docid\ qlsozu9hgudf psgd9b1f stages stages are containers that group conditions and actions together each stage contains one or more conditions that determine if the stage executes contains one or more actions that execute when conditions are met can be nested within other stages for complex workflows can be disabled without deletion workflow structure workflow is structured as a tree workflow start ├── default actions (always execute) ├── stage 1 (conditional) │ ├── condition(s) │ ├── action(s) │ └── nested stage(s) ├── stage 2 (conditional) │ ├── condition(s) │ └── action(s) └── workflow execution summary there is no set order of how a workflow is executed the processing first evaluates all of the conditions in the workflow, and then determines a list of actions that are dependent upon how the conditions are met the process then executes the defined actions for detailed information on workflow execution, see docid\ v3iqarormfioie8d3yh4i related documentation getting started with workflow learn how to access and use the workflow builder creating conditions detailed guide on creating and configuring conditions workflow actions complete guide to all workflow action types advanced workflow topics execution details and advanced concepts workflow best practices design patterns and best practices troubleshooting workflows common issues and solutions