...
The page Creating and Editing a Workflow page explains the screens and steps that are used to create a Workflow in general.
...
You can split the flow using an Exclusive Branch Connector (only one path taken) or a Parallel Branch Connector (all paths taken).
Before an Exclusive Branch Connector, you will usually have either an Asset Creation, Request Status, or Job Status connector. This ensures that the data values that will be used for the testing will be valid. You don’t want to test the results of an Inspection before the Inspection is completed!
To access a value in one node, the value must be listed on the output tab of a previous node.
Step 4: Change, Publish, Test, and Repeat
Once you have enough done you can test it, publish the design and test it using dummy data. Get a feeling for how it is working then you can go back and fix any issues and add more functionality.
...
The following videos will show you the steps we went through to add functionality to our example workflow.
| Widget Connector | ||||||
|---|---|---|---|---|---|---|
|
Points to remember from this video:
To put an unchanging link in an email add an Email connector and add the URL details in the button fields.
To put a link to an Asset, Job, or Request in an email, create a “Generate Link To …” node first and then add the Email connector. On the “Action Button Link” field change the field type from text to Parameter and select the newly generated link.
| Widget Connector | ||||||
|---|---|---|---|---|---|---|
|
Points to remember from this video:
You can split the flow using an Exclusive Branch Connector (only one path taken) based on almost any field in the user entered data for an Asset, Job, or Request. Using form data you can control more than two branches.
Combining Exclusive Branching based on Form Data along with Parallel Branching can create a complex sequence of work based on an initial inspection.
| Widget Connector | ||||||
|---|---|---|---|---|---|---|
|
Points to remember from this video:
When defining the job, we define offsets for start and stop dates and Gruntify calculates the absolute dates when the job is created.
Newly created jobs can be saved as Unassigned for manual updating or Queued ready to be picked up by a field team.
| Widget Connector | ||||||
|---|---|---|---|---|---|---|
|
Points to remember from this video:
Test all possible paths through the workflow.
The results are found in the Instances view.
Keep your test cases for next time.
Step 5: Trial,
...
Review, Improve
Keep repeating this process until you have good enough to use it with some real-world users. We suggest that you try out it with a trial group of users to start with and check the outcomes via the Instances view.
...
If you are making improvements to a workflow that is running okay, then can leave the workflow running while you work on the changes. Gruntify will autosave your changes, but the running version of the workflow will not be affected until you click Publish.
| Widget Connector | ||||||
|---|---|---|---|---|---|---|
|
Points to remember from this video:
Look out for issues when you start running it in Production. It could just be an odd behavior that a user notices.
Any issues found? Analyze and fix.
Like to see more?
For another example workflow, see Sample Workflow Date Time Comparisons.
Related articles
| Filter by label (Content by label) | ||||||
|---|---|---|---|---|---|---|
|