16.3 - Sending Message Events to Process Models

A Score Level 1
The release notes for Appian 16.3 contains the following (forum.appian.com/.../Appian_Release_Notes.html

Sending Message Events to Process Models
We've deprecated the ability to send messages to process models from the Setup tab in the Send Message Event smart service. Sending message events to process models this way has negative performance impacts.

Use the Start Process Smart Service instead.

The last part implies this is only for start message events, but the body implies it applies to all message events, including intermediate message events. Would someone be able to clarify exactly what is being deprecated? Removing the ability to message process models (and therefore in-flight instances) altogether would be a serious loss of functionality and would place Appian behind its competitors as fa...

OriginalPostID-238470

  Discussion posts and replies are publicly visible

Parents
  • @stefan Again, that's fine but it assumes nobody has any processes that use that functionality - I'm not sure we can assume that nobody uses the functionality without knowing everything everyone has ever done, which of course we don't know! It seems a little short-sighted to just suddenly deprecate this functionality.

    @mschmitt It can result in performance issues, presumably if there are many instances of a specific model (as described here - https://forum.appian.com/suite/help/16.3/Messaging_Best_Practices.html). However, it is often useful to message a process model and "correlate" on a piece of business data rather than the alternative, which is to implement a process report to reterieve the process IDs and subsequently message each of them individually. I have seen this implemented in a number of projects, and I'm assuming that those clients don't wish to rewrite what would effectively constitute the core architecture of the solution.
Reply
  • @stefan Again, that's fine but it assumes nobody has any processes that use that functionality - I'm not sure we can assume that nobody uses the functionality without knowing everything everyone has ever done, which of course we don't know! It seems a little short-sighted to just suddenly deprecate this functionality.

    @mschmitt It can result in performance issues, presumably if there are many instances of a specific model (as described here - https://forum.appian.com/suite/help/16.3/Messaging_Best_Practices.html). However, it is often useful to message a process model and "correlate" on a piece of business data rather than the alternative, which is to implement a process report to reterieve the process IDs and subsequently message each of them individually. I have seen this implemented in a number of projects, and I'm assuming that those clients don't wish to rewrite what would effectively constitute the core architecture of the solution.
Children
No Data