Update Task (Microsoft Planner) activity

An activity that changes a task in Microsoft Planner.

Configure the Update Task activity

Examples

(External) AgilePoint NX Connector For Microsoft Planner.
Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Prerequisites

AgilePoint NX OnDemand (public cloud), AgilePoint NX PrivateCloud, or AgilePoint NX OnPremises v9.0 Software Update 1 or higher.

Good to Know

To send an email notification, click Advanced > Email Notifications .
For more information, refer to Email Notifications screen (Process Activities).
In most text fields, you can use process data variables as an alternative to literal data values.
You can configure whether this activity waits for other activities before it runs.
For more information, refer to How Do I Configure an Activity to Wait for Other Incoming Activities?
This section shows the configuration settings on the configuration screens for this activity. Other configuration settings apply to system activities. For more information, refer to:
Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

How to Start

Open Process Builder.
For information about how to open this screen, refer to Process Builder.
In Process Builder, in the Activity Library, open the Microsoft Planner tab.
On the Microsoft Planner tab, drag the Update Task activity onto your process.

General Configuration

Specifies the basic settings for the Update Task activity.

Good to Know

Documentation for this screen is provided for completeness. The fields are mostly self-explanatory.

Fields

Field Name	Definition
Display Name	Description: Specifies the activity name that shows in your process. Allowed Values: One line of text (a string). Accepted: Letters Numbers Spaces Default Value: None Accepts Variables: No Example: This is a common configuration field that is used in many examples. Refer to: Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.
Description	Description: Specifies an optional text description for your activity. Allowed Values: More than one line of text. Default Value: None Accepts Variables: No

Field Name

Definition

Display Name

Description:

Specifies the activity name that shows in your process.

Allowed Values:

One line of text (a string).

Accepted:

Letters
Numbers
Spaces

Default Value:

None

Accepts Variables:

Example:

This is a common configuration field that is used in many examples. Refer to:

Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Description

Description:: Specifies an optional text description for your activity.
Allowed Values:: More than one line of text.
Default Value:: None
Accepts Variables:: No

Update Task Configuration > Basic tab

Specifies the information to change a task in Microsoft Planner.

Fields

Field Name	Definition
Microsoft Planner	Description: Specifies the access token that connects to Microsoft Planner. Allowed Values: A list of access tokens configured for your environment. Default Value: None Accepts Variables: No Example: Refer to: (External) AgilePoint NX Connector For Microsoft Planner.
Create	Opens this Screen: Access Token for Microsoft 365 Function of this Screen: Configure an access token to connect to Microsoft 365. Example: Refer to: (External) AgilePoint NX Connector For Microsoft Planner.
Task ID	Description: Specifies the ID of the task to change. The task ID comes from Microsoft Planner. Allowed Values: A task ID from Microsoft Planner. Default Value: None Accepts Variables: Yes Example: Refer to: (External) AgilePoint NX Connector For Microsoft Planner. Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Bucket Name Or ID	Description: Specifies the name or ID of the bucket in which to change the task. Allowed Values: One line of text (a string) that represents a bucket name in Microsoft Planner. An alphanumeric string that represents a bucket ID. The bucket ID comes from Microsoft Planner. Default Value: None Accepts Variables: Yes Example: Refer to: (External) AgilePoint NX Connector For Microsoft Planner. Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
New Task Name	Description: Specifies the name for the task to create in Microsoft Planner. Allowed Values: One line of text (a string). Accepted: Letters Numbers Spaces Special characters Default Value: None Accepts Variables: Yes Example: Refer to: (External) AgilePoint NX Connector For Microsoft Planner. Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Preview Type	Description: Specifies the preview for the task. The value specified in the field shows as a preview on the task card. Allowed Values: A preview type from the list. Default Value: None Accepts Variables: Yes Example: Refer to: (External) AgilePoint NX Connector For Microsoft Planner. Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Start Date	Description: Specifies the start date for the task. Allowed Values: A date from the date picker. Default Value: None Example: Refer to: (External) AgilePoint NX Connector For Microsoft Planner. Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Due Date	Description: Specifies the date when the task is due. Allowed Values: A date from the date picker. Default Value: None Example: Refer to: (External) AgilePoint NX Connector For Microsoft Planner. Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Assignee ID Or Email	Description: Specifies the user ID or email address of the Microsoft Planner user to assign the task. Allowed Values: An email address from the list. When you select the access token from the Microsoft Planner field, this field shows the email addresses associated with the access token. One or more user IDs or email addresses, separated by semicolons (;). The user IDs or email addresses must be associated with the Microsoft Planner users. Default Value: None Accepts Variables: Yes Example: Refer to: (External) AgilePoint NX Connector For Microsoft Planner. Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Task Notes	Description: Specifies a description for the task. Allowed Values: More than one line of text. Default Value: None Accepts Variables: No Example: Refer to: (External) AgilePoint NX Connector For Microsoft Planner. Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

