Notify Connector

The Notify connector sends simple notification emails to the recipients defined on the application Alerts page.

Key Capabilities

Simple email notification system using application-wide alert settings
Configurable subject lines and message bodies with macro and ArcScript support
Automatic email sending to predefined recipients from the Alerts configuration
Support for file attachments and both synchronous and asynchronous delivery

Connector Configuration

This section contains all of the configurable connector properties.

Settings Tab

Configuration

Settings related to the core configuration of the connector.

Setting	Description
Connector Id	The static, unique identifier for the connector.
Connector Type	Displays the connector name and a description of what it does.
Connector Description	An optional field to provide a free-form description of the connector and its role in the flow.
Subject	The subject line of the outgoing email message.
Message	The body of the outgoing email message. ArcScript is supported, as are the following macros: %MessageId%, %ConnectorID%, %Filename%, %FilenameNoExt%, %EXT%, %ShortDate%, %LongDate%, %RegexFilename:[regex]%, %DateFormat:[format]%, %Header:[headerName]%

If you have not already specified notification settings on the Alerts page, click Configure Notification Settings to set them up.

Advanced Tab

Setting	Description
Processing Delay	The amount of time (in seconds) by which the processing of files placed in the Transactions tab is delayed. This is a legacy setting. Best practice is to use a File connector to manage local file systems instead of this setting.

Logging

Settings that govern the creation and storage of logs.

Setting	Description
Log Level	The verbosity of logs generated by the connector. When you request support, set this to Debug.
Log Subfolder Scheme	Instructs the connector to group files in the Logs folder according to the selected interval. The Weekly option (which is the default) instructs the connector to create a new subfolder each week and store all logs for the week in that folder. Leaving this setting blank tells the connector to save all logs directly in the Logs folder. For connectors that process many transactions, using subfolders helps keep logs organized and improves performance.
Log Messages	Check this to have the log entry for a processed file include a copy of the file itself. If you disable this, you might not be able to download a copy of the file from the Transactions tab.

Other Settings

Setting	Description
Processing Delay	The amount of time (in seconds) by which the processing of files placed in the Transactions tab is delayed. This is a legacy setting. Best practice is to use a File connector to manage local file systems instead of this setting.

Miscellaneous

Miscellaneous settings are for specific use cases.

Setting	Description
Other Settings	Enables you to configure hidden connector settings in a semicolon-separated list (for example, `setting1=value1;setting2=value2`). Normal connector use cases and functionality should not require the use of these settings.

Automation Tab

Automation Settings

Settings related to the automatic processing of files by the connector.

Setting	Description
Send	Whether messages arriving at the connector are automatically processed.

Performance

Settings related to the allocation of resources to the connector.

Setting	Description
Max Workers	The maximum number of worker threads consumed from the threadpool to process files on this connector. If set, this overrides the default setting on the Performance Settings portion of the Advanced Settings page.
Max Files	The maximum number of files sent by each thread assigned to the connector. If set, this overrides the default setting on the Performance Settings portion of the Advanced Settings page.

Alerts Tab

SLAs Tab

Notify Operations

In addition to the Operations provided with Arc, connectors can provide operations that extend functionality into ArcScript. These connector operations can be called just like any other ArcScript operation, except for two details:

They must be called through the connector.rsc endpoint.
They must include an auth token.

For example, calling a connector operation using both of these rules might look something like this:

<arc:set attr="in.myInput" value="myvalue" />
<arc:call op="connector.rsc/opName" authtoken="admin:1j9P8v8b9K0x6g5R5t7k" in="in" out="out">
  <!-- handle output from the op here -->
</arc:call>

The operation specific to the functionality of the Notify connector is listed below.

notifySendEmail

Sends email notifications.

Required Parameters

Message: The message to send.

Optional Parameters

To: A comma separated list of addresses for destinations.
Subject: The message subject.
Attachment#: File(s) to attach to the message.
Async: Send asynchronously. The allowed values are true or false. The default value is true.

Getting Started

Flows

EDI Trading Partner Management Console

Connectors

Mapping

APIs and Automation

How-To Guides

Scripting

Software License and Third-Party Copyrights

Key Capabilities

Connector Configuration

Settings Tab

Configuration

Advanced Tab

Logging

Other Settings

Miscellaneous

Automation Tab

Automation Settings

Performance

Alerts Tab

SLAs Tab

Notify Operations

notifySendEmail

Required Parameters

Optional Parameters

​Key Capabilities

​Connector Configuration

​Settings Tab

​Configuration

​Advanced Tab

​Logging

​Other Settings

​Miscellaneous

​Automation Tab

​Automation Settings

​Performance

​Alerts Tab

​SLAs Tab

​Notify Operations

​notifySendEmail

​Required Parameters

​Optional Parameters

Key Capabilities

Connector Configuration

Settings Tab

Configuration

Advanced Tab

Logging

Other Settings

Miscellaneous

Automation Tab

Automation Settings

Performance

Alerts Tab

SLAs Tab

Notify Operations

notifySendEmail

Required Parameters

Optional Parameters