Please give details of the problem



    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


    To trigger a subprocess, select Activity (1) > Functional tab (2) > Type : 'Subprocess' (3) > then go to tab 'Implementation of a sub-process' (4)


    Then click on 'Search for sub-processes in the directory' link (1), it will open the list of processes in the project and subprojects. Select the subprocess to be triggered (2) and click 'Ok' (3)


    Then you should see this screen:


    Different properties are available:

    • 1 - Nested process : best practice is to not tick this option. This will only be used in very specific cases (father and subprocess share mesures for example). If ticked, you'll see father process' computed parameters are mixed with son process' ones.
    • 2 - Send variables : if ticked, all the computed parameters defined in the father process will be passed as input of the son process
    • 3 - Inject results : if ticked, when the son process is completed, all the computed parameters defined in the son process are passed to the father process
    • 4 - Run as : you can choose who will be the P_initiator of the son process : is it the P_initiator of the father process ('Process initiator') or P_user ('Last process modifier')
      • Keep in mind that the P_initiator of the son process must belongs to its start lane (cf below), otherwise you'll get an error message.


    Best practice is to only pass the needed variables from the father to the son process, and to only retrieve the needed variables from the son to the father. So if you follow this practice, 'Send variables' and 'Inject results' are not ticked.

    Choose the variables to pass from the father to the son process

    You can specify a set of mandatory parameters to be passed as input of the son process.

    It implies:

    • you can't trigger the process if they are not defined as input parameters
    • if a father process triggers the son process, even if 'Send variables' is unticked, these parameters will be passed

    Let's configure these 'required input parameters':

    Open the son process, and click on 'Input'


    It will open a new window. Click on 'Add a variable' (1), enter a variable name (2), and its type (3)


    Note about the type:

    • Value : if the variable is a string, a number, a boolean
    • Object : if the variable is a array, a json structure

    If you choose the wrong type, eg: you specify 'Value" for a json variable, it will lead to an error when triggering the process.

    Then click 'Ok' (4), and save your process.

    Now try to plug again the son process to the father process:

    Click on the activity in the father process (1), go to input variables tab (2)


    You now see all the 'required parameters' you configured in the son process : array_phone_number, firstname, lastname, plus 2 global variables you can leave as it is(P_mode & P_version).

    Now you can untick 'Send variables' in the 'Implementation of a sub-process' tab, as these parameters will be automatically passed


    Note : this best practice is to optimize your process design, but here are other benefits:

    • As you listed required parameters for the son process , you can't forget to first define them in the father process before passing them to the son process
    • As you only pass a predefined list of parameters, when you're doing supervision of sub-process instances, you're not flooded with many other parameters you don't wantto
    • When you click on launch test (1) , you'll be able to see this parameters in the testing console. So to do unit tests of the son process, you'll definitely save time.



    Choose the variables to pass from the son to the father process

    On the father process, untick 'Inject results'


    If unticked, when the son process is completed, no parameters of the son process will be passed to the father process.
    But you can inject them manually, one by one.

    Open the activity in the father proces (1), go to 'Output variables' tab (2), add rows by clicking on 'Add' (3) and enter name and value of the parameters to create (4)


    Name : the name of the variable to create
    Value : its value. Syntax is ${P_result.name_of_the_variable_defined_in_the_son_process}

    Save the father process, you're done.