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
      • (list)
    • Organization
      • (Organizational 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.
    • Add
      • (Role)
      • (remove)

Capture

Notes

  • Multiple rules for defining Operators (candidates to be offered) can be specified
  • Possible to exclude users who operated Tasks on other Swimlane from candidates
  • Possible to offer to candidates at each every 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: