Changes for page Communication between models

Last modified by Erik Bakker on 2024/09/05 14:00

From version 17.1

edited by Erik Bakker
on 2022/07/28 10:54

Change comment: There is no comment for this version

To version 18.1

edited by Erik Bakker
on 2023/04/13 14:16

Change comment: There is no comment for this version

Summary

Page properties

Content

@@ -18,8 +18,6 @@
  == 3. Communication between models ==
--In a low-code platform like eMagiz, you want to prevent using custom scripting as much as possible. However, sometimes in practice, you encounter situations that cannot be realized with the standard toolbox provided within the platform. As a result, we offer the option to use a Groovy script in these situations to achieve the desired solution. In this microlearning, we will look at where you can use a Groovy script and discuss the key considerations when implementing a Groovy script within your model.
--
  Most users would think that communication via queues to connect two separate eMagiz models is a bright idea. However, this is something that we do not encourage. We discourage this for several practical and technical reasons alike.
  When looking at the practical side of things getting it configured correctly is time-consuming and an error-prone action (as is evident by the question). Furthermore, it can lead to unexpected situations where you make a typo to listen to a queue on which no messages are provided. This queue will, however, be registered on the JMS level (when you activate the flow in question with the custom configuration), which can lead to confusing queue statistics and even more troublesome false-positive alerting based on missing queue metrics or missing consumers.