![]() ![]() This condition loops through the collected messages while the process instance is running and checks if every new message that arrives has not been collected already before adding new message to the collection.Ĭondition to loop through collected messages to prevent collecting duplicated messages The condition is specified as below using the “non-equality” logic in combination with “If-then-else” statement. Create a mapping: This mapping step helps to introduce an additional condition to prevent adding duplicated messages to the already collected messages while the process instance is still running for the 5 minutes time duration. If the condition on the IME is not fulfilled, the process server starts a new process instance.Ĭondition: string-equal(incomingString,locallyStoredStringInDO)ģ. All messages that match the stored “Functional location value” are collected and appended to the Data Object which is a list of value. Configure Intermediate Message Event: Configure the intermediate message event with a condition, this condition is defined dynamically, by comparing the incoming value in a specific field and a locally stored field in the Data Object (DO) while the process instance is running. Create a BPM process development component in NWDS with below example (detailed steps on this will not be provided, other blogs have addressed this already)Ģ.This will also check that messages collected are not also duplicated, in case duplicated messages are coming from the same functional within the 5mins duration. During the 5mins duration, collect pattern with an intermediate message event (IME) has to be implemented to collect messages belonging to the same functional location. The situation is such that for every process instance started, there is an intermediate timer event (ITE) of 5mins which keeps the process instance running for this duration. Note: Since it is only possible to define conditions on Intermediate Message Event by comparing two fields based on “equality (=)” the “non-equal part to collect messages that have not been duplicated was achieved by introducing the extra mapping steps to append new non-duplicated messagesĬhallenge: Business requirement is such that message duplication and clustering of messages towards C4C application needs to be achieved. ![]() This article shares some insight on how best to make use of intermediate message event with dynamic conditions in combination with a mapping object. ![]() However, the business requirements could pose an integration challenge that requires thorough knowledge of SAP BPM implementation when using intermediate message even. Collection pattern could make use of time duration for message aggregation or time duration in combination with conditions. There exists different ways to achieve the aggregation pattern using the intermediate message event. Introduction: Message collect pattern provides a way to aggregate messages based on functional requirements or system performance. Condition-based Collect Message Pattern with Intermediate Message Event in SAP BPM ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |