Swimlane

/ BPMN Icons

Overview

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

  • mode_edit_outline Name
  • mode_edit_outline Note
Configs: Operator

  • (Operator)
    • format_list_bulleted Operator setting rules (default: App create User) / edit (edit)　delete (delete)
      • crop_din Add
      • crop_din Show Candidates
        • format_list_bulleted (Users who are capable of being the Operator)
  • check_box (Option to exclude)
    • Users who accepted Tasks in Swimlane arrow_drop_down (Swimlane name) are excluded
  • (Option to assign)
    • check_circle All tasks are handled by the same one user / the user in charge of the first task.
    • check_circle The operator of each task can be made a different user. For each task, candidates will be asked for acceptance.
Configs: Operator Settings

  • check_circle User
    • mode_edit_outline Search for user  search (Search)  emoji_emotions (Select yourself)  account_tree (Select from Organization Tree)  close (Clear)
  • check_circle Organization
    • mode_edit_outline Search for organization  search (Search)  emoji_emotions (Select your main Organization)  account_tree (Select from Organization Tree)  close (Clear)
    • arrow_drop_down (conditions)
      • [Members who belong to this / Members who belong only sub organizations of this]
    • arrow_drop_down (Position)
      • [(N/A) / (With Position) / (No Position) / (Registered Position name)]
  • check_circle App Authorization
    • arrow_drop_down (conditions)
      • [App Administrator / Process Manager]
  • check_circle User specified by Data Item
    • arrow_drop_down (User/Organization-type Data Item)
      • (User-type)
      • (Organization-type)
        • arrow_drop_down (conditions)
          • [Members who belong to this / Members who belong only sub organizations of this]
        • arrow_drop_down (Position)
          • [(N/A) / (With Position) / (No Position) / (Registered Position name)]
  • check_circle Swimlane
    • arrow_drop_down (Swimlane name)
    • arrow_drop_down (conditions)
      • The same user as a user who operated tasks in the swimlane (the same organization)
      • Members in [the SAME organization with / the PARENT organization of / the UPPER organization of] a user who operated tasks in the swimlane
    • arrow_drop_down (Position)
      • [(N/A) / (With Position) / (No Position) / (Registered Position name)]
  • check_circle None (Only Role)
  • In addition to the above, add conditions about Role.
    • mode_edit_outline (Type name) search (Search)  close (Clear)
    • crop_din Add
  • Added Role name /　delete (Delete)

Capture

Property
Operator Settings

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.

Scroll to Top

Discover more from Questetra Support

Subscribe now to keep reading and get access to the full archive.

Continue reading