Difference between revisions of "Process Models"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 1: Line 1:
'''{solution} > Designer > Processes''' (solution-global processes)<br>'''{solution} > Designer > Case Types > {case type} > Processes''' (case-specific processes)
'''{solution} > Designer > Processes''' (solution-global processes)<br>
'''{solution} > Designer > Case Types > {case type} > Processes''' (case-specific processes)
__TOC__
__TOC__
==About Processes==
==About Processes==

Revision as of 22:25, 9 July 2012

{solution} > Designer > Processes (solution-global processes)
{solution} > Designer > Case Types > {case type} > Processes (case-specific processes)

About Processes

Processes are generic procedures that can be attached to Case Activities. Using Processes, you can define the procedure once, and then use it in multiple Case Types. For example, a Process like "Review the Application" can be defined for a Banking Solution, and then reused in Activities for different kinds of Cases--say, Consumer Loans and Commercial Loans.

Similarly, a generic procedure can be defined for a particular Case Type, and then be used in different activities associated with that kind of Case.

Working with Processes

Creating or Modifying a Process

To create or modify a process:

  1. From the Processes tab, click [New Process] or click an existing Process.
    The Process Editor opens.
  2. Drag elements from the sidebar into the main panel
  3. Click a task in the main panel to a display several convenience elements:
    • XOR Connector - An XOR gateway is added to the process (see below), with a connection from the task
    • End Event - An End Event element is added to the process, connected to the task
    • Cancel Timer - A Cancellation Timer is automatically added to the task (see below).
    • Arrow - Click the arrow, and then click another element. A connection is drawn between them.
  4. Press Ctrl+S or click the Save icon to save your changes and close the window, or simply close the window to exit without saving changes.
    ProcessIcon Save.png

Process Elements

  • User Task - This is a task that will be carried by a user. (You can add instructions to help them out.)
    Requirements:
  • Define either the Role(s) that will be responsible for the task, or the Rule Set that will determine the owner. (You cannot save the task until a mechanism for determining its owner has been established.)
  • Define the Form the task owner will use to view (and possibly update) the Case the task is part of. (The default Form can be used, but it is likely be more helpful to restrict the view to the information needed to carry out the task.)
  • Email Task - Send an email
  • Content Generation Task - Create a document, optionally using one of the Document Templates
  • Execute RuleSet Task - Execute Rules in a Rule Set, to carry out a number of tasks
  • Data-based XOR gateway - Do one task or another--never both.
  • Parallel Gateway - Allow tasks to proceed in parallel.
  • Start Event - Specify the starting point for the process. (The start point is required.)
  • Cancel Timer - Specify an interval after which the task will be automatically canceled.
  • Reminder Timer - Specify an interval after which a reminder will be sent to the task owner(s).
  • End Event - Specify an endpoint for the process. (At least one end point is required.)
  • Sequence Flow - Draw a connector between two tasks, to create a sequence