Serial Workflow (v8.xx)

Serial Workflow (v8.xx)

  • Within the serial Workflow the Project Leader plans the resources with Workload. Then they change the status in “To proof”. It is now possible for the Team Leaders to work on the Team Planner and accept / deny the planning. When they are done, it goes back to the Project Leader for a last checking before he / she accept the changes (or deny and such give it back “To proof”).

  • Here it makes sense to work with email notifications by changing the status. But other

  • problems might occur: In the Workflow below you will see, Cerri.com recommends that still the Author / Project leader (or at least only one responsible e.g. via a role) is responsible for the status “To proof” and NOT all Team Leaders. This allows easier working. Otherwise it will in reality take too long until everybody have approved.

  • Again it might be helpful for the Team Leaders to meet in a weekly meeting and assign the resources.

  • Remark, the serial workflow is not recommended by Cerri.com (but possible in from a technical point of view).

    • Related Articles

    • Workflow Status Definition (v8.xx)

      Once the workflow definition has been created, it is time to list all of the possible statuses a document can pass through when following the workflow. A best practise when going through this exercise is to define all workflow statuses on paper, and ...
    • Workflow Settings (Serial) (v8.xx)

      General Overview: STATUS 1 (Draft): General: Responsible Resources: Author/Project leader Next Status: To Proof Security Settings: Action: Run a formula @SetField("ReviewType"; ""); @SetField("ReviewStatus"; "") STATUS 2 (To proof): General: ...
    • Workflow Definition (v8.xx)

      To begin it is necessary to create a workflow definition to specify the type of workflow being created, i.e. Contract. Navigate to the [Setup & Administration] module of the 'Projects' database, [Setup] tab. Select «Workflow» from the «Setup» view. ...
    • Workflow Types (v8.xx)

      The workflow is an integral part of document management. It is the modeling of a work process that defines how documents inside a workgroup pass from one status & participant to another according to a predefined set of rules. These predefined rules: ...
    • Create Workflow Actions (v8.xx)

      In addition to creating the different statuses, it is also possible to create a series of actions to be triggered whenever a document enters, leaves or is saved in a new status. To define an action and all of its parameters: Navigate to the [Setup & ...