Please give details of the problem



    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. Roles Entities
          2. Organization
          1. Project Definition
          2. Versions
          3. New Version
          4. Version Management Log
          5. Access Rights
          6. Collections
          7. Versioned Files
          8. Files
          9. Description
            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. Implementation
          2. Design
          3. Collections
          4. Stylesheet
          5. JavaScript
          6. API Listener
          7. Google Analytics
          1. Process Design
            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
          2. General
          3. Input
          4. Variables
          5. Measures
          1. Connectors
          2. Processes
          3. Providers
        1. Custom Lists
        2. Collections
          1. Design
          2. Configuration
        3. Revision
        1. My Applications
        2. Files
        3. Home
        1. Process Examples
        2. Connectors
        1. Web Interface Reports
          1. Execution Path
          2. Measuring
          3. Parameters
          4. Runtime Users
        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


    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.