Update Task Configuration > Advanced tab

Configures the checklist items for the task in Microsoft Planner.

Fields

Field Name	Definition
Microsoft Planner	Description: Specifies the access token that connects to Microsoft Planner. Allowed Values: A list of access tokens configured for your environment. Default Value: None Accepts Variables: No Example: Refer to: (External) AgilePoint NX Connector For Microsoft Planner.
Create	Opens this Screen: Access Token for Microsoft 365 Function of this Screen: Configure an access token to connect to Microsoft 365. Example: Refer to: (External) AgilePoint NX Connector For Microsoft Planner.
Task ID	Description: Specifies the ID of the task to change. The task ID comes from Microsoft Planner. Allowed Values: A task ID from Microsoft Planner. Default Value: None Accepts Variables: Yes Example: Refer to: (External) AgilePoint NX Connector For Microsoft Planner. Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Bucket Name Or ID	Description: Specifies the name or ID of the bucket in which to change the task. Allowed Values: One line of text (a string) that represents a bucket name in Microsoft Planner. An alphanumeric string that represents a bucket ID. The bucket ID comes from Microsoft Planner. Default Value: None Accepts Variables: Yes Example: Refer to: (External) AgilePoint NX Connector For Microsoft Planner. Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Priority	Description: Specifies the importance of a task. Allowed Values: Important Low Medium Urgent Default Value: None Accepts Variables: Yes Example: Refer to: (External) AgilePoint NX Connector For Microsoft Planner. Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Progress	Description: Specifies the status of the task. Allowed Values: A status from the list. Default Value: None Accepts Variables: Yes Example: Refer to: (External) AgilePoint NX Connector For Microsoft Planner. Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Labels	Description: Specifies one or more labels that are used as categories for the task. Allowed Values: A label from the list. When you select the access token from the Microsoft Planner field, this field shows the label names associated with the access token. The line of text represents one or more labels, separated by semicolons (;). If the labels entered in this field do not exist in your Microsoft Planner environment, when this activity runs, the activity creates the labels and adds them to the task. Default Value: None Accepts Variables: Yes Example: Refer to: (External) AgilePoint NX Connector For Microsoft Planner. Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Repeating Node	Description: Specifies a complex schema node from which the values of the node can be added as the checklist items to the task. Allowed Values: A complex schema node. Default Value: None Accepts Variables: Yes Example: Refer to: (External) AgilePoint NX Connector For Microsoft Planner. Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Checklist Items	Description: Specifies the name of the checklist item to add to the task. Allowed Values: One line of text (a string) that represents a checklist item. A parent node from the complex schema node. If you specify a complex schema node in the Repeating Node field, you must specify a parent node in this field. Default Value: None Accepts Variables: Yes Example: Refer to: (External) AgilePoint NX Connector For Microsoft Planner. Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Status	Description: Specifies the value of the checklist item. Allowed Values: Checked Unchecked Default Value: None Accepts Variables: Yes Example: Refer to: (External) AgilePoint NX Connector For Microsoft Planner. Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Create	Function: Adds a row for the CheckList Items and Status fields. Limitations: In the Repeating Node field, if you specify a complex schema node, this field is disabled.
Delete	Function: Deletes the selected row.