Create Journal Entry activity

An activity that creates a journal entry in Microsoft Outlook.


Create Journal Entry activity

Configure the Create Journal activity

To configure the Create Journal Entry 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 Exchange Server tab.

    Open Exchange Server tab
  3. On the Exchange Server tab, drag the Create Journal Entry activity onto your process.

    Drag Create Journal Entry activity

General Configuration

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

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

Specifies the configuration to create a journal entry.

Figure: Create Journal Entry Configuration screen

Create Journal Entry Configuration screen

Fields

Field NameDefinition

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

Create Add Token icon

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:
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. 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?