×

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

    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"}