Composite Events CMS042 - Limit Workflow calls

The documentation for Composite Events is very limited.

Does anyone know if a Composite Event (CMS042) can be used in an Event Based Alert (CMS047), to call a Workflow?

Would like to be able to do this so that I can Filter on Fields from Related Table(s) as well BEFORE calling Workflow to ensure performance, as well as not having to see Workflow History for Workflows that are never processed (not needed based on Criteria).

Or is the option available to use 'Event Analytics' to be able to utilize 'Composite Events'?

Would appreciate if anyone has some insight into this.

Find more posts tagged with

Accepted answers

All comments

Maxime Richard

Hi Rene,

As composite events tags's length is 6, i had to go through EA first after composite event creation. Did built a new event (same name = YourEventFromCMS042, same operation, virtual fields only) with virtual tags to get 4 digits (CMS047).

In CMS047, build your WF call based on subscription : EventAnalytics:YourEventFromCMS042:YourOperation

Last but not the least, happy new year.

Rene Bottern

Hi Maxime,
and thanks for this. I have ended up at the EA as well, and is about to verify this.
Hopefully this will work as expected this way.

Happy New Year to you as well.

mosterberg

.... adding to Rene's question - needing to know if there are any limitations on Composite Event entries - quantity etc. as we are looking to use these more aggressively in a high volume integration environment to limit volume through enhanced filters and to reduce API calls within MEC mappings etc. by including additional data joins within the events. Looking for performance downsides/upsides with composite events utilization and any restrictions in volume of them or complexity of them to be considered.

Rene Bottern

I add some findings myself here for everyone, since this one was a bit tricky to get working as expected.

Ended up needing this to be based on EventAnalytics to ensure I can filter as required.
(You can do this without involving EventAnalytics as well, but I think this misses the reason why Composite Event is necessary)

EventAnalytics:
EventAnalytics listens to CMS042 M3:MWOHED_WC -> publishes EventAnalytics:MWOHED_WC

By linking MWOPE in CMS042 I can now add more Filters in the EventAnalytics process.

Remaining flow as per below:
CMS047 EventAnalytics:MWOHED_WC listens to CMS045 EventAnalytics:MWOHED_WC which listens to EventAnalytics:MWOHED_WC

Hopefully this helps someone.

Copyright © 2025 Infor. All rights reserved.