Call the LongJump Sales Team at
(800) 886-9028 to request a demo.
Introduction to Workflow Designer
For Full Screen viewing, roll over the image above and click on the icon top right corner,
or select Menu » Full Screen. To exit Full Screen viewing, select Menu » Exit Full Screen.
Hello, and welcome to our quick tour of the Workflow Designer in LongJump.
Here, you'll see how easy it is to build a workflow and automate your business processes.
When we open the Workflow Designer, we see that Start and End states are already in place.
Every workflow has a start point and an endpoint that define the beginning and end of a particular request or task
The Start and End States each have settings that you can modify
A state is a condition of a request.
Some examples might be: submitted, pending approval, approved, rejected.
To add a state, we click and drag the state icon to the work area, then drop it in place.
A dialog box opens, where we can specify:
the name of the state
editing rights for the Workflow Initiator
Workflow Decision Maker(s) – folks who are authorized to make the decisions
Setup email notification, task creation or editing rights options
Or, select a Data Policy
Next, we will add an Action.
Actions are tasks and activities that carry the request to next step/state.
Some examples are: Approve Request, Accept Proposal, Hold for consideration, Approved, with Changes.
To add an action, click the action icon, drag it to the first state and release the mouse button, then drag it into place at the second state, and click again.
A dialog box opens, where we can specify:
the name of the action
notify the workflow initiator after the decision has been made
add criteria -
If a record meets the criteria, the process moves forward. If the record does not meet the criteria, no further action is taken
Let’s skip ahead and see the completed workflow
In this example, we see a Simple Approval Process. Once the request is submitted, one of three actions can be taken: Approve, Approve with Changes, Reject [ at this point, the workflow ends, the initiator is notified and no further action is taken].
Let’s see workflows in action
When we open a request record in the Workflow Approver’s screen, we see the pending actions (at the top), and workflow history (at the bottom).
The workflow approver can accept, reject, or accept with changes.
Note that the pending action buttons are built from the actions we chose in the workflow.
In the approver’s home page, we can see report-based widgets with a piechart or tabular examples of pending expenses.
