Skip to content

Commit c34ed07

Browse files
committed
Review
1 parent 50621f2 commit c34ed07

5 files changed

Lines changed: 9 additions & 13 deletions

File tree

content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/multi-user-task.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -376,13 +376,12 @@ To add a parameter to the **Task name** or the **Task description**, do the foll
376376
{{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/user-task/parameter-example.jpg" alt="Parameter Example" class="no-border" >}}
377377

378378
{{% alert color="info" %}}
379-
Make sure that the attribute you use in the expression is of the **String** type. If your attribute is a different type, you must convert it using a build-in function:
379+
Make sure that the attribute you use in the expression is of the **String** type. If your attribute is of a different data type, you must convert it using a build-in function:
380380

381381
* For **Date and time** attributes, use the `formatDateTime()` function to define the desired display format.
382382
* For all other types (such as **Integer**, **Decimal**, or **Boolean**), use the `toString()` function.
383383
{{% /alert %}}
384384

385-
386385
4. In the **Template** setting, write the text you would like to display and type **Index** of the parameter you would like to include. For example, you can add a template for the **Task description** specifying the name of the workflow and what the workflow due date is :
387386

388387
{{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/user-task/task-description-example.jpg" alt="Task Description Example" class="no-border" >}}

content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/user-task.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -175,7 +175,7 @@ To add a parameter to the **Task name** or the **Task description**, do the foll
175175
{{< figure src="/attachments/refguide/modeling/application-logic/workflows/workflow-elements/user-task/parameter-example.jpg" alt="Parameter Example" class="no-border" >}}
176176

177177
{{% alert color="info" %}}
178-
Make sure that the attribute you use in the expression is of the **String** type. If your attribute is a different type, you must convert it using a build-in function:
178+
Make sure that the attribute you use in the expression is of the **String** type. If your attribute is of a different data type, you must convert it using a build-in function:
179179

180180
* For **Date and time** attributes, use the `formatDateTime()` function to define the desired display format.
181181
* For all other types (such as **Integer**, **Decimal**, or **Boolean**), use the `toString()` function.

content/en/docs/refguide10/modeling/application-logic/workflows/workflow-elements/multi-user-task.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -380,13 +380,12 @@ To add a parameter to the **Task name** or the **Task description**, do the foll
380380
{{< figure src="/attachments/refguide10/modeling/application-logic/workflows/workflow-elements/user-task/parameter-example.jpg" alt="Parameter Example" class="no-border" >}}
381381

382382
{{% alert color="info" %}}
383-
Make sure that the attribute you use in the expression is of the **String** type. If your attribute is a different type, you must convert it using a build-in function:
383+
Make sure that the attribute you use in the expression is of the **String** type. If your attribute is of a different data type, you must convert it using a build-in function:
384384

385385
* For **Date and time** attributes, use the `formatDateTime()` function to define the desired display format.
386386
* For all other types (such as **Integer**, **Decimal**, or **Boolean**), use the `toString()` function.
387387
{{% /alert %}}
388388

389-
390389
4. In the **Template** setting, write the text you would like to display and type **Index** of the parameter you would like to include. For example, you can add a template for the **Task description** specifying the name of the workflow and what the workflow due date is :
391390

392391
{{< figure src="/attachments/refguide10/modeling/application-logic/workflows/workflow-elements/user-task/task-description-example.jpg" alt="Task Description Example" class="no-border" >}}

content/en/docs/refguide10/modeling/application-logic/workflows/workflow-elements/user-task.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -122,13 +122,12 @@ To add a parameter to the **Task name** or the **Task description**, do the foll
122122
{{< figure src="/attachments/refguide10/modeling/application-logic/workflows/workflow-elements/user-task/parameter-example.jpg" alt="Parameter Example" class="no-border" >}}
123123

124124
{{% alert color="info" %}}
125-
Make sure that the attribute you use in the expression is of the **String** type. If your attribute is a different type, you must convert it using a build-in function:
125+
Make sure that the attribute you use in the expression is of the **String** type. If your attribute is of a different data type, you must convert it using a build-in function:
126126

127127
* For **Date and time** attributes, use the `formatDateTime()` function to define the desired display format.
128128
* For all other types (such as **Integer**, **Decimal**, or **Boolean**), use the `toString()` function.
129129
{{% /alert %}}
130130

131-
132131
4. In the **Template** setting, write the text you would like to display and type **Index** of the parameter you would like to include. For example, you can add a template for the **Task description** specifying the name of the workflow and what the workflow due date is :
133132

134133
{{< figure src="/attachments/refguide10/modeling/application-logic/workflows/workflow-elements/user-task/task-description-example.jpg" alt="Task Description Example" class="no-border" >}}

content/en/docs/refguide9/modeling/application-logic/workflows/workflow-elements/user-task.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -70,13 +70,12 @@ To add a parameter to the **Task name** or the **Task description**, do the foll
7070

7171
{{< figure src="/attachments/refguide9/modeling/application-logic/workflows/workflow-elements/user-task/parameter-example.jpg" alt="Parameter Example" class="no-border" >}}
7272

73-
{{% alert color="info" %}}
74-
Make sure that the attribute you use in the expression is of the **String** type. If your attribute is a different type, you must convert it using a build-in function:
73+
{{% alert color="info" %}}
74+
Make sure that the attribute you use in the expression is of the **String** type. If your attribute is of a different data type, you must convert it using a build-in function:
7575

76-
* For **Date and time** attributes, use the `formatDateTime()` function to define the desired display format.
77-
* For all other types (such as **Integer**, **Decimal**, or **Boolean**), use the `toString()` function.
78-
{{% /alert %}}
79-
76+
* For **Date and time** attributes, use the `formatDateTime()` function to define the desired display format.
77+
* For all other types (such as **Integer**, **Decimal**, or **Boolean**), use the `toString()` function.
78+
{{% /alert %}}
8079

8180
4. In the **Template** setting, write the text you would like to display and type **Index** of the parameter you would like to include. For example, you can add a template for the **Task description** specifying the name of the workflow and what the workflow due date is :
8281

0 commit comments

Comments
 (0)