×

Please give details of the problem

Docs

Find

    Developer Guide

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

    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