×

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

    SubProcess

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

    2012-01-20_115448

    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)

    2012-01-20_115752

    Then you should see this screen:

    2012-01-20_114638

    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.

    2012-01-20_123047

    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'

    2012-01-20_174224

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

    2012-01-20_174829

    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)

    2012-01-20_175411

    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

    2012-01-20_175703

    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
      see
    • 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.

    2012-01-20_180324

    2012-01-20_180427

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

    On the father process, untick 'Inject results'

    2012-01-20_180730

    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)

    2012-01-20_181340

    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.