...
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 | ||||
|---|---|---|---|---|
|
...
[TODO Add Video to show adding Job]
|
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. [TODO Add Video to show adding outer path]
| 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) | ||||||
|---|---|---|---|---|---|---|
|