Activities application architecture

The Activities engine part on the server side runs as engine in the ION Service container. The Activities engine is accessed by the Event Management and Workflow engines and pushes tasks and alerts through secured web-service calls. Other Infor applications can also send PulseAlert, PulseTask, and PulseNotification messages directly to the Activities engine.

For details, see the Infor ION Development Guide.

The Activities UI acts as a client application for the Activities engine and displays the activities and workflow information relevant to each user.

tr_scheme_ion_activities_component_diagram.png

When a new alert or task is created, it is visible for all users from the distribution list of this alert and task. If the distribution list contains group names, all users that are part of this group receive a notification when the task or alert is created.

Tasks and alerts are shown in these locations:

  • The Alert List or Task List widgets from the Infor Ming.le homepages and the Infor Inbox application in Infor Ming.le of the user to which the task or alert is assigned.
  • If the activity is not assigned to a user: the Alert List or Task List widgets from the Infor Ming.le homepages and the Infor Inbox application of all users who are in the distribution list of the task or alert.
  • The Activities and Archived Activities pages in ION Desk.