Changes for page Groovy Script

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -23,30 +23,30 @@
23	23
24	24	=== 3.1 Implementation in Create ===
25	25
26		-To implement a groovy script in Create you first need to consider what your Groovy script should do. Within the flow designer there are five components available that can handle a Groovy script.
	26	+To implement a groovy script in Create, you first need to consider what your Groovy script should do. Then, within the flow designer, there are five components available that can handle a Groovy script.
27	27
28		-* In case you want the Groovy script to filter out messages you should implement the Groovy script in a "standard filter" component.
29		-* If you want your Groovy script to always transform your message from a certain format into another format you should consider using a "standard transformer" component.
30		-* In case you need an optional output the "standard service activator" is your friend. So for example, when you want to do some transformation and do a check whether a message can continue you can use the "standard service activator" and have an optional output.
31		-* When you want to split your message based on a Groovy script you should use the "standard splitter"
32		-* If you want to route messsages based on a Groovy script you should use the "standard router"
	28	+* In case you want the Groovy script to filter out messages, you should implement the Groovy script in a "standard filter" component.
	29	+* If you want your Groovy script to always transform your message from a certain format into another format, you should consider using a "standard transformer" component.
	30	+* The "standard service activator" is your friend if you need an optional output. So, for example, when you want to do some transformation and check whether a message can continue, you can use the "standard service activator" and have an optional output.
	31	+* When you want to split your message based on a Groovy script, you should use the "standard splitter."
	32	+* If you want to route messages based on a Groovy script, you should use the "standard router."
33	33
34		-{{warning}}Note, that in practice we mainly see use cases for the "standard service activator" and the "standard transformation".{{/warning}}
	34	+{{warning}}Note that in practice, we mainly see use cases for the "standard service activator" and the "standard transformation." {{/warning}}
35	35
36	36	[[image:Main.Images.Microlearning.WebHome@expert-data-handling-groovy-script-available-components.png]]
37	37
38		-Regardless of the component you choose you always need to select the option called "Groovy script" and reference the Groovy resource available on flow level that you want to use within the component.
	38	+Regardless of the component you choose, you always need to select the "Groovy script" option and reference the Groovy resource available on the flow level you want to use within the component.
39	39
40	40	[[image:Main.Images.Microlearning.WebHome@expert-data-handling-groovy-script-groovy-configuration.png]]
41	41
42		-{{info}}As you can see in the help text when selecting the "resource" attribute you need to make sure that the Groovy script is uploaded within the context of your flow.{{/info}}
	42	+{{info}}As you can see in the help text when selecting the "resource" attribute, you need to make sure that the Groovy script is uploaded within the context of your flow.{{/info}}
43	43
44		-After you have the component in such a way that the correct Groovy script is called you are done with the configuration of the component and can test the flow using flow testing.
	44	+After you have the component in such a way that the correct Groovy script is called, you are done with the component's configuration and can test the flow using flow testing.
45	45
46	46	=== 3.2 Key considerations ===
47	47
48		-* To make some groovy scripts work you need to upload (third-party) Java libraries that are not packaged on default by eMagiz
49		-* To make some groovy scripts work you need to reference Java libraries via a standard header enricher or as a dummy variable
	48	+* To make some groovy scripts work, you need to upload (third-party) Java libraries that are not packaged on default by eMagiz
	49	+* To make some groovy scripts work, you need to reference Java libraries via a standard header enricher or as a dummy variable
50	50	* The store consists of several groovy scripts that might be of use to you
51	51	* Groovy scripts should be viewed as an extension that can be used in fringe cases, not as a standard best practice
52	52	* When a groovy script becomes so complex that you are programming, you should consider alternatives to the solution
...	...	@@ -57,12 +57,12 @@
57	57	== 4. Assignment ==
58	58
59	59	Try to implement a component that references a Groovy script and see whether the flow can be tested.
60		-This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
	60	+This assignment can be completed with the help of the (Academy) project you created/used in the previous assignment.
61	61
62	62	== 5. Key takeaways ==
63	63
64		-* To make some groovy scripts work you need to upload (third-party) Java libraries that are not packaged on default by eMagiz
65		-* To make some groovy scripts work you need to reference Java libraries via a standard header enricher or as a dummy variable
	64	+* To make some groovy scripts work, you need to upload (third-party) Java libraries that are not packaged on default by eMagiz
	65	+* To make some groovy scripts work, you need to reference Java libraries via a standard header enricher or as a dummy variable
66	66	* The store consists of several groovy scripts that might be of use to you
67	67	* Groovy scripts should be viewed as an extension that can be used in fringe cases, not as a standard best practice
68	68	* When a groovy script becomes so complex that you are programming, you should consider alternatives to the solution