×

Please give details of the problem

Docs

Find

    User Guide

  1. Usage Report
  2. Logs Application
  3. Easy Builder
  4. FAQ
  5. User Management
        1. Composite API Design Tab
        2. Composite API Configuration Tab
        1. Providers
        2. Connectors
        3. Processes
        1. Roles entities
        2. Organization
      1. Collections
        1. Project Files Tab
        2. Project Definition Tab
        3. Project Versioned Files Tab
        4. Project Version Tab
        5. Project Description Tab
        6. Version
        7. Project Rights Tab
        8. Project Collection Tab
        1. Web Interface JS Tab
        2. Web Interface Design Tab
          1. Image Widget
          2. FileUpload Widget
          3. StaticText Widget
          4. ProgressBar Widget
          5. TextInput Widget
          6. JavaScript Widget
          7. Section Widget
          8. Geolocation Widget
          9. Checkbox Widget
          10. RadioButton Widget
          11. Tree Widget
          12. Spinner Widget
          13. History Widget
          14. URLInput Widget
          15. Tab Widget
          16. List Widget
          17. Array Widget
          18. HTML Editor Widget
          19. Report Widget
          20. Button Widget
          21. Custom Widget
          22. Captcha Widget
          23. HTML Widget
          24. Multi Checkbox Widget
        3. Web Interface Analytics Tab
        4. Web Interface Collection Tab
        5. Web Interface Implementation Tab
        6. Web Interface API Tab
        7. Web Interface Stylesheet Tab
      2. Revision
      3. Custom Lists
        1. Process Variables Tab
        2. Process Measures Tab
            1. Process Timer Event
            2. Process Start Event
            3. Process Intermediary Event
          1. Gate
            1. Process Task Loop Tab
            2. Process Task Manual Tab
            3. Process Task Email Tab
            4. Process Task Connector Tab
            5. Process Task SubProcess Tab
            6. Process Task Functional Tab
            7. Process Task Script Tab
          2. Process Step Output Variables
          3. Process Step Testing Variables
          4. Process Step Input Variables
        3. Process General Tab
        4. Process Design
        5. Process Input Tab
      1. Home
      2. My Tasks
      3. My Applications
      4. Files
    1. Customer Management
      1. Messages
      2. Scheduled Process
      1. Process Examples
      2. Connectors
      1. Users
      2. Configuration
      3. Usage
      1. Web Interface Reports
        1. Measuring
        2. Runtime Users
        3. Execution Path
        4. Parameters
    1. RunMyApp for Android
    2. RunMyApp for iOS
    3. RunMyApp for Windows
  6. My Settings
  7. App Translator

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.

Language

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.

Title

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
Code.

Example

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

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

Public

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

Priority

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.

Formula

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

Description

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:

1
<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: