# Appendix I - Methodology

More than 90% of the development in Workflow Ascendant is done in classic Notes. While following are the basic steps, the best approach is generally to copy/paste/adapt existing generic State documents which you have already tested. The XPage layer is (optionally) added at the end of the process once you have an operational application for the Notes client. For your very first application, you will need to sign the model database, configure the basics in the Language document, set the basic Workflow - ACL Entries and create an agent log (optional).

1. Notes database. Make a Notes copy of the database according to your requirements (including modifying Page WA Left to reflect the name of your database).

2. Language document. In the Documents tab of the active Language document, set the Alias (how the process will be known to your end users) and corresponding Notes Form Name for each of the processes to be included in the database. Logging Type should be set to Verbose and Hide Workflow Tab to No.

3. Field and Role documents. Create these documents once you have identified the various profiles of those who will intervene in the various processes. Creating these first allows you to select these values from a list in the State documents (although that is strictly optional). Consider setting default values (a1/Horizon, blue/Horizon ...) in these fields for subsequent testing.

4. Notes Forms. Modify the existing Notes Forms (one per process) from existing ones forms:

   • Workflow Tab. Create all the Constraint fields defined in the previous step. Consider setting default values (a1/Horizon, blue/Horizon ...) in these fields for initial testing.

   • Fields. Create fields in the form which will affect the process (i.e., how documents are routed).

5. State documents. Create the State documents (always using the button Verify to verify that your definitions are coherent), concentrating on the basic manual and automatic routing rules:

   • The following RIs can intervene...

   • And forward to the following states...

   • Which will be displayed as...

   • The following state will be routed to automatically...

6. Notes workflow testing. Select the Verify button in the view to ensure that the process is coherent before testing. At the end of this step the basic workflow should be operational (note that the users placed as default values in Step 4 will be used, not those in the Field and Role documents).

7. Notes initialization testing. Include in each state document $created$ (one for each process) the routines you plan to invoke when a workflow document is created (e.g., #waInitModFields, #waInitModTabs, ...) in field The document will be initialized with the following stocked subroutine(s)... Remove the default values from Step 4 and verify that the expected users from Step 3 are correctly inserted into the appropriate fields on the Workflow tab (there is no need to test the workflow at this point).

8. Finalize Notes Forms. Create the rest of the fields in the Notes forms not completed in Step 4.

9. Control routines. Add any custom control routines to script library WA Application Specific and reference these (as well as any of those provided by default) in the various State documents.

10. Window dressing. Complete the State document Notifications and Actions tabs, as well as customizing presentation related information (Historical Description ...).

OPERATIONAL NOTES CLIENT WORKFLOW APPLICATION!

1. XPages components. Copy/paste XPages and Custom Controls to correspond to the Notes application created above.

2. XPages fields. Copy/paste fields into the appropriate Custom Controls.

3. Visibility. Apply mechanisms to selectively hide documents and/or portions of the workflow documents.

4. Deployment. Once you deploy applications, be sure to use design templates, naming them accordingly to facilitate design roll-back (e.g., MD.Promo.2018.02.15.ntf).

OPERATIONAL WEB CLIENT WORKFLOW APPLICATION!