×

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

    Configure a task reminder email (for advanced designers)

    When you assign a manual task to a user or a group of users, you may want to send a reminder email until the task is completed. Let's go through its configuration.

    Your main process

    Let's take the following example: you configured a manual task assigned to a Manager + email notification:

    main_process_v1

    What you shouldn't do

    To configure a reminder, you may want to configure a timer/overdue handler on the task and loop back to send again the email with the task link:

    bad_design_main_process

    With this design, it will not only send an email with the task link again, but also GENERATE a new task link and CANCEL the previous link you've sent.

    What you should do

    Our goal is to keep the SAME task link to only have 1 task generated, and to send several reminder emails with the SAME task link.

    Let's go through 2 examples:

    • How to split manual task + email notification into 2 different activities, with no reminder
    • How to split and add a reminder

    Split manual task assignation and email notification with no reminder

    You can split the activity manual task + email notification into 2 different activities:

    split_process

    Since you will send the email before assigning the task, you have to generate its link.

    You have to use this freemarker function:

    1
    ${get_next_url(activityid,ispublic)}
    

    activityid is the id of the activity where you've configured the manual task, and ispublic=true only if you generate a public task link. You can get activityid in Functional tab > ID

    split_process_activityid

    So, forour example, activityid=2 and ispublic=false. Let's configure email sending activity:

    split_process_config_email

    As an input create a task_url variable with value

    1
    ${get_next_url(2,false)}
    

    You'll have to configure To and Message fields. Note that we used ${task_url} in Message.

    You may want to use this design anytime you'd like to notify less people than the task is assigned to (ex: the task is assigned to managers and super managers, but you only want to notify the managers).

    Split manual task assignation and email notification + add a reminder

    Our goal is to assign a task, send an email notification, and keep sending emails every 5min until the task is completed.

    Architecture

    We'll split the activity manual task + email notification into 2 different activities (cf previous section), but instead of sending an email, we'll start a process as a connector that will manage the reminder emails.

    The Main process:

    reminder_process_main

    The Main process will pass ${task_url} to the connector that will start the reminder process:

    reminder_connector_kick_process_reminder

    The reminder process will send the email notification, wait 5min, then check if the task is completed/validated. If not, then loop back to email notification:

    reminder_process_reminder

    The reminder process will call a connector to check if the task is completed or not:

    reminder_connector_check_task_status

    Configuration

    • Main process

    Add a new measure

    1
    task_url = ${task_url}
    

    reminder_process_main_measure

    Note the position of the measure: here it's #1.

    Modify this input variable value to call the connector:

    1
    task_url = ${get_next_url(2,false)}
    

    reminder_process_main_call_connector

    reminder_plug_connector_kick_task_reminder_process

    • Get task status connector

    Since we configured task_url as a measure, we are able to retrieve the webinterface instance status (the task status) from the task_url.

    Use a standard RunMyProcess provider:

    rmp_provider

    And create a new connector, that will send a GET request to the following url:

    1
    live/${P_customer}/applistate?nb=20&first=0&filter=PROJECT%20MODE%20MEASURE_1%20APPLI%20SUB_STATE&operator=EE%20EE%20EE%20EE%20EE&column=name%20published%20state%20measure_1&value=${project_id}%20${P_mode}%20${task_url?url}%20${webinterface_id}%20START
    

    project_id: to be replaced by the id of your project.

    P_customer: leave it as it is.

    P_mode : leave it as it is.

    webinterface_id: to be replaced by the id of the webinterface you used to generate a task.

    MEASURE_1 and measure_1 : remplace 1 by the position id of task_url measure.

    task_url: input parameter.

    Accept media type must be application/atom+xml

    reminder_connector_check_task_status

    • Task reminder process

    reminder_process_reminder_fig

    (1) Plug an email notification, and pass the ${task_url} link in the content of the email

    (2) Configure a timer/waiter to wait 5min (frequency to be customized)

    reminder_process_timer

    (3) Call the Get task status connector

    Pass as input:

    reminder_process_get_status_input

    As output create a is_task_active parameter:

    reminder_process_get_status_output

    As value use this script:

     1
     2
     3
     4
     5
     6
     7
     8
     9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    <#function get_array my_father my_son>
        <#if my_father?is_hash>
            <#if my_father[my_son]?exists>
                <#if my_father[my_son]?is_sequence>
                    <#assign my_array = my_father[my_son]>
                <#else>
                    <#assign my_array = [my_father[my_son]?eval]>
                </#if>
            <#else>
                <#assign my_array = []>
            </#if>
        <#else>
            <#assign my_array = []>
        </#if>
        <#return my_array>
    </#function>
    
    <#assign entries = get_array(P_result.feed,"entry")>
    <#if (entries?size == 0)>
        <#assign is_task_active = "no">
    <#else>
        <#assign is_task_active = "yes">
    </#if>
    ${is_task_active}
    

    Then you can configure the gateway condition:

    reminder_process_gateway

    Add task_url as input parameter for this process:

    reminder_process_input_params

    Then you can save your process and click on Open corresponding connector

    reminder_process_open_corresponding_connector1

    reminder_process_open_corresponding_connector_preview

    • Connector to kick the reminder process

    Under the RunMyProcess provider, create a new connector with the exact configuration you see when clicking on Open corresponding connector in the reminder process.

    reminder_process_connector_kick_process

    This connector has to be plugged to the Main process

    Congratulations, you've configured an automatic task reminder email!

    Note: you can use the same connector to trigger the reminder process at several places in the Main process, you just have to pass the frequency and the recipients logins as input parameters.