Changes for page Most Used - SpEL
Last modified by Erik Bakker on 2024/07/02 14:55
From version 10.1
edited by Erik Bakker
on 2022/05/02 09:37
on 2022/05/02 09:37
Change comment:
There is no comment for this version
To version 23.1
edited by Erik Bakker
on 2024/07/02 14:55
on 2024/07/02 14:55
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - eMagiz DataSink1 +Most Used - SpEL - Content
-
... ... @@ -2,35 +2,28 @@ 2 2 {{container layoutStyle="columns"}} 3 3 ((( 4 4 == About == 5 - With thehelpof thisfunctionality,youcansinkyour messagesinto theeMagiz data sink bucket.Once themessage isstoredinthe eMagiz data sinkbucket,youwillhavetheoption toviewthis messagein the Managephase.5 +This store item houses examples of SpEL expressions used within eMagiz models. Use it as inspiration when you need a SpEL expression to execute a certain task within your flow. 6 6 7 7 == Documentation == 8 8 9 9 ==== 1. How to use==== 10 - Oncestored,eMagiz can retrieve allmessageswith thesameIDattachedduringthesink actionvia thenagephase.In thiscase,itisassumedthat youreMagiz data sinkis suchthatyoucan reviewthemonthefly.OthereMagizdatainkvariants are offered thatrequiredspecificon-demand queries.10 +This store item houses examples of SpEL expressions used within eMagiz models. Use it as inspiration when you need a SpEL expression to execute a certain task within your flow. 11 11 12 12 ==== 2. Keynotes & restrictions==== 13 13 14 -* Note that you should think about when you want to archive your data to the eMagiz data sink. That choice determines what the impact on the functional flow is. 15 -* Don't use a wiretap to invoke this part of the flow, as that causes the sink's behavior to happen before the actual processing. If the sink fails, the message will not be delivered via the functional part of the flow. 16 -* Note that we define (among others) how the message is stored in the data sink bucket in this component. The file structure expression should not be altered, as changing this would break the functionality. 17 -* Note that the 'standard' eMagiz headers to define the source system (i.e. relevant systems) and the messageType need to be available upon sinking to make this functionality work. 14 +* Note that this is an example of using the SpEL expression within eMagiz. 15 +* The name of each header identifies the function of the SpEL expression. 16 +* Note that you need to determine how to best utilize the SpEL expression within the context of your flow to make it work in your use case. This store item is focused on inspiring you instead of providing an out-of-the-box solution. 18 18 19 19 ==== 3. License Information==== 20 - To use this store itemyouneedto secureanadditionallicenseon the eMagiz platform.Ifyouareinterestedinsucha licensepleasecontactusatproductmanagement@emagiz.com.19 +Part of the standard license agreement as agreed upon when using the store for the first time. 21 21 22 22 ==== 4. Relevant eMagiz Academy Microlearnings==== 23 23 24 -[[ https:~~/~~/emagiz.github.io/docs/microlearning/advanced-data-management-data-sink>>url:https://emagiz.github.io/docs/microlearning/advanced-data-management-data-sink]]23 +* [[SPEL Expressions>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Data Handling.advanced-data-handling-spel-expressions||target="blank"]] 25 25 26 -Would you please consult the privacy policy of eMagiz at the following link : [[https:~~/~~/www.emagiz.com/privacy-policy/?>>url:https://www.emagiz.com/privacy-policy/?]])))25 +//Would you please consult the privacy policy of eMagiz at the following [[link>>https://www.emagiz.com/privacy-policy/||target="blank"]]))) 27 27 28 - 29 - 30 -((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %) 31 -|=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option 32 -|(% style="width:45px" %) a|(% style="width:241px" %) XML message(s) 33 -|(% style="width:45px" %) b|(% style="width:241px" %) JSON Message(s) 34 -))) 27 +((())) 35 35 {{/container}} 36 36 {{/container}}