Create User (Office 365) activity

An activity that creates a user in Office 365.


Create User activity

Configure the Create User activity

To configure the Create User activity, do the procedure in this topic.

Good to Know

How to Start

  1. On the Application Explorer screen, do one of these:
  2. Do one of these:
    • Add an activity:
      1. In the Process Builder, in the Activity Library, open the Office 365 Administration Office 365 Administration icon tab.
      2. On the Office 365 Administration Office 365 Administration icon tab, drag the Create User Create User icon activity onto your process.
    • Change an activity:
      1. In your process, double-click your activity.

General Configuration

Specifies the basic settings for the Create User activity.

Figure: General Configuration screen

General Configuration screen

Fields

Field Name Definition

Display Name
Function:
Specifies the activity name that shows in your process.
Accepted Values:
One line of text that can have spaces.
Default Value:
None
Accepts Process Data 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
Function:
Specifies an optional text description for your activity.
Accepted Values:
More than one line of text.
Default Value:
None
Accepts Process Data Variables:
No

Create User Configuration > Basic tab

Specifies the basic information to create a user in Office 365.

Figure: Create User Configuration > Basic tab

Create User Configuration Basic tab
Figure: Create User Configuration > Contact tab

Create User Configuration Contact tab

Fields

Field Name Definition

Office 365 Administration
Function:
Specifies the access token that connects to your Office 365.
Accepted Values:
A list of access tokens configured for your environment.
Default Value:
None
Accepts Process Data Variables:
No

Add Token Add Token icon
Opens this Screen:
Access Token for Office 365
Function of this Screen:
Configure an access token to connect to Office 365.

User Name
Function:
Specifies the name of the user to create in Office 365.
Accepted Values:
Default Value:
None
Accepts Process Data Variables:
Yes

User Information Fields
Function:
Fields on the Basic and Contact tabs store information about the Office 365 user. You can complete these fields with text or variables.

Create User Configuration > Response Variable

Specifies the variable that stores the temporary password for the new user in Office 365.

Figure: Create User Configuration > Response Variables tab

Create User Configuration Response Variables tab

Fields

Field Name Definition

Office 365 Administration
Function:
Specifies the access token that connects to your Office 365.
Accepted Values:
A list of access tokens configured for your environment.
Default Value:
None
Accepts Process Data Variables:
No

Add Token Add Token icon
Opens this Screen:
Access Token for Office 365
Function of this Screen:
Configure an access token to connect to Office 365.

User Name
Function:
Specifies the name of the user to create in Office 365.
Accepted Values:
Default Value:
None
Accepts Process Data Variables:
Yes

Store the Response Password in Process Attribute
Function:
Specifies a process data variable that stores the Office 365 temporary password.
Accepted Values:
A process data variable that accepts an alphanumeric string that can have special characters.
Default Value:
None
Accepts Process Data Variables:
Yes
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses 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, and 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?