Please give details of the problem



    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

    Manual Task Tab

    This tab allows you to configure a manual task to be performed during the process. This document outlines each option that can be set.


    You can use i18n to internationalize your application. Enter the language code that you'd like your email / notification to be sent in and use App Translator to create a dictionary for that language.

    There are two ways of populating this field:

    • By writing a script (e.g. ${P_user.preferences.my_language})
    • By entering the name of the dictionary to be used for the translation. Dictionaries are given custom names when they are created in AppTranslator.

    If this field is not set and the task is assigned to one person, the email will be sent in that person's preferred language. If the task is assigned to several users and this option is not set, the email will be sent in the default value of the i18n functions.


    The title of the task: it can either be fixed or dynamically evaluated using a formula (use Freemarker syntax).

    Web interface

    There are two options for choosing the web interface:

    1. Static web-interface

    Choose a web interface that contains a screen to perform the manual task (see Web interfaces). This web interface must belong to the project the process belongs to.

    Select a screen of your web interface (see Web interface)

    info You can open your web interface by clicking on the icon application_go . You can also create a new one by clicking on the button "New web interface"

    2. Dynamic web-interface

    You can choose to have a dynamic screen (see image bellow). In this case, the Web interface will be determined either by the launch web-interface or by its number identifier. You will need to provide a screen name (part of the specified web interface).

    info_1 "Screen name" and "Dynamic Web interface" can be freemarker formula.

    info_1 We recommend that you define a unique name for the screens to avoid potential conflict issues.

    Assign to

    The person in responsible for completing a manual task can be selected from the list of users or dynamically evaluated using a formula (use Freemarker syntax): it is always an email address.
    In all cases, runtime controls ensure that the chosen person in charge belongs to the role/entity that this task is attached to.
    If this field is empty, the task will be assigned to the role/entity that this task is attached to.

    Do not delegate

    Check this box if you don't want a user to delegate this task.

    Keep visible for the role

    Check this box if you want to display this task to all users in the role although it has been assigned to a specific user.

    Assign to entity

    Allows you to define the role in charge of the manual task. It is the identifier of a role that belongs to the dynamic role. It can be calculated with a Freemarker script


    <#if var="1" >27551<#else>27552</#if>

    info_1 This field only appears if the manual task belongs to a dynamic role


    If you check this box, the person that will receive the email won't have to authenticate to perform the manual task.

    info_2 If you open the task from "Desktop/My tasks", authentication will be needed. You must click on the link (the description of the task) to have the public URL of the task (without authentication).

    Inject results

    Check this box if you want to create all variables of your web interface screen as output variables of your task otherwise you will have to create for each variable of your web interface an output variable to get values typed by the user in your web interface (e.g. name=${P\_result.name}) or use inject_params() freemarker function.

    info_3 In this case, the P_result variable of manual task is not updated, the value of the previous task remains present in variable P_result.

    Notify via email

    Send an email to the person responsible for completing the task. You must fill in the "Provider" field.If needed, you can modify the sender of the email by entering an email address in "From" field. This "From" field will be taken into account according to your email provider.

    info_4 Only providers that belongs to the same project as the process (or a project included in this project) will be proposed.

    info_5 The "From" field must be an email of an active RunMyProcess user otherwise it will be replaced during process execution by "no-reply@runmyprocess.com".


    Select the priority of the email and the task: high, medium, low.

    Due in

    Number of days and/or months the assignee has before the task needs to be completed.


    Number of days given by a variable of a freemarker script before which the task must be performed.


    A description of the task given to the person responsible for completing it.

    info_6 If the 'Notify via email' option is checked, the content of this field will then be the body content of the email sent to the person responsible for completing the task.

    info_7 Internal variable P_task_url gives the url of the web interface screen to perform the task. To create a link to your web page in your
    email, type:

    <a href="${P_task_url}">click here</a>

    info_8 If 'Inject results' check box is not checked, the variables filled up in your web page are stored in P_result.variable_name variable in the Output variable.This will allows you, for instance, to detect which fields have been modified in your web form by user.

    info_9 When a process is launched in a project's version in Test state, emails are sent to the user who has launched the process(at the beginning of the body of the email, you will find the real recipient), tasks are assigned to the user who has launched the process (he will also receive an email notification if this option has been checked in manual task), whatever the entries in the 'Assign to' field above. User who is testing must belongs to the lane manual task belongs to.

    Send Mobile Notification

    If this option is checked the end user will receive a push notification on their mobile device for this task, provided that: