Create Community activity

An activity that creates a community in your Viva Engage network.


Create Group activity

Configure the Create Community activity

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

Good to Know

How to Start

  1. Open Process Builder.

    For information about how to open this screen, refer to Process Builder.


    Open Process Builder
  2. In Process Builder, in the Activity Library open the Viva Engage tab.

    Open Yammer
  3. On the Viva Engage tab, drag the Create Community activity onto your process.

    Drag Create Group

General Configuration

Specifies the basic settings for the Create Community activity.

Figure: General Configuration screen

General Configuration screen

Good to Know

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

Fields

Field NameDefinition

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

Create Community Configuration

Specifies the community to create in your Viva Engage network.

Figure: Create Community Configuration screen

Create Group Configuration screen

Fields

Field NameDefinition

Viva Engage

Description:
Specifies the access token that connects to Viva Engage.
Allowed Values:
A list of access tokens configured for your environment.
Default Value:
None
Accepts Variables:
No

Create Add Token icon

Opens this Screen:
Access Token for Viva Engage
Function of this Screen:
Configure an access token to connect to Viva Engage.

Community Name

Description:
Specifies the name of your Viva Engage community.
Allowed Values:
One line of text (a string).

Accepted:

  • Letters
  • Numbers
  • Spaces
Default Value:
None
Accepts Variables:
Yes
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?

Community Description

Description:
An optional description of the community.

Set To Private

Description:
Specifies who can see and add posts, comments, and files.
Allowed Values:
  • Selected - Anyone can work with add posts, comments, and files.
  • Deselected - Only group members can work with posts, comments, and files.
Default Value:
Deselected

Store Community ID in this Variable

Description:
Specifies a process data variable that stores the community ID.
Allowed Values:
A process data variable that accepts an alphanumeric string with no spaces or special characters.
Default Value:
None
Accepts Variables:
Yes
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?