Activity Stream

The LumisXP has an Activity Stream framework that allows the generation of activities and notifies portal users about them.

An activity consists of actor, action, scope, object, and target object.

• Actor is the user who generated the action. Example: User Caio created a content; Caio is the actor of this activity;
• Action is the action that the actor performs on the object. Example: Caio created a content; Created is the action of this activity;
• Scope is a free string aimed at identifying the scope of the activity. Example: Caio changed the workflow state of a content; In this case, the default scope applied by the portal is an administration scope (lum_objectAdmin).
• Object is the object to which the activity is related. Example: Caio created a news "LumisXP on AWS"; In this case, the referred news is the object.
• Target object is the destination object of the activity. Example: Caio added a comment on a content; In this case, the content is the target object and the comment is the object of the activity.

It is possible to register new actions and object types.

It is possible to use the Activity Stream Manager to facilitate access to activities. A document in Big Data is automatically generated for each activity, allowing for consultation through the Big Data framework.

To process new activities, an Activity Processor is used, which can be defined in the channel or in the service instance.

The LumisXP includes a standard processor that has a notifier capable of sending emails to users, prioritizers for content (scope for end users and administrative) and a prioritizer for comments (scope for end users).

The Activity Stream service allows for the visualization of activities by the end user.

More information on customization and development is available in the javadoc.