Hi,

We are currently evaluating implementation options for internal alert creation in our application, specifically for the Bulk Upload and Manual Alert Case Creation use cases using AIM Accelerator.

BulkUpload- A journery where bulk events are uploaded in system manually and create alerts cases for each events for investigation
Manual Alert- A simple user journey to create the alert case manually by user

We have identified two viable approaches and would like to understand which is considered best practice from a platform perspective.

1. ChannelEntryWrapper (Activity): Currently this is the service activity for Rest API to create alerts by calling pega from external system. This can be called from application internally to create the alerts. While it functions correctly, it introduces additional overhead related to response formation, which may not be necessary for internal alert creation scenarios. Also this activity is of type Connect.

2. EventEntry (Activity): This OOTB activity is called internally from ChannelEntryWrapper which can be used to create alerts. It avoids the API response layer introduced by ChannelEntryWrapper. This activity is of type Activity

Request for Guidance:

We would appreciate your input on the following:

1. Which of the above approaches is considered best practice for internal alert creation within the application?

2. Is there any documentation or guidance available that outlines the intended use cases for these components?

We aim to align with platform standards and ensure long-term maintainability.

Please let us know if further details or implementation context are needed.