Skip to Content
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 19.1
edited by Eva Torken
on 2023/12/07 15:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.etorken
Content
... ... @@ -18,8 +18,6 @@
18 18  
19 19  == 3. Communication between models ==
20 20  
21 -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.
22 -
23 23  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.
24 24  
25 25  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.
... ... @@ -36,13 +36,8 @@
36 36  
37 37  Both alternatives have the benefit that the security can be tight and explicit (i.e., only model A can write/post data to model B). Furthermore, managing the solution becomes much easier as it uses the standard functionality within the platform. Therefore, we have no plans to support this approach in the product.
38 38  
39 -== 4. Assignment ==
37 +== 4. Key takeaways ==
40 40  
41 -Consider what your criteria are when communicating between models and compare them to our criteria.
42 -This assignment can be completed with the help of the (Academy) project you created/used in the previous assignment.
43 -
44 -== 5. Key takeaways ==
45 -
46 46  * Consider the following when communication between two models
47 47  ** Security
48 48  ** Loose coupling
... ... @@ -49,10 +49,8 @@
49 49  ** Maintainability
50 50  ** Clarity
51 51  
52 -== 6. Suggested Additional Readings ==
45 +== 5. Suggested Additional Readings ==
53 53  
54 54  If you are interested in this topic and want more information, please consult us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]]
55 55  
56 -== 7. Silent demonstration video ==
57 -
58 -As this is more of theoretical microlearning, there is no video accompanying the microlearning.)))((({{toc/}}))){{/container}}{{/container}}
49 +)))((({{toc/}}))){{/container}}{{/container}}