|
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:
|
|
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:
|
|
Group Name Or ID
|
- Description:
- Specifies the name or ID of the Microsoft Planner group
for which to create the task.
- Allowed Values:
-
- A group name from the list.
When you select the access token from the Microsoft Planner field,
this field shows the group names associated with the access token. - One line of text (a string) represents a group name.
If the group name entered in this field does not exist in the Microsoft Planner environment,
when this activity runs, the activity creates the group with the name specified in this field.
- An alphanumeric string that represents a group ID.
The group ID comes from Microsoft Planner.
- Default Value:
- None
- Accepts Variables:
- Yes
- Example:
- Refer to:
- 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?
|
|
Plan Name Or ID
|
- Description:
- Specifies the name or ID of the plan in which to create the task.
- Allowed Values:
-
- A plan name from the list.
When you select the access token from the Microsoft Planner field,
this field shows the plan names associated with the access token.
- An alphanumeric string that represents a plan ID.
The plan ID comes from Microsoft Planner.
- Default Value:
- None
- Accepts Variables:
- Yes
- Example:
- Refer to:
- 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 create the task.
- Allowed Values:
-
- Default Value:
- None
- Accepts Variables:
- Yes
- Example:
- Refer to:
- 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 Name |
- Description:
- Specifies the name of 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:
- 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:
-
- Default Value:
- None
- Accepts Variables:
- Yes
- Example:
- Refer to:
- 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:
- 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:
- 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:
- 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:
-
- Default Value:
- None
- Accepts Variables:
- Yes
- Example:
- Refer to:
- 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:
-
- Default Value:
- None
- Accepts Variables:
- Yes
- Example:
- Refer to:
- 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:
-
|
Delete  |
- Function:
- Deletes the selected row.
|
|
Store Task ID In This Variable (String)
|
- Description:
- Specifies a variable to store the ID of the task.
The task ID comes from Microsoft Planner.
- Allowed Values:
- A variable.
Format:
Accepted:
- Letters
- Numbers
- Special characters
Not Accepted:
- Default Value:
- None
- Accepts Variables:
- Yes
- Example:
- Refer to:
- 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?
|
>
Email Notifications 
. 
