Event Log Development¶

This document addresses technical aspects of the new Event Log and its role in tracking IFS Cloud application transactions. Its primary purpose is to serve as a generic log, capturing a predefined range of entities and events. The specific relationships between events and entities can be found in the Event Entity Configurations in application, those are set with Application Defined in Definition.

Additionally, it is possible to define Custom Defined events and establish personalized event-entity relationships, allowing to create log entries manually or via configuration of IFS Workflows.

event entity configuration

Contents¶

Visualization of Event Log¶

Event Log functions an Object Connection service, making it simple to activate within the attachment panel via Object Connections. The Service Name is EventLog. For comprehensive instructions on configuring the Event Log, refer to the functional end-user documentation located in IFS Business Models /Customer Relationship Management/ Event Generation.

Note:

Since Event Log automatically records user interactions in the application, the count of the events are excluded from the attachment count. However, a future enhancement is planned to give users the flexibility to include or exclude the events from the count according to their choice.

Object Connection Transformation (OCT) for Event Log¶

Given that the Event Log serves as an Object Connection Service, it's possible to establish Object Connection Transformation (OCT) rules for enhanced visualization. For an in-depth understanding and comprehensive background about OCT, refer the functional end-user documentation located in IFS Cloud / Define System Basic / Object Connection Transformations. For example rules, populate the contents of the Object Connection Transformation screen. If you need to write a custom transformation method (with PL/SQL code) you can look at the source code of any of the existing rules that has an API and a method name in the Transformation Method field.

Limitation :

Due to the inherent design of the Event Log, it exclusively supports OCT rules with the Editable property configured as Target only. Other Editable properties, namely Source and None are not supported.