CMEF Message Payload Using the Content Management Event Framework

Using the Content Management Event Framework 16-15 if message.action = UPDATE_PAGE_GROUP_ACL and message.object_class = PAGE_GROUP and message.raw.event = wwsbr_event_q_access.EVENT_UPDATE then . . . end if; However, if you are more interested in filtering for actual update and delete events on the page groups ACL, then your subscriber should perform the following checks: if message.object_class = PAGE_GROUP and message.raw_event = wwsbr_event_q_access.EVENT_UPDATE then if message.action = ADD_PAGE_GROUP_ACL then . . . end if; if message.action = DELETE_PAGE_GROUP_ACL then . . . end if; . . . end if;

16.3.7.1.4 Deleting a Page Deleting a page produces the following message payload:

16.3.7.2 Item Actions

Items are one of the basic components of a portal page. Items in a portal are based on item types. An action on an item triggers a CMEF event irrespective of the item type. For example, an ADD_ITEM action occurs whenever a user adds an item of a base, extended, or custom item type. This ensures that there is consistent CMEF messaging behavior when an item action occurs.

16.3.7.2.1 Creating an Item and Publishing it at the Same Time If a user has Manage

privileges, creating an item of any type on a page produces the following message payload: If you want you subscriber to respond to this action, perform the following check: if message.action = ADD_ITEM and message.object_class = ITEM and Note: The ADD_PAGE_GROUP_ACL and DELETE_PAGE_ GROUP_ACL events are triggered when the user clicks Add for each user that is added todeleted from the ACL. The UPDATE_PAGE_ GROUP_ACL is generated when the user clicks Apply or OK. Action Event State Object Class DELETE_PAGE DELETE PURGED PAGE Note: Events are not generated for the sub-pages or items that are on the page. Action Event State Object Class ADD_ITEM INSERT PUBLISHED ITEM 16-16 Oracle Fusion Middleware Developers Guide for Oracle Portal message.raw_event = INSERT and message.state = PUBLISHED then . . . end if;

16.3.7.2.2 Adding an Item That Requires Approval If approvals and notifications are

enabled for a page or page group, and a user with Manage Items With Approval privileges, adding an item to a page produces the following message payload: If you want your subscriber to respond to this action, perform the following check: if message.action = SUBMIT_ITEM_FOR_APPROVAL and message.object_class = ITEM and message.raw_event = INSERT and message.state = NOT_PUBLISHED then . . . end if;

16.3.7.2.3 Approving an Item Approving an item triggers either an INSERT or UPDATE

event, which may also be followed by either a DELETE or UPDATE event depending upon whether or not versioning is enabled. Item approved; versioning disabled This is the simplest case. If the item still has approval steps to pass through, then an UPDATE event is triggered: If the item has completed all approval steps, then an INSERT event is triggered: Item approved; versioning enabled; current version overwritten If item versioning is set to Simple at the page or page group level, and a user selects Overwrite Current Version when editing an item, on approval of the item, two events are generated. The first event is for the item that is approved, and a second DELETE event for the item that is overwritten as a result of the item being approved: Action Event State Object Class SUBMIT_ITEM_FOR_ APPROVAL INSERT NOT_PUBLISHED ITEM Action Event State Object Class APPROVE_ITEM_ STEP UPDATE GENERAL ITEM Action Event State Object Class APPROVE_ITEM INSERT PUBLISHED ITEM Action Event State Object Class APPROVE_ITEM INSERT PUBLISHED ITEM APPROVE_ITEM DELETE PURGED ITEM