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 e-mail notification, click Advanced > E-mail Notifications .
For more information, refer to Configure E-mail Notifications for Any Activity.
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?
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?

How to Start

On the Application Explorer screen, do one of these:
- Open a Process.
- Create a Process.
Do one of these:
- Add an activity:
  1. In the Process Builder, in the Activity Library, open the Exchange Server tab.
  2. On the Exchange Server tab, drag the Create Journal Entry activity onto your process.
- Change an activity:
  1. In your process, double-click your activity.

General Configuration

Specifies the basic settings for the Create Journal Entry activity.

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

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:

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 Journal Entry Configuration

Specifies the configuration to create a journal entry.

Fields

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