The following How to cover the real-time processing for the Price List. We want to store PL information in the Data Source in real-time. The old solution was, that we have several Dataloads runs every 10 mins which checks if there is some updated PL from the last run in special status APPROVED/REVOKED/SUPERSEDED. Based on it we process some data loads and updates in DS. But it is not effective, we wanted to have real-time solution. This article will show all the steps that need to be done.

Platform Manager - Event allowance setup

1. You need to have privileges to be able to admin the events.

2. In the PM Account → Partitions → Partition Overview → Event Admin

3. Click to button Event Configurator

   Open

   

    

4. Choose what events you would like to catch and process

   Open

   

    

5. Leave Event to Kafka/MQ = PROD (it is the setting for the dev/qa/prod the same) , you will specify later how and where the events will be matched and processed

6. Event URL = localhost

7. Ensure that events are generated and visible in the Event list. To be able manage PL we set events fro the ITEM_APPROVED_PL and ITEM_PL_REVOKE.

    

8. If events are generated and visible you can continue with the following steps. If you can’t see the events in the list contact support and ask for help.

    

Partition - Groovy Logic

The biggest problem for us was the situation when we were able to react to the event, but if we wanted to process it by Data Load (requirement), the DL was blind and the logic didn’t know what PL was approved. We were able to read inputs in Generic Logic, but we were not able to run the Data Load (it is not allowed to use actionBuilder). We would like to use CF logic, but it was not possible to join with the event. Many show-stoppers… Therefore several Jira tickets were created to have better options how to process events and the most common case - process them via Data Load which knows the object ID.

Solution

We created a Generic Logic, which was able to read the event parameters and used boundcall to input rows to the Data Source.

The event parameters from ITEM_APPROVED_PL that is processed is:

The generic logic can read the event parameters in the element PriceListId from the data input.

then we simply prepare data for the Data Source insert:

This solution covers the case of what we need. React in real-time on the event when Price List is approved or revoked (we don’t need to have an post-approval step and batch runs every 10 mins to check if some PL was updated and what is the status of that PLs).

The current list of the events is here: Events

Platform Manager - event setting and connect to the logic

When the partition generates the proper events and you have a logic ready to process the triggered event you just need to do the final setting.

1. You need to have privilege to set Event Workflow - ask support for that or ask for admin :)

2. If you have access, press the button “Create Event Workflow”

   1. Enable it

   2. Fill Name and Description

   3. Execution order - if you have one Event catch then keep it empty. If you have more, you can setup the order here.

   4. Then add Listener

3. Listener - General

   1. Choose the name - It is fine to keep the event name or something self descripted

   2. Description

   3. Timeout

4. Listener - Source

   1. Add the Source Event - don’t combine more events in one listener if not necessary. You can have some more complex setting, but this is not stable and can happened that some events will be missed, because the catcher will wait for several events and tries to combine them, etc… So keep it simple. Create separate Event Workflow for each event you want to process, don’t combine events in one Workflow if you don’t have very good reason for it.

   2. Select the Source Type = PARTITION - you want to catch events on the partitions

   3. Select the Source Name = <your partition>. Remember the Event to Kafka/MQ = PROD in the initial setting? Here is the partition differentiator, so don’t be confused, that originally you set PROD

   4. Then choose what event you want to catch - ITEM_APPROVED_PL in this case

       

5. Listener - Action

   1. Here you set on which partition the event will be processed. Honestly I didn’t try to trigger event in DEV and process it in QA But it seems as the theoretical option here. Anyway, my solution was ALL in ONE partition

   2. Select Target Type = PARTITION

   3. Target Name = <your partition>

   4. Action Type - here you can choose what logic will process the event. As mentioned in the beginning with the limitation of the logic types. Our solution uses Generic Ligic = LOGIC

   5. Action ID - the name of the logic

       

And that’s it. As recommended, create Event Workflow for each event, don’t combine them in the one workflow (when we did it, we have a problem with the loosing of the events and they were not processed, because the setting causes some waiting and mutual dependency, etc…)

So if we want to catch PL approval and revoke we have two Event workflows defined:

Then test the event. Trigger the event, check if the Last Run was updated, it means the event was catched and processed. And hopefully you will also have the final required result in the DS.