We have automated a business process in Appian wherein a set of business validation steps are performed by integrating with various systems via web services, data base and robotic process automation (RPA tool).
With respect to RPA, Appian process places a request in RPA's queue requesting for a set of data. RPA tool screen-scrapes a legacy system and responds back to Appian with required data via 5 different web API calls, in any order.
Since the RPA can respond back in any order, the Appian process has five receive-message event listening to five send-messages. These five send-messages are sent via the 5 web APIs which the RPA invokes.
Question is : Does having 5 different receive-message in single process have any implications on Appian memory, performance etc OR are there any cons of having 5 different receive-message in single process ?
Please note that there can be alternative patterns to implement above scenario but would really appreciate if I get responses specific to my question and not suggestions on alternative patterns :)
Discussion posts and replies are publicly visible
Does having 5 different receive-message in single process have any implications on Appian memory, performance etc OR are there any cons of having 5 different receive-message in single process ?
You can also use a single receive message node and then based on designed event conditions either on the request payload or message properties being received, trigger the respective processes.
https://docs.appian.com/suite/help/17.1/Receive_Message_Event.html#setup-tab
Ideally we should be using a singe receive message node to receive different requests.
just to add, Does your Appian receiver process get completed after receiving the messages & triggering the further flows or it's a long running process.
As, receive message events do listen for the lifetime of the process based on the checkbox selection and process completion.
"You can configure the event to continue listening for messages until the process completes by selecting the Activate Message Event checkbox (which displays the inline explanation: Once activated, listen for messages for the life of the process)."
Abhinav has missed the point You can configure the event to continue listening for messages until the process completes by selecting the Activate Message Event checkbox (which displays the inline explanation: Once activated, listen for messages for the life of the process).
When this checkbox is cleared, the event no longer listens for messages that could cause the event to execute again, once a message is received.
"For optimal performance, keep this option cleared."
Did you enable the checkbox?