×

Please give details of the problem

Docs

Find

    Developer Guide

      1. Todo Validation
    1. Release Your User Login
    1. Markdown Template
      1. Backloop
      2. JavaScript Inclusion
      3. Task Reminder Email
      4. Variable Mapping
      5. SubProcess
      6. PDF
    2. Trigger
      1. Lock
      2. Dynamic Variable
      3. List 1000+ Objects
      4. JSONObject Creation
      5. JSONArray Conversion
      6. Number Currency Format
      7. Error Handling
      8. JSONObject Concatenation
      9. Freemarker Container Test
      10. Number Test
      11. Loop
      12. File Visibility
      13. List Hash Sequence
      14. Special Freemarker Characters
      15. Array To List
      16. Salesforce Computation
      17. Metadata
      18. JSONObject Keys Values
    1. Delegation
    2. Access Rights
    3. Dynamic Lanes
    4. Runtime Lanes
    5. Scripted Lanes
    6. Compound Organization Hierarchy
      1. Array From WS
      2. Column Inactivation
      3. Holidays
      4. List Reinitialization
      5. ArrayJSON to JSONArray
      6. Print JSONObject
      7. Invalid Fields
      8. Number Currency Format
      9. Google Tables
      10. Initialization Widget Date
      11. Date
      12. JQuery
      13. Round
      14. Inject JSONObject
      15. Label Modification
      16. Launch Process JQuery
      1. CSS Personalization
      2. CSS Examples
      1. Tags
      2. Retrieving Variables Values
      3. Dialog Window
      4. Autocomplete Widget
      5. JavaScript Report
      6. User Lane Picker
        1. Chart Dashboard Collection
        2. Chart Dashboard
        3. Report Chart
        4. Google Visualization
      7. Collection
      8. Dynamic List
      9. Summing Array
      10. API Listener
      11. File Preview
    1. Performance
      1. Custom Login Page
      2. Redirection ExecutionMode
      3. Mobile Devices
        1. homepage.js
        2. homepage.css
      4. Logout
      5. Header
      6. Menu Bar
      7. Information Tags
      8. Basket
    1. Mobile
    2. Offline
        1. Collections
          1. Process General Tab
            1. Process Step Output Variables
              1. Process Task Email Tab
              2. Process Task SubProcess Tab
              3. Process Task Functional Tab
              4. Process Task Connector Tab
              5. Process Task Manual Tab
              6. Process Task Loop Tab
              7. Process Task Script Tab
            2. Process Step Input Variables
            3. Gate
            4. Process Step Testing Variables
              1. Process Intermediary Event
              2. Process Timer Event
              3. Process Start Event
          2. Process Variables Tab
          3. Process Measures Tab
          4. Process Design
          5. Process Input Tab
          1. Organization
          2. Roles entities
          1. Project Collection Tab
          2. Project Definition Tab
          3. Version
          4. Project Versioned Files Tab
          5. Project Files Tab
          6. Project Description Tab
          7. Project Version Tab
          8. Project Rights Tab
          1. Connectors
          2. Providers
          3. Processes
          1. Composite API Configuration Tab
          2. Composite API Design Tab
        2. Custom Lists
        3. Revision
            1. Image Widget
            2. Spinner Widget
            3. FileUpload Widget
            4. Section Widget
            5. Multi Checkbox Widget
            6. URLInput Widget
            7. RadioButton Widget
            8. Array Widget
            9. Captcha Widget
            10. Checkbox Widget
            11. Report Widget
            12. Geolocation Widget
            13. Button Widget
            14. Custom Widget
            15. TextInput Widget
            16. Tree Widget
            17. List Widget
            18. StaticText Widget
            19. HTML Editor Widget
            20. JavaScript Widget
            21. Tab Widget
            22. HTML Widget
            23. ProgressBar Widget
            24. History Widget
          1. Web Interface Stylesheet Tab
          2. Web Interface Design Tab
          3. Web Interface Analytics Tab
          4. Web Interface Collection Tab
          5. Web Interface API Tab
          6. Web Interface Implementation Tab
          7. Web Interface JS Tab
        1. Scheduled Process
        2. Messages
        1. Configuration
        2. Users
        3. Usage
        1. Connectors
        2. Process Examples
      1. Customer Management
          1. Measuring
          2. Parameters
          3. Execution Path
          4. Runtime Users
        1. Web Interface Reports
        1. Files
        2. Home
        3. My Applications
      1. Collections To Array
      2. Collections BackOffice
      3. Collection JS Freemarker
      4. Collections To List
      1. Composite API Example
      1. Process Reporting API

    Compound Organization Hierarchy

    The objective of this tutorial is to address a common problem related to rights faced by process designers.

    When assigning manual tasks within a process, there are 3 options :

    • Task must be assigned to one person defined by a variable. In this case, you insert the variable name related to assignee's email address ${waiting_for} in "Assign to" field.
    • Task must be assigned to one person or a group of people previously defined. Among these people, the first responder will be the task updater. In that case, you must create a dedicated Entity or Role and insert these people into it. On process side, you shouldn't complete the "Assign to" field.
    • Task must be assigned to a group of people not previously defined: the group is defined directly in the process, depending on the attributes related to the process as well as the attributes related to users (i.e. User's metadata). In this case, this documentation proposes you a "Best Practise" based on two technologies - Dynamic Lanes and Scripted Lanes, nested to each other.

    This solution allows us to use the possibilities of RunMyProcess to answer to the customer's exact need. Imagine the following scenario: we have one manual task and multiple assignees that depend on the process attributes, as well as User Metadata and belonging lanes (refer to the image below).

    The two technologies we provide are the following :

    • Dynamic lanes that allow you to select a group of assignees, depending on the variables within the process. However, it will be needed to respect the lane determined by the dynamic lane.
    • Scripted lanes that enable you to auto populate lanes based on Users' Metadata and lane belongings. However, there is no possibility to link in process attributes.

    Example :

    In a cost validation process, we have a manual task that must be assigned to an Accounting department of a specified country/entity. Let's assume that the country is specified in the computed parameters of the Process Instance.

    • In your process design, insert the box related to the manual task into a "DYNAMIC ROLE".
    • Via a "SWITCH" script (inserted in "Assign to entity" field), you will define the dynamic role that decides which entity to address (directly country related entities).

    Code:

     1
     2
     3
     4
     5
     6
     7
     8
     9
    10
    11
    12
    13
    14
    <#switch COUNTRY>
        <#case "FRANCE">
            109371 <#-- Entity ID -->
            <#break>
        <#case "SWITZERLAND">
            109372
            <#break>
        ...
        <#case "BELGIUM">
            109374
            <#break>
        <#default>
            150832
    <#switch>
    
    • These entities will all be "SCRIPTED LANES" where the associated script will look like :

    Script:

    1
    2
    3
    ${DIVI=="BELGIUM" && is_user_n_lane(1234)}
    
    <#-- where DIVI is User metadata attribute and 1234 is "All Accounting - Accounting global" role associated to all accountants whatever the country -->
    

    Lanes_concrete_descr

    Finally, make sure you take into account the following :

    • "All Accounting" roles must be maintained by somebody into the organization
    • Users must be populated considering the metadata "DIVI" which is equal to a country name