Swimlane

Bundles Tasks which particular worker will be in charge of. In principle, a single user handles Tasks in a Swimlane. The Operator is set using the information of Organization and Role and the relationship with the Operator of other Swimlanes.

Configs: Property
  • Name
  • Note
  • (specified User/Org, etc.)
    • Edit
Configs: Operator
  • (Operator)
    • (Operator Setting)
    • (remove)
  • (Option to exclude)
    • User who accepted (Swimlane) are excluded
  • (Option to assign)
    • All tasks are handled by the same one user / the user in charge of the first task.
    • The operator of each task can be made a different user. For each task, candidates will be asked for acceptance.
Configs: Operator Setting
  • User
    • (Type name / email address.)   (Search)   (Clear)   (Select yourself)   (Select from Organization Tree)
  • Organization
    • (Type name / email address.)   (Search)   (Clear)   (Select your main Organization)   (Select from Organization Tree)
    • (conditions)
      • Leaders or staff members who belong to this
      • Leaders who belong to this
      • Staff members who belong to this
      • Leaders or staff members who belong only sub organizations of this
      • Leaders who belong only sub organizations of this
      • Staff members who belong only sub organizations of this
  • User specified by Data Item
    • (User/Organizational-type Data Item)
  • Swimlane
    • (Swimlane)
    • (conditions)
      • a user who operated tasks in this swimlane
      • The same user as
      • Leaders or staff members in the SAME organization with
      • Leaders who belong to the SAME organization with
      • Staff members in the SAME organization with
      • Leaders or staff members in the PARENT organization of
      • Leaders who belong to the PARENT organization of
      • Staff members in the PARENT organization of
      • Leaders or staff members in the UPPER organization of
      • Leaders who belong to the UPPER organization of
      • staff members in the UPPER organization of
  • None (Only Role)
  • In addition to the above, add conditions about Role.
    • (Type name.)   (Search)   (Clear)
    • Add
  • (Added Role name) / (remove)

Capture

Notes

  • Multiple rules for defining Operators (candidates to be offered) can be specified
  • Users who are in charge of processes on other swimlanes can be excluded as processors
  • Different users can be assigned to be in charge of different processes
  • The maximum number of target Users to be the Operator (candidate) is 1000
    • If the number of target Users who are candidates for processing exceeds the upper limit, the Task will not be Offered/Allocated to anyone and will be an error Task

See also

2 thoughts on “Swimlane”

  1. Pingback: User-Type – Questetra Support

  2. Pingback: Organization-Type – Questetra Support

Comments are closed.

%d bloggers like this: