--- title: "Form Task" slug: "form-task" updated: 2026-06-03T22:55:46Z published: 2026-06-03T22:55:46Z canonical: "docs.processmaker.com/form-task" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.processmaker.com/llms.txt > Use this file to discover all available pages before exploring further. # Form Task A **Form Task** represents an activity that a participant performs as part of a case within ProcessMaker Platform. It serves as an interactive step where users provide input or make decisions using screens built in the [**Screens Builder**](/v1/docs/screen-builder). A Form Task can be assigned to: - A specific user - A member of a group - The previous task assignee in that case - The user who started the case --- ## Add a Form Task to a Process **Permissions** Your user account or group membership must have the following permissions to configure a Form Task object in the Process model unless your user account has the **Make this user a Super Admin** setting selected: Processes: Edit Processes Processes: View Processes See the [Process](/v1/docs/permission-descriptions-for-users-and-groups#processes) permissions or ask your Administrator for assistance. Add a Form Task object from one of the following locations in the Process Modeler: - **Object Panel:** Located to the left of the Modeler, the Object Panel contains various process modeling objects. - **Object Bar:** Located at the bottom of the Modeler, the Object Bar contains [pinned](/v1/docs/process-modeler#pin-and-unpin-objects) modeling objects for quick access. Add from the Object PanelAdd from the Object bar Follow these steps to add a Form Task object from the Object panel to the Process model: 1. Ensure that the Object panel is visible. If not, click the **Add** icon ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(247).png) from the Object bar at the bottom. 2. Click the **Task** object ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(248).png) from the Object panel to select it. 3. Click the location in the Process model to place this object. Follow these guidelines when placing this object: - If there is a Pool object in your process, the Form Task object cannot be placed outside of the Pool object. - To place this object between two existing objects, follow [these instructions.](/v1/docs/sequence-flow-element#place-an-object-between-two-process-model-objects-already-connected-with-a-sequence-flow-element) ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(249).png) Follow these steps to add a Form Task object from the Object bar to the Process model: 1. Ensure that the object is pinned to the Object bar. If not, [see instructions to pin it](/v1/docs/process-modeler#pin-and-unpin-objects). 2. In the Object bar at the bottom center, click the object's icon. 3. Click the location in the Process model to place this object. Follow these guidelines when placing this object: - If your process has a Pool object, the Form Task object cannot be placed outside of the Pool object. - To place this object between two existing objects, follow [these instructions](/v1/docs/sequence-flow-element#place-an-object-between-two-process-model-objects-already-connected-with-a-sequence-flow-element).![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(246).png) **Add boundary events** After adding an object to a process, consider adding the following events to handle exceptions: - [Boundary Timer Event](/v1/docs/boundary-timer-event) element - [Boundary Error Event](/v1/docs/boundary-error-event) element - [Boundary Signal Event](/v1/docs/boundary-signal-event) element - [Boundary Conditional Event](/v1/docs/boundary-conditional-event) element - [Boundary Message Event](/v1/docs/boundary-message-event) element **Adjust location and appearance** - [Move a Process Model Object.](/v1/docs/process-modeler#move-process-model-objects) - [Connect Two Process Model Objects with a Sequence Flow Element.](/v1/docs/sequence-flow-element#connect-two-process-model-objects-with-a-sequence-flow-element) - [Customize the Appearance of a Process Model Object.](/v1/docs/customize-the-appearance-of-a-process-model-object) - [Copy Process Model Objects into the Clipboard.](/v1/docs/process-modeler#copy-process-model-objects-into-the-clipboard) - [Clone Process Model Objects Without the Clipboard.](/v1/docs/process-modeler#clone-process-model-objects) - [Delete Process Model Objects.](/v1/docs/process-modeler#delete-process-model-objects) ## Replace a Form Task with a Different Task After a Form Task is added to a process, you may replace it with a different Task type or a Sub Process. Follow these steps to replace a Form Task with a different task: 1. Select the Form task to change to another object. 2. Click the **Objects** icon to view a list of task types. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/3c6ee61a-7dc9-478b-a634-1e98e55fd60e.png) 3. Select the object to replace the Form Task. The **Change Type** screen displays to confirm replacing the currently selected object. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/51cd84ae-e62d-4a29-94b5-3a1a5a0a298b.png) 4. Click **Confirm**. The new object replaces the Form Task object with its default settings and color. --- ## Settings The Form Task object has the following configuration settings: - [**Properties panel**](/v1/docs/form-task#configuration-panel-settings) - [**Loop Characteristics panel**](/v1/docs/form-task#loop-characteristics-panel-settings) - [**Documentation panel**](/v1/docs/form-task#documentation-panel-settings) - [**Assignment Rules panel**](/v1/docs/form-task#assignment-rules-panel-settings) - [**Notifications panel**](/v1/docs/form-task#notifications-panel-settings) - [**Email Notifications panel**](/v1/docs/form-task#email-notifications-panel-settings) - [**Web Entry panel**](/v1/docs/form-task#web-entry-panel-settings) - [**Advanced panel**](/v1/docs/form-task#advanced-panel-settings) --- ### Properties Panel Settings The Form Task object has the following settings in the **Properties** panel: #### Edit the Object Name An object name is a human-readable reference for a Process object. Process Modeler automatically assigns the name of a Process object with its object type. However, an object's name can be changed. Follow these steps to edit the name for a Form Task object: 1. Select the Form Task object from the Process model in which to edit its name. 2. Ensure that the **Configuration** panel displays. If not, [show it](/v1/docs/show-configuration-settings-for-a-process-model-object). The **Name** setting displays. This is a required setting. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/4b391a98-2b44-4efb-a31b-c3133e0db2c1.png) 3. In the **Name** setting, edit the selected object's name and then press **Enter**. #### Select a Screen for the Task Since Form Tasks are designed to collect or display [Request](https://docs.processmaker.com/v1/docs/request-details) information, a [screen](https://docs.processmaker.com/v1/docs/screens-types) must be associated with them. Follow these steps to select a Screen for a Form Task object: 1. Select the Form Task object from the Process model. 2. Click the ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/setting(1).png) icon to view the **Configuration** panel. 3. Expand the **Configuration** panel if it is not presently expanded, and then locate the **Screen For Input** setting. This is a required setting. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(284).png) 4. Do one of the following: - From the **Screen For Input** drop-down menu, select one of the available screens. - To create a new Screen, click the **Create a new screen** link. A new browser window opens to [create a new Screen](https://docs.processmaker.com/v1/docs/create-a-new-screen). After the Screen is created, it is automatically linked to the Form Task. 5. Optionally, click the **Open Screen** link to view and/or edit your Screen. Note that your user account must have appropriate [Screen category](https://docs.processmaker.com/v1/docs/screen-categories) permissions or be a [Project](https://docs.processmaker.com/v1/docs/projects) member in which this Screen is an asset. > [!CAUTION] > Ensure to select a Screen for each Form Task in your Process model. If a Screen is not specified and Requests are started for that Process, the following message will be displayed. > > ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(285).png) > > The placeholder Screen allows the Task assignee to continue the Request without causing it to pause indefinitely. > > If no Screens exist, the **Screen For Input** drop-down menu contains no options. #### Preview the Screen for a Task After [selecting Screen for the Task](/v1/docs/form-task#select-the-screen-for-the-task), you may preview the associated Screen, which allows you to interact with and verify the Screen content in the same Process Modeler. Follow these steps to preview the associated Form Screen from a Form Task object: 1. Select the Form Task object to preview the associated Screen. Available options display above the selected object. 2. Click the **Preview** icon ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/d5395b94-89a3-4a62-896a-c7f4a4cc6571.png). A preview window displays on the right-side of the Process Modeler. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/687dadca-e339-4454-b68d-a2b954175949.png) Previewing the Screen for a Form Task object 3. In the Preview window, you can do the following: - Click the icon ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/db98735d-91b2-476a-868a-44a8edfaa578.png) to open the [Screen Builder](/v1/docs/screen-builder) to edit the Screen. - Click the icon ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/5ea12518-0636-4efe-a849-21c1fb870b3f.png) to close the preview window. - Click another Task or connector object to change the asset in the same preview window. 4. The following message displays if you try to preview a task with no associated screens. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/6c9993b4-4dab-4e49-b43b-a832909d0eb0.png) #### Select the Task Destination Specify the destination to which users are redirected after completing a task. By default, users return to their original access point, such as a task list, dashboard, or previous page. You can override this behavior to redirect users to locations such as the process LaunchPad, a specific dashboard, or an external URL. Follow these steps to select a object destination: 1. Select the Form Task object from the Process model. 2. Click the ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/setting.png) icon to view the **Configuration** panel. 3. From the **Task Destination** drop-down menu, select the page to display after a user completes this task. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(281).png) 4. Select one of the the following options. Selecting a destination object other than **Task Source** will render the **Display Next Assigned Task to the Task Assignee** feature unusable since the object will have an alternate destination. - **Task Source (Default):** This option redirects the user to the original access point where the task started. - **Task List:** This option redirects the user to the [Task](/v1/docs/tasks#view-tasks) list. - **Process Launchpad:** This option redirects the user to the [Process Launchpad](/v1/docs/process-launchpad). - **Welcome Screen:** This option redirects the user to the [Participant Welcome Screen](/v1/docs/participant-welcome-screen). - **Custom Dashboard:** This option redirects the user to a [dashboard](/v1/docs/dashboards). After selecting **Custom Dashboard**, a dropdown menu appears below to select the desired dashboard. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(282).png) - **External URL:** This option redirects the user to an external URL. After selecting **External URL**, a dropdown menu appears below to enter the URL. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(283).png) --- **Display Next Assigned Task** Use the **Display the Next Assigned Task** option to automatically take the user to the next task if it is assigned to them. If the next task is assigned to a different user, then the [**To Do Tasks**](/v1/docs/tasks) page displays after Task completion. 1. Select the **Display the Next Assigned Task** option. 2. From the **Screen Interstitial** setting, select the Screen to display after this Task completes and before the next Task begins. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(341).png) **Benefits of Using Interstitial Screens** - **Smooth Task Transitions:** Display a loading screen (e.g., *"Loading your next Task"*) while a request routes to the next form-based Task. - **Prevent Abrupt Endings:** If a script task is followed by an end event, show a summary screen instead of abruptly ending the request. #### > [!NOTE] > Note: > > - Task Destination setting applies whether the user is completing the task while logged into ProcessMaker or as an anonymous user through a web entry. > - If an Interstitial Screen follows a **Web Entry Start Event** in a child request, it cannot redirect back to the parent request—only to tasks within the child request. #### Specify When the Task is Due Configure when a task becomes due after it is assigned to a user. When set, the due date/time is displayed in the task list for each in-progress task. If a task becomes overdue, the task assignee is notified through an indicator in the task list. #### ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(287).png) Due dates can be set as a static number of hours during process design, or made dynamic by using variables in `{{mustache_syntax}}` for greater flexibility. The task due date does not change in the following circumstances: - **Task is reassigned to another user:** The original due time remains the same and now applies to the new assignee. - **An interrupting boundary-type event triggers:** The event has its own due date, leaving the original task's due date unaffected. When an interrupting boundary-type event triggers, the workflow will route through the event, and the due date for any subsequent task will apply. > [!NOTE] > - The default due time for a Form Task is 72 hours (three days). > - Specify the due time as total hours, including non-business hours, overnight, weekends, and holidays. > - A Self Service Task can become overdue even without an assignee. The due time starts when the task becomes active. Follow these steps to specify when a Task is due: 1. Select the Form Task object from the Process model. 2. Click the ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/setting(2).png) icon to view the **Configuration** panel. 3. Expand the **Properties** panel, and then locate the **Due In** setting. #### ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(288).png) 4. In the **Due In** setting, specify the total number of hours after which a task becomes due. - Enter the number of hours in the **Due In** setting and then press **Enter**. - Hover your cursor over the **Due In** setting, and then use the spin arrows to increase or decrease the total number of hours. - Select the **Use Request Variable** option and reference a request variable in [mustache syntax](https://mustache.github.io/mustache.5.html) `{{variable_name}}`. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(289).png) - During a case, a numerical value must be assigned to this variable, indicating the number of hours after which the task will become overdue. For example, a value of `48` will mark the task as overdue after 2 days. #### Add a Placeholder for the Slideshow Mode The Slideshow Mode makes it easy for process designers to share the design of a process with all stakeholders, regardless of whether they have access to the ProcessMaker Platform. For more information on how to create slideshows for a process, see [Slideshow Mode.](/summer-2024/A7mdugENW7gZw1jmnrOv/designer-modeler/process-design/slideshow-mode) Follow these steps to add a placeholder image for the Slideshow Mode: 1. Select the Form Task object from the Process model. 2. Click the ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/setting(5).png) icon to view the **Configuration** panel. 3. From the **Placeholder for Slideshow** section, click on the **+Drag or click here** button to upload an image. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(295).png) 4. A preview of the image will display, and the configuration will be auto-saved. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(296).png) 5. The uploaded image will be shown for this task the next time the slideshow is viewed. ***Notes:*** - *Size of a placeholder image for slideshows must less than 2 MB.* - *Image files with PNG, JPG, JPEG, and GIF extensions are supported.* --- ### Loop Characteristics Panel Settings Use the **Loop Activity** panel settings to specify how to perform multiple instances of this object. The following loop modes are available: #### No Loop Mode Select the **No Loop Mode** option to perform this object's Task only once. Follow these steps to specify characteristics to perform multiple instances of the Task:‌ 1. Select the Task from the Process model. Panels to configure this object display. 2. Expand the **Loop Activity** panel. By default, the **Loop Mode** setting is set to **No Loop Mode** and the function is performed only once. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(291).png) #### Loop Select the **Loop** option to sequentially repeat this Task's function multiple times until an exit condition is `True`. This is useful when a function should be performed multiple times with the same set of data, such as, processing a credit card payment. This loop mode has the following characteristics: - The Task's function is repeated until the exit condition is `True` or the maximum iterations limit is reached. - At any given time, only one instance of the Task is active. The subsequent instance does not begin until the current instance completes. - The same exit condition evaluates at the end of each instance; however, value(s) of the Request variable(s) used in the exit condition can change during an instance resulting in the exit condition to eventually evaluate as `True`. - If any one instance of that function does not complete, workflow pauses. - All active instances are terminated if an interrupting boundary-type event object triggers.![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/load.png) An object configured in this mode shows the **Loop** icon in Process Modeler. Follow these steps to specify characteristics to perform multiple instances of the Task:‌ 1. Select the Task from the Process model in which to specify multiple instance characteristics. Panels to configure this object display. 2. Expand the **Loop Activity** panel to display the **Loop** Mode Setting. 3. From the **Loop Mode** setting, select the **Loop** option. The settings for this loop mode display: ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(292).png) 4. In the **Maximum Iterations** setting, enter an integer value representing the maximum number of times this Task should be performed. 5. In the **Exit Condition** setting, enter a condition in FEEL syntax. When this condition is True the loop activity is halted. #### Multi-instance (Parallel) Select the **Multi-instance (Parallel)** option to perform this Task's Task multiple times in parallel a fixed number of times. This is useful when performing any action in bulk, such as sending an email to several people. This loop mode has the following characteristics: - Instances of the Task are governed by the size of an array-type Request variable where a new instance is created for each item in this variable. For example, an array with 10 items will create 10 parallel instances of this function that each contains data from its respective array index. - All instances begin simultaneously when this Task triggers; however, they perform their function independently of each other. - The function as a whole completes when all instances are complete. - The output from each instance can either be saved in the source Request variable or a new array-type Request variable. - All active instances terminate if an interrupting boundary-type event object triggers. - A Task configured in this mode shows the Multi-instance (Parallel) icon![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/lines.png) in Process Modeler. Follow these steps to specify characteristics to perform multiple instances of the Task:‌ 1. Select the Task from the Process model in which to specify multiple instance characteristics. Panels to configure this object display. 2. Expand the **Loop Activity** panel to display the **Loop Mode** Setting. 3. From the **Loop Mode** setting, select the **Multi-instance (Parallel)** option. The settings for this loop mode display: ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(293).png) 4. In the **Request Variable Array** setting, enter the name of an array-type Request variable. The size of this array will determine how many times this loop iterates. 5. In the **Output Data Variable** setting, enter the name of an array-type Request variable in which to store the results of all instances. Each instance of the loop saves to a separate JSON object within the array of the specified Request variable. If the **Output Data Variable** setting is not configured, then the output data replaces the source data in the **Request Variable Array**. **Multi-Instance Task Assignment for Users Without Email Addresses** When assigning a multi-instance task to a group, the platform includes all users in the group, even if some users do not have an email address configured. - Users without an email address still receive the assigned task in their task inbox as usual. The platform skips email validation for those users and does not attempt to send email notifications to them. - Email notifications continue to be sent normally to users in the group who have a valid email address configured. - This behavior prevents assignment failures caused by users with missing email addresses while still allowing tasks to be assigned successfully to everyone in the group. #### Multi-instance(Sequential) Select the **Multi-instance (Sequential)** option to perform this Task's function multiple times sequentially a fixed number of times or until an exit condition is `True`. This is useful when sequentially repeating a function multiple times but with a different set of data each time. This loop mode has the following characteristics: - Instances of the function are governed by the size an array-type Request variable where a new instance is created for each item in this variable. For example, an array with 10 items will create 10 parallel instances of this function that each contains data from its respect array index. - At any given time, only one instance of the function is active. The subsequent instance does not begin until the current instance completes. - At the end of each instance an exit condition evaluates and the loop activity halts if the exit condition is `True`. - The function as a whole completes when all instances are complete. - The output from each instance can either be saved in the source Request variable or a new array-type Request variable. - All active instances terminate if an interrupting boundary-type event object triggers. - A Task configured in this mode shows the Multi-instance (Sequential) icon![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/setting(4).png)in Process Modeler. Follow these steps to specify characteristics to perform multiple instances of the Task:‌ 1. Select the Task from the Process model in which to specify multiple instance characteristics. Panels to configure this object display. 2. Expand the **Loop Activity** panel to display the **Loop Mode** Setting. 3. From the **Loop Mode** setting, select the **Multi-instance (Sequential)** option. The settings for this loop mode display: ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(294).png) 4. In the **Request Variable Array** setting, enter the name of an array-type Request variable. The size of this array will determine how many times this loop iterates. 5. In the **Exit Condition** setting, enter a condition in FEEL syntax. When this condition is True the loop activity is halted. 6. In the **Output Data Variable** setting, enter the name of an array-type Request variable in which to store the results of all instances. Each instance of the loop saves to a separate JSON object within the array of the specified Request variable. If the **Output Data Variable** setting is not configured, then the output data replaces the source data in the **Request Variable Array**. --- ### Documentation Panel Settings Describe the object's purpose and how it functions in the Process. This description does not affect Requests for the Process, but may be useful for Process model maintenance such as how the object is configured. Edit information by using the What-You-See-Is-What-You-Get (WYSIWYG) rich text editor. A Process's entered documentation displays by selecting the [**View Documentation option for that Process**](/v1/docs/process-documentation). #### Edit the Object Documentation Follow these steps to edit the description for an object: 1. Select the object from the Process model in which to edit its description. 2. Ensure that the **Configuration** panel displays. If not, [show it](/v1/docs/show-configuration-settings-for-a-process-model-object). Panels to configure this object display. 3. Expand the **Documentation** panel if it is not presently expanded. The **Description** setting displays. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/d76e8941-8a7b-4d41-9164-205b64b9070e.png) 4. In the **Description** setting, edit the information to display when viewing documentation for this object and then press **Enter**. Alternatively, use the What-You-See-Is-What-You-Get (WYSIWYG) rich text editor to stylize your text by clicking the **More** icon![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/00671229-2947-447c-91dc-2665ebb36cc3.png). ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/c9bb3026-5cd5-407b-aabd-bec638b5c54b.png) Follow these guidelines to use the WYSIWYG rich text editor to stylize your text: - **Undo changes:** Click on the![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/5df337cb-9359-4ded-8bfd-1aaccc0a829a.png)icon to undo the last action. - **Redo changes:** Click on the![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/b232a604-947d-493c-a5cb-7b45cc0ee3b9.png)icon to redo the last undone action. - **Insert/Edit Link**: Click on the![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/c8375eda-da7c-4b2e-b215-3150fce8ab88.png)icon to convert the selected text into a hyperlink. Follow these steps to create a hyperlink: 1. Select the required text from the Rich Text control. 2. Click on the![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/c8375eda-da7c-4b2e-b215-3150fce8ab88.png)icon. The **Insert/Edit Link** screen displays. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/35f02a5c-bbef-4b0a-99a7-ee99bd5fd181.png) 3. In the **URL** setting, enter the destination URL. 4. In the **Text to display** setting, edit or enter the text displayed in the Rich Text control. 5. In the **Title** setting, enter the text to display when a user hovers over the displayed text. 6. From **Open link in…** drop-down menu, select one of these options: - **New window**: Select this option to open the destination page in a new browser window. - **Current window**: Select this option to open the destination page in the current browser window. - **Insert/Edit Image:** Click on the **Insert/Edit Image** icon![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/b4f4a7c2-f469-43c3-9ef0-0fd4df574b26.png)to insert an image. Follow these guidelines: 1. Click on the **Insert/Edit Image** icon![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/b4f4a7c2-f469-43c3-9ef0-0fd4df574b26.png). 2. The **Insert/Edit Image** screen displays: ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/d07306df-cc49-4f13-ab67-4c37685f25d7.png) 3. In the **Source** setting, enter a URL for the image. 4. In the **Alternative Description** setting, enter the text to display if the source URL of the image is not accessible. 5. In the **Width** setting, enter the maximum width for the image. 6. In the **Height** setting, enter the maximum height for the image. 7. Toggle the **Constrain Proportions** icon![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/93fa708f-8cde-4628-af96-1336f8841dc5.png)to maintain the width-height ratio of the image to its original proportion. 8. Click **Save**. - **Insert Page Break for PDF:** Click on the **Insert Page Break for PDF** icon![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/29b1cd29-e381-4810-af9b-a84b04e02af6.png)to insert a page break when a PDF document is created for this documentation if your browser supports this feature. - **Format text**: Follow these guidelines to format text: - **Headings**: From the **Paragraph/Formats** menu, select **Headings** and then select a heading size. - **Bold:** Do one of the following: - From the editor toolbar, select the![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/79b5eec2-d2bf-472b-808a-a1d37c1548c8.png)icon. - From the **Paragraph/Formats** menu, select **Inline** and then **Bold**. - **Italics:** Do one of the following: - From the editor toolbar, select the![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/a3288228-a55a-4013-9ddd-81887f1be388.png)icon. - From the **Paragraph/Formats** menu, select **Inline** and then **Italic**. - **Underline**: From the **Paragraph/Formats** menu, select **Inline** and then **Underline**. - **Strikethrough**: From the **Paragraph/Formats** menu, select **Inline** and then **Strikethrough**. - **Superscript**: From the **Paragraph/** **Formats** menu, select **Inline** and then **Superscript**. - **Subscript**: From the **Paragraph/Formats** menu, select **Inline** and then **Subscript**. - **Code**: From the **Paragraph/Formats** menu, select Inline and then **Code**. - **Paragraph**: From the **Paragraph/Formats** menu, select **Blocks** and then **Paragraph**. - **Blockquote**: From the **Paragraph/Formats** menu, select **Blocks** and then **Blockquote**. - **Division**: From the **Paragraph/Formats** menu, select **Blocks** and then **Div**. - **Preformatted**: From the **Paragraph/Formats** menu, select **Blocks** and then **Pre**. - **Change text color**: Use the **Text Color** drop-down to change text color. Click on the![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/678b9e7e-cb25-44e1-a218-ab9c6259bddc.png)icon. The color palette displays. Do one of the following: - Select one of the color swatches from the color palette. The selected text changes to that color. - Click the![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/be6f8d61-413c-4907-aa9a-2c87e79b4bd3.png)icon to select a custom color from the **Color Picker**. - Click the![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/166ea0a7-b6b0-4da6-b098-6f990208d3ec.png)icon to reset the text to its default color. - **Align text**: Follow these guidelines to align text: - **Left align:** Do one of the following: - From the editor toolbar, use the![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/7b4c3b0c-0585-425f-92fa-84f7b93dda7d.png)icon to left-align text. - From the **Paragraph/Formats** menu, select **Align** and then **Left**. - **Center align:** Do one of the following: - From the editor toolbar, use the![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/ce57dc05-690b-4440-aeed-98fc73a91e0e.png)icon to center-align text. - From the **Paragraph/Formats** menu, select **Align** and then **Center**. - **Right align**: Do one of the following: - From the editor toolbar, use the![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/0c88f089-db27-46a3-b08a-3b54c0581163.png)icon to right-align text. - From the **Paragraph/Formats** menu, select **Align** and then **Right**. - **Justify**: Do one of the following: - From the editor toolbar, use the![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/acdf1ae4-86e2-49e8-86f4-678997985c41.png)icon to justify text. - From the **Paragraph/Formats** menu, select **Align** and then **Justify**. - **Insert a bullet list**: Use the![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/1030c4be-1075-4263-b4fb-0949007d361e.png)icon to format text as a bulleted list. - **Insert a numbered list:** Use the![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/590cec4d-8356-4317-8ec4-089c72f77858.png)icon to format text as a numbered list. - **Indent text**: Click on the![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/352d9627-97e4-4354-bdd1-8d502959b7d0.png)icon to increase text indenting. - **Outdent text:** Click on the![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/a4b73eac-2e2d-4ce8-8a6d-bf534ea8f8bb.png)icon to decrease text indenting. --- ### Assignment Rules Panel Settings Select a task recipient and configure task re-assignment options. #### Select the Task Assignee Follow these steps to select the assignee for a task: 1. Select the Form Task object from the Process model. 2. Ensure that the **Configuration** panel displays. If not, [show it](/v1/docs/show-configuration-settings-for-a-process-model-object). Panels to configure this object display. 3. Expand the **Assignment Rules** panel. The **Assignment Type** setting displays. The **Request Starter** option is the default setting. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/db0cb6cb-0f79-49ea-871b-4c8685ed7014.png) 4. From the **Assignment Type** drop-down menu, select one of the following options: - **Users / Groups:** Select this option to assign the Task to a specified user or to a group member. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/17048bc4-ec3a-4370-bd10-e3c15e19b477.png) From the **Assigned Users/Groups** drop-down menu, select one or more users and/or groups for this Task. The Task is assigned following this protocol: - **One user:** The Task is assigned to the selected user. - **One or more users and/or group(s):** The Task is assigned randomly to one of those users or group members. The exception is if the **Self Service** toggle key is enabled, then the Task remains unassigned, in a queue, for one of those users to [self-assign from the **Self Service** Task page](/v1/docs/self-assign-tasks-from-a-queue). - **Previous Task Assignee:** Select this option to assign the Task to the assignee of the previous task. - **Request Starter:** Select this option to assign the Task to the Request starter. This is the default option. - **Process Variable:** Select this option to assign the Task determined by the value of a Request variable. The entered variable(s) may be one or both of the following: - **Variable Name (Users):** In this setting, enter the Request variable that contains the user ID(s) for one or more users. If more than one user ID is included the Request variable's value, then the Task is assigned randomly to one of those users. The exception is if the **Self Service** toggle key is enabled, then the Task remains unassigned, in a queue, for one of those users to [self-assign from the **Self Service** Task page](/v1/docs/self-assign-tasks-from-a-queue). - **Variable Name (Groups):** In this setting, enter the Request variable that contains a group ID(s). The Task is assigned randomly to one of the group members. The exception is if the **Self Service** toggle key is enabled, then the Task remains unassigned, in a queue, for one of those users to [self-assign from the **Self Service** Task page](/v1/docs/self-assign-tasks-from-a-queue). ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/d9f195e3-c514-4d55-82ff-c87334bbaa09.png) - **Rule Expression:** Select this option to assign the Task's assignee using one or more rules. The rule expressions follow the Friendly Enough Expression Language (FEEL) syntax described in [Expression Syntax Components](/v1/docs/feel-expression-syntax#expression-syntax-components). ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/3ed5ab04-62aa-48e3-b076-72cebff50d26.png) Each rule can only have one expression, but by using logical operators multiple conditions can be specified in that expression. You may use multiple rules to better confine the condition(s), and you may use [Magic Variables](/v1/docs/magic-variables) in your expression. To add an expression, click the add ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/0a84f89f-9a9f-4007-91c9-6fb9ac19f6f6.png) button. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/1cac35ec-1486-4c91-8442-ffd042e8ed71.png) Follow these steps to define an expression: 1. In the **FEEL** **Expression** setting, enter or edit the expression using the syntax components described in [Expression Syntax Components](/v1/docs/feel-expression-syntax#expression-syntax-components), and then press **Enter**. 2. From the **Assign to User/Group** drop-down menu, select the user or group to assign the Task to when the **FEEL Expression** evaluates to True. 3. From the **Default Assignment** drop-down menu, select a user or group to assign that Task to if none of the expressions evaluate as True. - **Process Manager:** Select **Process Manager** to assign the Task to the Process Manager. [Ensure to configure the Process Manager for this Process](/v1/docs/configure-general-process-settings). 5. Enable the **Self Service** toggle to allow group members to [self-assign the Task from a queue](/v1/docs/self-assign-tasks-from-a-queue). This option is only available if the **Assignment Type** is set to Users / Groups, Process Variable, or Rule Expression. 6. Enable the **Assign to Manager** toggle key to assign that Task to the manager of the task assignee. An Administrator can configure the manager for each user in their [user account](/v1/docs/edit-a-user-account#edit-user-settings). 7. Enable the **Lock User Assignment** toggle to ensure the Task is reassigned to the same user if the workflow returns to it. This is useful when the original assignee may need to clarify or update information they previously submitted.![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/749df072-8d44-438b-bd60-e9e6aba4805e.png) 8. Enable the **Allow Reassignment** toggle key to allow the Task assignee to reassign the Task if necessary. If the **Allow Reassignment** option is enabled, the **Reassign** button displays in the Task summary to allow for task reassignmen. For more information, see [View a Task Summary](/v1/docs/open-a-task#summary). 9. Enable the **Allow Manager Escalation** toggle key to automatically reassign this Task to the Task assignee's manager. An Administrator can configure the manager for each user in their [user account](/v1/docs/edit-a-user-account#edit-user-settings). > [!NOTE] > If you enable the **Allow Reassignment** option, make sure the Task is assigned to multiple users or to a group. Otherwise, even though the **Reassign** button will appear in the Task summary, the assignee will have no available users to reassign the Task to. If this Form Task object is configured to assign the Task to an anonymous person who started this Request via [Web Entry](/v1/docs/form-task#web-entry-panel-settings), the settings described here are disabled because these Form Task object settings only configure which authenticated user(s) may assigned this Task. Therefore, to configure these settings, either disable Web Entry or select that authenticated users may start Requests from this object via Web Entry. See [Web Entry Panel Settings](/v1/docs/form-task#web-entry-panel-settings). --- ### Notifications Panel Settings Configure when to send task notifications. Task notifications are shown in ProcessMaker Platform and can be accessed using the Notifications ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(297).png) icon on the top right the screen. Task notifications can be sent to the following users: - **Requester:** This is the user who started the process. - **Task assignee:** This is the user to whom the task is currently assigned. - **Request participants:** All users you have participated in the process. - **Process Manager:** The user set as the [Process Manager in process configuration](/v1/docs/edit-the-process-model-information). > [!NOTE] > - A copy of these notifications is also sent as automated emails to users. To disable these emails, see [User Profile Settings](https://docs.processmaker.com/docs/profile-settings#edit-task-notifications-email-settings). > - To setup custom email notifications, see [email notifications for Tasks](/v1/docs/form-task#set-email-notifications). #### Set Task Notifications Task notifications can be sent to participants when following events occur. | Task Notifications | | --- | | **Assigned** | Send a notification when this task is assigned or reassigned. | | **Completed** | Send a notification when this task is completed | | **Due** | Send a notification when this task is due. | Follow these steps to set Task notifications in a Form Task object: 1. Expand the **Notifications** panel. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(342).png) 2. From the **Requester** settings, set Task notifications for the Requester. 3. From the **Assignee** settings, set Task notifications for the assignee of the current task. The **Assigned** and **Due** notifications are enabled by default for task assignees. 4. From the **Participant** settings, set Task notifications for all process participants. 5. From the **Process Manager** settings, set Task notifications for the [Process Manager](/v1/docs/process-manager). --- ### Email Notifications Panel Settings Configure when to send email notifications to task recipients. Email notifications can be sent to the following recipients: - [Users](/v1/docs/user-accounts#what-is-a-user) and/or [group](/v1/docs/groups#what-is-a-group) members. ***Note:*** Members of a child group within a parent group will not receive email notifications unless the child group is selected in the email notification configuration. - Specific email addresses for individuals who are not users in your ProcessMaker Platform instance. The email body for the Task notification may be plain text or an [Email](/v1/docs/screens#email-1)-type Screen. Email notifications are sent to recipients based on the following events: - **Task trigger:** Send email notifications when a Task is activated. - **Task completion:** Send email notifications when a Task is completed. - **Value in Request data or Magic Variable:** Specify an expression to conditionally send the email notification when a Request Variable or [Magic Variable](/v1/docs/magic-variables) meets a specific setting or condition. Specify this condition using an expression syntax described in [Expression Syntax Components](/v1/docs/form-task#expression-syntax-components-1). #### Set Recipients for This Email Notification Use the **To**, **Cc**, and **Bcc** settings to set which users, groups, and/or email addresses to send this email notification. Follow these steps to set the recipient(s) for this email notification: 1. Select the Form Task object from the Process model. 2. Click the **Show Configuration** button ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/57210434-a8cc-40e9-8973-b14d0841196a.png) in the upper right of the Process Modeler canvas. 3. Expand the **Email Notifications** panel if it is not presently expanded. The **Notifications** setting displays. 4. Click the ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/0a84f89f-9a9f-4007-91c9-6fb9ac19f6f6.png) icon to add an email notification. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Add Notification.png) 5. From the **To**, **Cc**, or **Bcc** settings, click the ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Plus Icon.png) icon to display the **Add a** **Recipient** window. 6. From the **Recipient Type** dropdown, select the recipient(s) of this email: - **Users and Groups:** Send this email to user(s) or group(s). When this option is selected, the **Users and Groups** setting displays. Select a user or group from the available list. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Recipient User-Groups.png) - **Request Starter:** Send this email to the user who started this Request. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Recipient - Requester.png) - **Participants:** Send this email to all users participating in this Request. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Recipient - Participants.png) - **Assigned User:** Send this email to the user currently assigned to the task. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Recipient - Assiigned User.png) - **User ID:** Send this email to a user based on the value of a [Request variable](/v1/docs/request-variable). When this option is selected, the **User ID** setting displays. Enter a variable name in this setting. A valid user name must be assigned to this variable in a previous step in the Request. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Recipient - User ID.png) - **Email Address:** Send this email to the entered email address. When this option is selected, the **Send to Email Address** setting displays. Enter a single email address or multiple email addresses separated by commas with no spaces. For example: `amanda@mycompany.com,john@homeoffice.com`. Alternatively, enter a Request variable in [mustache syntax](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/mustache.5.html) that contains a comma delimited string of multiple email addresses. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Recipient - Email.png) - **Process Manager:** Send this email to the Process Manager assigned in the [Process's configuration](/v1/docs/edit-the-process-model-information). ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Recipient - Manager.png) 7. Click **Add** to list the recipients. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Recipients.png) 8. Click the ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Blue Gear Icon.png) icon to edit an email recipient that is currently added. 9. Click the ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Blue Trash Icon.png) icon to remove an email recipient that is currently added. #### Set the Email Server From the **Email Server** drop-down menu, select an email server. The **Default Email Server** option is the default. If additional [email servers are configured](/v1/docs/email-default-settings) in Admin Settings, they will be displayed in the **Email Server** drop-down menu. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Email Server.png) #### Set the Email Notification's Subject and Body Content [Email Notifications](/v1/docs/form-task#email-notifications-panel-settings) settings in Form Task objects are not included when importing a Process. Configure Email Notifications settings after importing the Process instead. Follow these steps to configure email notification settings: 1. From the **Subject** setting, revise the default text if necessary that displays as the email subject. By default, ProcessMaker Platform displays the current Form Task object's [**Name**](/v1/docs/form-task#edit-the-element-name) as part of the **Subject**. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Notification Subject.png) 2. From the **Body** setting, select one of the following options: - **Plain Text:** Select the **Plain Text** option to enter plain text to display as the email body. This is the default option. Follow these steps: 1. From the **Body** setting, ensure that the **Plain Text** option is selected. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Plain Body Recipient.png) 2. In the setting below the **Plain Text** option, revise the default text if necessary. - **Display Screen:** Select the **Display Screen** option to select an [Email](/v1/docs/screens#email-1)-type [Screen](/v1/docs/screens) to use as the email body. Follow these steps: 1. From the **Body** setting, ensure that the **Display Screen** option is selected. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Screen Body Recipient.png) 2. From the drop-down menu below the **Display Screen** option, select a screen from the list. Only Email-type Screens display from this drop-down menu. 3. Optionally, click the **Open Screen** link to view and/or edit your selected Screen. ***Note:*** You must have appropriate [Screen category](/v1/docs/permission-descriptions-for-users-and-groups#screens) permissions to view and/or edit the selected Screen. #### Select Files to Attach to This Email Notification Use the **Attach File** setting to specify one or more file(s) to attach with this email notification. Follow these steps: 1. Click the **+File** button to specify the files to attach to this email notification. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/28fe7496-7fb6-49bc-ad4b-b3fec02092c7.png) 2. From the **Source** setting, select one of the following options: - **URL**: Select the **URL** option to provide a link to the file to be attached. Follow these guidelines: 1. In the **URL** setting, enter the URL referencing an attached file to be accessed from a Web address. ![img](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/ec652e67-c861-4a6c-9f9b-bc0cf8eef419.png) 2. Click **Save**. The URL referencing the file displays. - **Request Variable**: Select the **Request Variable** option if the file to be attached can be referenced through a request variable. Follow these guidelines: 1. In the **Request Variable Name** setting, enter a Request variable name without the [mustache syntax](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/mustache.5.html). This variable must already be linked to a [File Upload](/v1/docs/file-upload-control#variable-panel-settings) control in a Screen in the same Request. When the Request is in-progress, any file uploaded using this File Upload control is attached to this email notification. This is a required setting. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/28fe7496-7fb6-49bc-ad4b-b3fec02092c7.png) 2. Click **Save**. The Request variable referencing the file displays. - **Request Array**: Select the **Request Array** option to attach multiple files. Follow these guidelines: 1. In the **Request Array Variable Name** setting, enter an array-type Request variable. This variable must already be linked to a [File Upload control with **Upload Multiple Files**](/v1/docs/file-upload-control#variable-panel-settings) option enabled in the same Request. When the Request is in-progress, any files uploaded using this File Upload control are attached to this email. 2. In the **Variable in Array** setting, optionally enter the name of a variable in the **Request Array Variable** containing ID of the file to be attached. If the Request Array Variable is a simple array containing a list of files, leave this setting blank. 3. Click **Save**. The Request variable referencing the files displays. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/ad57273c-9135-4fb9-8a7c-d5996abad3fc.png) 3. Repeat steps 3 and 4 to add additional files. 4. Optionally, click on the **Delete** ![img](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/23e356c8-5020-45b5-adeb-21139c302c3d.png) icon to delete any referenced file from being attached to the email. #### Set When This Email Notification Sends Use the **Send At** or **Expression** settings to set when this email notification is sent. Do one of the following based on when you need the email notification sent: 1. From the **Send At** setting, select one of the following options: - **Task Start:** Select the **Task Start** option to send this email notification when this Form Task is activated. This is the default option. - **Task Completion:** Select the **Task Completion** option to send this email notification when this Form Task completes (when the Task assignee submits the Screen associated with this Task). ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/bb869c14-a5f1-446a-a8b9-121d306dd985.png) 2. In the **Expression** setting, optionally enter the expression to conditionally send the email notification when a Request data object or [Magic Variable](/v1/docs/magic-variables) meets a specific setting or condition, and then press **Enter**. Specify this condition using an expression syntax described in [Expression Syntax Components](/v1/docs/form-task#expression-syntax-components-1). Use logical operators to specify multiple conditions in that expression if necessary. If the **Expression** setting does not contain a value, then the **Send At** setting determines when to send email notifications for this Task. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/ef82bc85-c8af-44a9-a7ef-40b8e5fce840.png) 3. Click **Close**. This email notification is saved and displays below the **Notifications** setting using the **Subject** setting as the email notification label. 4. Click the **Edit** icon ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/4aacbfbc-7885-4a99-9bcf-6cbdac243dec.png) beside the email notification to edit. 5. Click the **Duplicate** icon ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/64bd8d4a-1c88-46e9-9cd7-e5ed6d1f1cb2.png) beside the email notification to duplicate it. 6. Click the **Delete** icon![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/ea06997b-5075-4f5b-bf1d-1b81adbbb9b7.png)beside the email notification to delete. The following message displays to confirm deletion of this email notification: **Are you sure you want to delete this notification?** ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/9381e764-d3ac-4c52-9fc2-961a86cc9e79.png) 7. Click **Delete**. > [!WARNING] > Consider carefully when deleting an email notification. Deleting a configured email notification cannot be undone. #### Default Email Notification for New Form Tasks When a new **Form Task** is created, the platform automatically generates a default email notification to streamline case communication. This built-in configuration includes the following pre-filled values: - **Recipient:** `Assigned User` - **Email Server:** `Default Email Server` (configured in [Admin > Email Settings](/v1/docs/email-settings)) - **Subject:** `RE: {{_user.firstname}} assigned you in "{{_task_name}}"` - **Body:** Uses the **Default Email Task Notification** display-screen - **Send At:** `Task Start` (immediately when the task is assigned) This auto-generated configuration ensures that assigned users receive timely notifications without requiring manual setup. You can customize or disable the notification as needed by editing the Form Task’s **Email Notifications** panel settings. #### Actions By Email Allow task recipients to complete tasks directly from their email inbox without logging into the ProcessMaker Platform. When a task is assigned, the user will receive an email notification through which they can take action on the task. > [!WARNING] > Forwarded Emails > > If an Actions by Email notification is forwarded to another user, that user can still complete the action, and the system will treat it as if it came from the original assignee. Therefore, use caution when forwarding these emails, as this may allow unauthorized Task actions. > [!TIP] > View an example of how to [enable Actions by Emails for a task](/v1/docs/example-enable-actions-by-email-for-a-form-task). #### Steps to enable Actions by Email Follow these steps to enable Actions By Email for task recipients: 1. Select the Form Task from the Process model. 2. Click the **Show Configuration** button ![Hamburger Icon](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Hamburger%20Icon.png) in the upper right corner of the Modeler. 3. Expand the **Email Notifications** panel. The **Actions By Email** toggle displays below the **Notifications** setting. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Form Task - Email Notifications.png) 4. Enable the **Actions By Email** toggle to display settings for it. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Form Task - Actions By Email.png) 5. From the **Email Server** drop-down menu, select an email server. The **Default Email Server** option is the default. If additional [email servers are configured](/v1/docs/email-default-settings) in Admin Settings, they will be displayed in the **Email Server** drop-down menu. 6. In the **Subject** setting, enter the subject of the email. For example, enter the decision that the email recipient must take through this email. 7. From the **Screen** drop-down menu, select an email-screen. When an email notification is sent, this screen will be displayed to the participant through which they can take an action on the task. > [!WARNING] > Ensure that this screen uses Submit button controls to allow users to take an action on task. The Link URL control can also be used to take the user to an alternate form for task completion. 8. Enable the **Require Login** setting to require a user to log in before filling out the screen. 9. From the **Screen for Completed** drop-down menu, select a completion screen to indicate to the user that the task was successfully submitted. --- ### Web Entry Panel Settings Web Entry provides a seamless and straightforward method for initiating or completing cases, catering to both anonymous and authenticated users. This feature allows external users to start and work on cases through a link without the need to access the ProcessMaker Platform dashboard. #### Configure Web Entry for a Task Follow these steps to select to configure web entry for a task: 1. Select the Form Task object from the Process model. 2. Ensure that the **Configuration** panel displays. If not, [show it](/v1/docs/show-configuration-settings-for-a-process-model-object). Panels to configure this object display. 3. Expand the **Web Entry** panel if it is not presently expanded. The **Mode** setting displays. 4. From the **Mode** drop-down menu, select one of the following options. **Disabled** Select the **Disabled** option to disable Web Entry for this task and allow access through ProcessMaker Platform only. This is the default setting. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(299).png) **Anonymous** Select the Anonymous option to allow the task to be accessed without having to log in to ProcessMaker. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(301).png) If selecting the **Anonymous** option, consider using the following settings: 1. Select **Require Valid Session** to require users to log in to the ProcessMaker Platform to access the task. Even though users will log in, the task will be submitted anonymously. 2. From the **Completed Action** drop-down menu, select one of the following options: 1. **Screen**: Select the **Screen** option to display a screen after the Task assignee submits the Task. - From the **Screen For Completed** drop-down menu, select the Screen. This drop-down menu displays only Display types to display a message to the request starter. This is a required setting. - Optionally, click the **Open Screen** link to view the selected Screen in a separate Web browser window, or create a new screen using the **+Create a New Screen** link. - Select the **Enable Password Protect** setting to require a password to access the Web Entry. 2. **URL:** Select the URL option to indicate that the Task assignee is redirected to a URL after the Task is completed. - In the **Redirect URL** setting, enter the URL and then press Enter. The redirect URL supports mustache syntax to reference the value of a Request variable as the URL. This is a required setting. - Select the **Enable Password Protect** setting to require a password to access the Web Entry URL. **Authenticated** Select the **Authenticated** option to assign the Task to an authenticated user or group member. If an authenticated user or group member is already selected from the [**Assignment Rules** panel](/v1/docs/form-task#assignment-rules-panel-settings), then only one of those user(s) may view this task. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/image(300).png)If selecting the **Authenticated** option, consider using the following settings: 1. From the **Completed Action** drop-down menu, select one of the following options: 1. **Screen**: Select the **Screen** option to display a screen after the Task assignee submits the Task. - From the **Screen For Completed** drop-down menu, select the Screen. This drop-down menu displays only Display types to display a message to the request starter. This is a required setting. - Optionally, click the **Open Screen** link to open the selected Screen in a separate Web browser window, or create a new screen using the **+Create a New Screen** link. 2. **URL:** Select the URL option to indicate that the Task assignee is redirected to a URL after the Task is completed. - In the **Redirect URL** setting, enter the URL and then press Enter. The redirect URL supports mustache syntax to reference the value of a Request variable as the URL. This is a required setting. #### Exclude Data and Copy URL Follow these steps to prevent sensitive data being accessed in the web entry and learn how to share the web entry URL. 1. From the **Exclude Data** setting, optionally exclude any Request data from being included in the Web Entry Task so that it does not display in the Screen for that Task. Specify the Request variable name to exclude as indicated by the Screen control's **Variable Name** setting value. 2. Click the ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/c670b4e5-2ec0-4da4-a181-df363b17d782.png) icon to add a variable. 3. Enter the Request variable name into the setting. 4. If necessary, click the ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/a6b0c722-3b9b-49a3-85ba-11a281e10a86.png) icon to remove a variable. 5. The **Web Entry URL** displays the URL to use for viewing the form associated with this task. The **Web Entry URL** value cannot be changed. ProcessMaker Platform generates this URL using the following structure: `ProcessMaker Platform instance domain/webentry/Web Entry numerical instance/Identifier Value of this Form Task object`. 6. Click the **Copy** button below the **Web Entry URL** setting to copy the Web Entry URL so that it is available in your clipboard. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/c92b741b-3b19-4ed3-8e35-db8e168fd1f3.png) > [!NOTE] > - If you are copying an anonymous Web Entry link while logged in to ProcessMaker, the following message will be displayed. This message indicates that you must log out in order to use this Web Entry link. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/e45fb163-3b14-4b11-9172-44a0429b38cb.png) > - Users accessing an *authenticated* Web Entry task via a direct URL see an **Unauthorized** message if they are not assigned to the task. The message reads: > > ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Unautorized Message - Authenticated Web Entry.png) > > 📝 Superadmin users can still access the task normally from within the **Requests** or **Cases** view. This restriction only applies when attempting to access the task via **direct Web Entry URLs** without being assigned. 7. The **Embed Code** setting displays the JavaScript that contains the Web Entry URL to embed into your Web server's or blog's HTML header. If necessary, click the **Copy** button below the **Embed Code** setting to copy the Web Entry URL so that it is available in your clipboard. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/38491898-65ae-4765-9742-497abb1e35b0.png) 8. If this Form Task object's Web Entry uses a Conversational-type Screen to provide a chat-style interaction with the Request starter, optionally click the **Options** button below the **Embed Code** setting to configure how the chat box displays in the embedded container to which the Web Entry's JavaScript code is applied. When the **Options** button is clicked, the **Embed Options** screen displays. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/aced0b1e-8e68-4e68-99e3-7472cfac56a4.png) Configure how the chat box displays in the embedded container from the following options: 1. From the **Position** setting, select one of the following options: - **Fill Container:** The chat box displays the width of the container to which the Web Entry's JavaScript code is applied. This is the default setting. When the **Fill Container** setting is selected, all other settings in the **Embed Options** screen are disabled. - **Top Left:** The chat box displays in the top left corner of the container to which the Web Entry's JavaScript code was applied. - **Top Right:** The chat box displays in the top right corner of the container to which the Web Entry's JavaScript code was applied. - **Bottom Left:** The chat box displays in the bottom left corner of the container to which the Web Entry's JavaScript code was applied. - **Bottom Right:** The chat box displays in the bottom right corner of the container to which the Web Entry's JavaScript code was applied. 2. In the **Title** setting, enter the title that displays in the chat box. **Form** is the default setting. This setting does not apply when the **Fill Container** option is selected from the **Position** setting. 3. From the **Color** setting, select the color that displays for button to show the chat box and for the chat box frame itself. The left-most color option is the default. This setting does not apply when the **Fill Container** option is selected from the **Position** setting. 4. From the **Icon** setting, select an icon that displays to show the chat box. The **Question Circle** is the default option. This setting does not apply when the **Fill Container** option is selected from the Position setting. 5. Click **Save**. > [!WARNING] > **Considerations for Using Web Entry** > > - **Parallel Tasks**: When designing a process, parallel tasks connected through a parallel gateway do not support the use of Web Entries. > - **Request Summary**: The Screen used for Web Entry does not display in the **Forms** tab in [Request summary](/v1/docs/request-details). > - **Multi-instance (parallel) Loops**: Web Entry settings are not supported for tasks configured with [Multi-instance (Parallel) Loops](/v1/docs/form-task#loop-characteristics-panel-settings). > - **Embedding Rules**: Due to the default Laravel cookies, Web Entries cannot be embedded into a third-party site for authenticated users. > - **Testing Web Entries**: When testing an anonymous Web Entry during process design, always test or open the Web Entry link in a private (incognito) window. --- ### Advanced Panel Settings #### Edit the Node's Identifier Value Process Modeler automatically assigns a unique value to each Process node added to a Process model. However, a node's identifier value can be changed if it is unique to all other nodes in the Process model, including the Process model's identifier value. > [!WARNING] > All identifier values for all nodes in the Process model must be unique. Follow these steps to edit the identifier value for a Form Task object: 1. Select the Form Task object from the Process model in which to edit its identifier value. 2. Ensure that the **Configuration** panel displays. If not, [show it](/v1/docs/show-configuration-settings-for-a-process-model-object). Panels to configure this object display. 3. Expand the **Advanced** panel if it is not presently expanded. The **Node Identifier** setting displays. This is a required setting. ![](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/4081555b-976d-468c-b8a0-e54d64503dfd.png) 4. In the **Node Identifier** setting, edit the Form Task object's identifier to a unique value from all nodes in the Process model and then press **Enter**. ## Related - [Screens](/screens.md)