Workflow Cheat Sheet
1. There are two Public Folders (under All Public Folders) where Workflows should be kept: a. DevWorkFlow b. ProdWorkFlow 2. Each Folder minimally contains the following subfolders: a. Completed Flows (a holding place, if needed, for completed workflows) b. Forms (folder of forms used in flows) c. Running Flows (a folder where flows can be opened to debug during runtime) d. Scripts (VB or Java Scripts are kept here) e. Templates (the folder where the workflow templates are kept) 3. When creating a new workflow template, DevWorkFlow/Templates should be highlighted so that the new template will be created there (and later it should be moved to ProdWorkFlow/General/Templates, for example). Attention should be paid that whatever is the current folder – that is where the template will be created! 4. When creating a new workflow template, the first thing that appears is the “Flow Template Properties” window. On the General tab, the “Start flows using this server:” should have icXpertFLOW Server selected (from Global Address book) and the “Place started flows in this folder:” should Browse to All Public Folders/ DevWorkFlow/Running Forms (this will be changed in production). If necessary, you can get back to this window by clicking on the eyeglasses icon on the toolbar. 5. Scripts can be created or called up in the Scripting tab. They should be saved in the DevWorkFlow/Scripts subfolder. When the template is moved to production, the script also needs to be moved, and then “repointed” to. What this means is that after the template and script are moved to ProdWorkFlow, the template must be reopened, the Scripting tab selected, the script deleted (X) and chosen (>) from the new folder it exists in. 6. Forms can/should be created in the Start step, Forms tab. Choose Lexign ProForm (>), New and save it in DevWorkFlow/Forms. This can then later be selected as a form within the current template (or even from another template). The same applies to forms as does to scripts when moving from DevWorkFlow to ProdWorkFlow. Once moved, open the template in ProdWorkFlow , change the form so that it points to the form in ProdWorkFlow. Apply the change. 7. (Java) Form Scripts can be created while the form is being edited by clicking on File, Form setup…, Form Scripts. Field scripts (within the form) can be created by double clicking on the field, click on the Field Scripts tab and creating the script in the appropriate routine. Also, while that window is open, the Authoring tab can be selected to name the field (i.e. KF:ApplicationData NameIn). Other possible selections on that tab are Type (String, Integer, etc.), Visible, Enabled, Must Fill (see InStateTravelRequestForm). 8. Prerequisites for a single addressee can be Simple Test for previous step to be done. However, on a “distribution group”, use the Voting button and test VoteCount() is at least (>=) 1. Equal to (=) 1 doesn’t appear to work! 9. For example, see DevWorkFlow/Templates/In State Travel Form Flow. 10. Proper Security needs to be set up on the subfolders (i.e. Finance, General, etc) with level of “Editor” so that only the people responsible have the authority to look at the email workflows. Each subfolder (Completed Flows, Forms, etc) can have their own security level permissions, if necessary!