Important notes

Regarding the data flow, be aware that Activities is an 'engine' inside ION. It is not a normal application for which you can create a connection point. Therefore, the configuration differs from a normal configuration. Normally, a data flow is created from A to B where you select the documents to be sent. This selection can be a subset of the documents sent by connection point A and received by connection point B.

If an application connection point that can publish ProcessPulseAlert, ProcessPulseTask, or ProcessPulseNotification, is used in an active data flow, these BODs are delivered directly to the Activities engine. Similarly, if the connection point is configured to receive SyncPulseAlert, SyncPulseTask, or SyncPulseNotification, it receives those BODs without selecting them in a data flow.

Therefore, you cannot use mapping, content-based routing, or filtering in a data flow for PulseAlert, PulseTask, and PulseNotification.

For details on how to define connection points and data flows, see the Infor ION User Guide.