Create Journal Entry activity

An activity that creates a journal entry in Microsoft Outlook.

Configure the Create Journal activity

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

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 Exchange Server tab.
On the Exchange Server tab, drag the Create Journal Entry activity onto your process.

General Configuration

Specifies the basic settings for the Create Journal Entry 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

Create Journal Entry Configuration

Specifies the configuration to create a journal entry.

Fields

Field Name	Definition
Exchange Server	Description: Specifies the access token that connects to your Exchange Server. Allowed Values: A list of access tokens configured for your environment. Default Value: None Accepts Variables: No
Create	Opens this Screen: Access Token for Exchange Server Function of this Screen: Configure an access token to connect to Exchange Server.
Journal Entry Subject	Description: Specifies the subject line for your journal entry. Allowed Values: One line of text that can have spaces. A process data variable. You can use App Data screen to specify a process data variable. Default Value: None Accepts Variables: Yes
Start Date	Description: Specifies the start date and time of the journal entry. Allowed Values: A valid date and time. A process data variable. You can use App Data screen to specify a process data variable. Default Value: None Accepts Variables: No
End Date	Description: Specifies end date and time of the journal entry. Allowed Values: A valid date and time. A process data variable. You can use App Data screen to specify a process data variable. Default Value: None Accepts Variables: No
Company Name	Description: Specifies the name of the user's organization. Allowed Values: One line of text that can have spaces. A process data variable Default Value: None Accepts Variables: Yes
Entry Type	Description: Specifies the type of journal entry to record, such as a phone call, task, or meeting request. Allowed Values: One line of text that can have spaces. A process data variable. You can use App Data screen to specify a process data variable. Default Value: None Accepts Variables: Yes
Journal Entry Body	Description: Specifies the body of the journal entry. Allowed Values: More than one line of text. A process data variable. You can use App Data screen to specify a process data variable. Default Value: None Accepts Variables: Yes
Store Journal Entry ID in this Variable	Description: Specifies a process data variable that stores the journal ID from Exchange Server. Allowed Values: A process data variable that accepts an alphanumeric string with no 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?