• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 10 subscribers
  • Views 806 views
  • Users 0 members are here
Related Discussions
Home » Discussions » General

Multiple Messages to One Receive Message Event

anak3061
Certified Associate Developer

Hi,

is it possible to receive multiple messages on one Receive Message Event?

I need to use Receive Message Event to stop the process flow until all the fields of multiple entities are populated, so I have a Send Message Event on each asynch subprocess that sends a message to my main one that the fields have been populated. There is also an Expression Condition on Receive Message Event that checks if all entities have populated values. If it's possible to receive multiple messages, does the condition get validated each time it receives a message?

Thanks!

  Discussion posts and replies are publicly visible

Parents
  • 0
    Appian Employee
    1. Yes, a Receive Message node (a "listener") can either be exercised once and once only, or for the life of the process instance
    2. Yes, each time a Receive Message is triggered and steps in the flow from that event will be executed again.

    I'd issue a warning here that this is not a scalable option and there may well be a better pattern. For instance, instead of sending/receiving messages your process instance could run on a repeating timer and retrieve the data from the entities you mention and run validation on the data retrieved to determine if your data in complete and valid.

    Alternatively, every time an entity is updated you could call a sub-process that also runs the data retrieval/validation to achieve the same outcome.

Reply
  • 0
    Appian Employee
    1. Yes, a Receive Message node (a "listener") can either be exercised once and once only, or for the life of the process instance
    2. Yes, each time a Receive Message is triggered and steps in the flow from that event will be executed again.

    I'd issue a warning here that this is not a scalable option and there may well be a better pattern. For instance, instead of sending/receiving messages your process instance could run on a repeating timer and retrieve the data from the entities you mention and run validation on the data retrieved to determine if your data in complete and valid.

    Alternatively, every time an entity is updated you could call a sub-process that also runs the data retrieval/validation to achieve the same outcome.

Children
No Data

© 2024 Appian. All rights reserved.