User Guide for PaperSave Application System > PaperSave Configuration > PaperSave Settings > Workflows > Workflow 1.0

The Toolbox in the Design Screen contains pre-defined States and Activities that you can use to build a Workflow. Some of these States and Activities are discussed below and in later sections.

State Activity: This is the activity you will be using to create basic steps within your Workflow and Event-Driven Activities.

Event-Driven Activity: These activity define events within State Activities. PaperSave includes a few extra pre-defined State Activities for common functions to save time which are known as Composite State Activities. There are three composite state activities as mentioned below:

•

Created State Activity: A State Activity containing an Event-Driven Activity with a queue. It contains "Create Event" and "Set State After." The Properties pane includes a Target State to identify the State you want the item to go to upon the Create Event. (Right-clicking on a state in the Properties pane and clicking on Set as Initial State will set the Initial State of the Workflow.)

•	Review State Activity: Pre-set to contain Approve and Reject Event-Driven Activities.

•	Data Entry State Activity: Pre-set with Approve, Reject, and Associate activities.

All pre-set states have pre-set container activities you can load from the Properties pane to direct the action/path. Each Event Container contains little steps which appear like a mini-workflow. These are used to define the steps that occur when an event is triggered.

You can use the activities and the events in the Toolbox by simply dragging them into the State Machine Workflow area. Using these activities you can create various states that include different conditions which can be used for processing the documents.

Following is the list of Static Constants which can be used while writing a Workflow condition:

1.	"ps_smtp_ps"

2.	"ps_smtpuser_ps"

3.	"ps_smtppassword_ps"

4.	"ps_fromemail_ps"

5.	"ps_smtpport_ps"

6.	"ps_queueitem_id_ps"

7.	"ps_queue_id_ps"

8.	"ps_queue_name_ps"

9.	"ps_queueitem_filename_ps"

10.	"ps_document_id_ps"

11.	"ps_document_clickonce_ps"

12.	"ps_user_ps"

13.	"ps_currentstate_ps"

14.	"ps_parentid_ps"

15.	"ps_documenttype_ps"

16.	"ps_transactiontype_ps"

17.	"ps_module_ps"

18.	"ps_hostapplication_ps"

19.	"ps_connectionstring_ps"

Example: profile.ps_smtp_ps

profile.ps_queue_id_ps

The above constants can be used in writing conditions for various events, such as the OnEnter Event, OnChange Event, and OnExit Event. The OnEnter Event will perform certain activities once you enter the values to the profile fields for which the OnEnter Event condition is applied. Similarly, by providing a particular script for the OnChange Event and OnExist Event, you can also perform certain activities when the values of profile fields change or when you exit a specific profile field.