sfPMS uses special ATC commands within workflow scripts as a means to tell the system to do specific things at specific times. By creating ATC workflow scripts, you can set up automatic workflow to run at specific times, for a specific document, or for certain documents that use predefined routes.
Workflow refers to the set of relationships between all the activities in a project, from start to finish. These activities are tracked by various Doc types, some of which trigger new activities during the course of their routing or when they are saved or their status changes to Pending, Approved or Closed.
Automatic workflows can include simple scripts to alter the workflow and even create new documents. For example, you might want a Project Setup document to use automatic workflow to create one or more Punchlist documents, each routed to the correct person. Or you might want your Pay Request document to create next month’s Pay Request with instructions not to send it to the appropriate person until three or four days before it is due.
We recommend that most, if not all, workflow scripts be created and managed through the Workflow Scripts tool, found on the System Admin Dashboard. You must have the SYS | Global Access role capability or the PAGE | System Admin Dashboard and PART | Maintain Workflow Script Library role capabilities to access this tool. In order to create the actual workflow scripts, whether on the Workflow Scripts tool, the Routes tool (on the Manage Dashboard) or a document’s route, you must have the DOC | Can edit workflow role capability. [See the Designing User Roles technical white paper.]
With the exception of scripts run by a route to “Spitfire”, workflow scripts run within the security context of the current user and are subject to the user’s permissions. The logic in the script can do things a user cannot, such as set a status code that is not displayed, but user permissions still apply.
