Workflow Editor

the workflow editor enables users to create new workflows and modify existing workflows understanding the workflows table we can observe that each record represents a workflow each workflow contains the following workflow – the name of the workflow connections if there are connections within the workflow, you will see them listed here for instance, in the workflow “salesforce won >priority,” you can see that there are two connections one for priority and one for salesforce last run – the last date and time when the workflow ran created – the user who created the workflow and date and time when the workflow was created updated – the last user who updated the workflow and date and time when the workflow was updated status – here you can see if the workflow is activated if active, the color will be black; otherwise, it will be gray edit workflow page on the sidebar, click on the “workflows” option hover over the workflow you want to edit and click on the 3 points now click on "edit" workflow settings this section defines the general configuration of the workflow, including its name, description, and connected apps it also controls execution settings such as concurrency limits and the maximum number of consecutive failures before the workflow stops you can access workflow settings from inside a specific workflow in the top bar, click the icon this will open the workflow’s general configuration panel, where you can manage the name, description, connected apps, and execution settings info the info section allows you to define the workflow’s name and description and view metadata such as creation date, last update, and connected applications name defines the workflow name it can also be edited directly from within the workflow editor itself description allows you to add a short explanation of what the workflow does for documentation purposes concurrency determines how many runs of the workflow can execute simultaneously apply concurrency limits to waiting workflow when enabled, concurrency limits will also apply to workflow runs that are in a waiting state consecutive failures limit sets the maximum number of consecutive failed runs allowed before the workflow is automatically stopped the maximum is 10/ create displays who created the workflow and when this information is also visible on the main workflows home page updated shows who last updated the workflow and the date of the update this is also available on the https //app engini io/workflows home page connections lists the apps and connections used in the workflow this information can also be viewed from the https //app engini io/workflows home page save saves any changes made in the https //app engini io/workflows settings add activity engini activities represent individual steps in your workflow there are two types of activities available trigger – appears only one time in each workflow and always at the top the trigger is what initiates the workflow run action – there is no limit to the number of actions you can add to your workflow to add an action, follow the next steps if you want to add an action between two existing activities, hover over the arrow between the two actions and click on the plus icon that appears you can choose to add a sequential action that will appear before the lower of the two activities – click on “add action” you can choose to add a parallel activity – click on “add as parallel branch” if you want to add an action after the last action you added, click on the “next step” button choose the engini software and click on the name of the action you want to use for more information on the types of actions for each software, see the "apps" delete activity stand on the action you want to delete click on the trash option copy to clipboard stand on the action you want to copy to clipboard click on the “copy to clipboard” option the action is created disconnected from all other actions it is now possible to attach the copied action to the rest of the workflow skip action you can choose to skip an action in your workflow to do so, follow these steps stand on the activity you want to skip click on the “skip action” option rename activity click on the three dots on the right side of the activity click on the “rename” option the name field will be opened for editing, and you will be able to change the name of the activity when you finish editing the activity name, click outside of the input field and the name will be saved automatically note that if you won’t save the workflow the name change won’t take effect refresh the connection if you updated fields or objects in your software after the activity was created you can “refresh” the connection, and then you will be able to use the fields or objects you updated click on the activity click on the three dots on the right side of the activity click on the “refresh” option configure run after you can set a activity to run after the previous neighboring activity has succeeded or failed the action will work only after the success or failure of the action before it by default, each activity is configured to run after previous neighboring activity has succeeded to change the default settings, do the following click on the three dots on the right side of the activity click on the “configure run after” option after clicking on the option, the display of the activity will change and you can define if you want the current activity to work only after the previous activity succeeded, failed or both of them click the “done” button to return the previous activity view configure context the context field is a field that can be populated at runtime this is a global variable in the workflow that you can populate in different activities throughout your workflow, and the value that will be displayed to the user is the last value that was populated in this variable the value received in the field can be seen in the history table and thus allow the user to easily identify which run history to open click on the three dots on the right side of the activity click on the “configure context” option after clicking on the option, the display of the activity will change and you can define the context click the “done” button to return the previous activity view configure retry policy the retry policy is a mechanism designed to handle temporary failures by automatically re executing a specific action before the workflow proceeds to the next steps click on the three dots on the right side of the activity click on the “configure retry policy” option define the following fields max retries sets the number of repeat attempts (0–100) the system performs if the initial action fails if set to 0 , no retries will occur if set to 1 , a total of two attempts will be made (the initial run plus one retry) in the event of a failure delay between retries defines the waiting period between retries, delays of 30+ seconds put the workflow to sleep until the next try retry conditions (optional) specifies particular rules for when a retry should occur, if left blank, the system retries on any failure done saves and activates the configured retry logic for this specific action dynamic connection enable use of several different connections within the same activity click on the 3 dots inside the action on the right side of the activity again inside click on the 3 dots choose "dynamic" click on the empty field near the connection label select the relevant connections for this activity you can define conditions with https //app archbee com/public/preview ixqqblwfxopjg0nave78y/preview o3kkbgi5xnqf yvnuqkcv#ca 5p that will choose which connection to use in this activity finalize connection selection or cancel dynamic connection click “done” to save your selection click “cancel” if you don’t want to save your selection workflow edit top bar save when you’re done editing your workflow, click the save icon to save your progress the workflow isn’t saved automatically if you have unsaved edits and you try to leave the page, to restore previous version or to run a workflow, engini will display the unsaved changes dialog you can then choose from the following options leave without saving to leave without saving save to keep your new edits and proceed to the page you wanted to navigate to x to dismiss the dialog and remain on the page in addition, if you try to access another page without saving your changes in engini, the system will display the following message this is an extra layer of protection to ensure you don’t lose your work unintentionally you can choose to leave the page or remain on the engini page by clicking cancel export allows you to download the workflow configuration file so it can be imported into another environment or used as a backup after clicking export , the workflow is downloaded to your computer as a json file you can then refer to the https //app archbee com/docs/ixqqblwfxopjg0nave78y/qekap xmuf1qqexhxggoz guide (link here) to learn more about how to use it restore previous versions of workflows over 45 days will be automatically removed if you want to restore to a previous version, follow the next steps click on the restore icon located at the top bar choose the version you want to restore click on the run you want to run again click on "rerun" note in order to restore the workflow to the version you chose to display, you need to save the workflow using the save button on the top bar you can switch between versions freely as long as you haven’t saved the version you retrieved, you can always go back to the original workflow run run your workflow to ensure that all components are functioning correctly to learn how to run workflow click https //app archbee com/docs/ixqqblwfxopjg0nave78y/dpcb7xk1knjjeh0x 70rc using values from previous operations after you add an action, press on the text box to enter a value the pictures are for illustration only, it can be used in any activity choose the previous activity from which you want to take a value and press on the arrow next to it choose the value you want to use webhook metadata metadata can be useful for storing additional information about the object in a structured format if you would like to use the metadata of certain conector choose the action of the desired connector press on the arrow next to the “webhook metadata” choose the the data you need url the address where the webhook expects to receive http requests, it’s where the data will be sent after trigger method the http method used for sending data to the webhook endpoint headers\[] http request headers contain additional information related to the request itself query parameters\[] key value pairs, where the key identifies the parameter and the value is the information associated with that parameter url parameters\[] the additional information appended to a url that is sent to a web server as part of an http request body the request body contains data that the client wants to send to the server workflow status a workflow in engini has two types of states active or inactive active workflows run when their trigger is activated and also when you run them manually by testing them you can switch between the two statuses whenever you want (active workflows can become inactive and vice versa), by clicking the on/off button in the top bar to save the workflow status you have to save the workflow you can also change the workflow status from the details page of the workflow or from the workflow’s table