×

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

    Trigger a process

    On RunMyProcess, a process can be launched in several ways. Each solution for triggering a process has strong implications on the input variables passed to the process and the link to instances. in this pages, we will review each solution

    Schedule a process with a Timer

    You can schedule a process : it will be launched automatically at a predefined frequency (@see Process Start Event).

    In order to trigger a process with a Timer, you have to configure certain parameters.

    (1) Choose Timer as Trigger.

    (2) Choose the number of repetitions of launches. Click "Unlimited" if you want the process scheduling to loop indefinitely.

    (3) Delay between two launches of the process. Choose the delay between responses days, hours and minutes.

    When a process is triggered with timer configuration, initial parameters are not configured.

    Trigger a process by email

    You can also trigger a process by sending an email to our platform (@see Process Start Event).

    (1) Choose Trigger Message

    (2) Message box address : Email address to launch the process. You can click on link to copy Live email address needed to launch the process. Format of email address is the following :

    process+{customerid}.{processid}@runmyprocess.com to launch process in Live state and

    process+{customerid}.{processid}.TEST@runmyprocess.com to launch process in Test state.

    (3) You can map the subject of your email to an input variable of the process.

    (4) The content of your email can be associated to an input variable of the process.

    (5) You can map also the cc field to a variable.

    (6) The attachement of your email can be associated to a variable of the process.

    You can manage messages through the flex IDE

    (@see Messages Monitoring)

    Please note that the user who launches the process must belong to the lane of the process.

    Trigger a process from a Web Interface

    You can launch a process using a Web Interface.

    (1) Create a Button and choose Start Process as Action.

    (2) Choose the process you want to launch.

    (3) You can define On click action after pushing the button :

    • Show pop-up message after pushing the button.
    • Close the window opened.
    • Show the message and then close the window.
    • Redirect to another page.
    • Reload the same screen after button pushed.
    • Load next screen.

    The variables of the web interface will be considered as initial parameters of your process.

    This is the most common way to launch a process. Using this solution brings many advantages

    • the measures of the process launched will be transmitted to the instances (web interface instanciation)
    • globally the process is linked to the instance which means for example that you can retrieve the generated manual task url in the process execution

    Subprocesses

    In order to factorize tasks, you can include a process in another process. The included process will be called a subprocess.

    A subprocess is always launched synchroneously with respect to the main process, which means that the main process will only be resumed once the subprocess execution is over.

    A subprocess can be executed as a different process (case by default) or as a nested process.

    When a subprocess is confgured as a nested process it means that the subprocess ans the main process will share the same execution context. The parameters will be shared and the history (@see Web Interface History and Comments Widget) too. On the other hand, when a subprocess is not configured as a nested process, one can define precisely which variables are going to be passed from the main process to the subprocess and vice-versa.

    Last a launched subprocess will be linked with the launched main process. The main request is said to be the parent of the subrequest.

    For more information on subprocess configuration @see Subprocess

    Process Listener

    A process can be launched from a web interface without being linked to it ( meaning that the measures defined on the process will not be passed to the web interface ) using the process listener feature.

    Launching a process as a process listener can also be used to launch several process from the same web interface.

    All the variables from the web interface will be passed to the process listener.

    A process listener can be configured as shown in the link below (section process listener) : (@see Process Listener).

    Trigger a process directly by Web Service

    You can trigger a process directly by Web Service.

    When done using a connector in a process, it can be considered as aysnchroneous. In this case, the triggered process parent will have no parent to be linked to.

    Here is the API to launch a process by web service.

     1
     2
     3
     4
     5
     6
     7
     8
     9
    10
    11
    POST https://live.runmyprocess.com/live/${P_customer}/process/${process_id}?P_mode=${execution_mode}&P_version=${version_id}
    Content-Type : application/*
    
    <?xml version="1.0" encoding="UTF-8"?>
    <feed xmlns="http://www.w3.org/2005/Atom" xml:base="https://live.runmyprocess.com/">
        <title>Title</title>
        <entry>
            <title>Title</title>
            <content type="text/base64">${encrypt('BASE64',initial_parameters)}</content>
        </entry>
    </feed>
    

    with input params a JSON object containing the parameters to be passed to the process

    1
    {"my_var_1":"foo","my_var_2":"bar"}