×

Please give details of the problem

Docs

Find

    Developer Guide

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

    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