Skip to Content

Changes for page Base64 encoding

Last modified by Danniar Firdausy on 2024/09/17 21:22
From version 19.4
edited by Danniar Firdausy
on 2024/09/17 21:22
Change comment: There is no comment for this version
To version 19.2
edited by Danniar Firdausy
on 2024/09/04 13:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,7 +1,6 @@
1 1  {{container}}
2 2  {{container layoutStyle="columns"}}
3 -(((
4 -In many cases, the standard tools in eMagiz are sufficient for manipulating data to meet the needs of external parties. However, there are instances where more complex functionality is required. This microlearning session will guide you through the process of base64 encoding your input messages, which is essential when the receiving party requires encoded data. By the end of this microlearning, you will understand how to implement this feature and when it's most useful, especially when the message is not encoded, but you need to send the data encoded to the external party.
3 +(((Most of the time, you can use the standard tooling of eMagiz to manipulate the data so that it makes sense for the (external) party that receives the data. However, sometimes there are cases in which you need a little bit of extra complexity. This microlearning will explain one of those more complex scenarios. In this microlearning, we will learn how to use base64 encoding on your (input) message. This functionality is beneficial when the message is not encoded, but you need to send the data encoded to the external party.
5 5  
6 6  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7 7  
... ... @@ -12,8 +12,15 @@
12 12  == 2. Key concepts ==
13 13  
14 14  This microlearning centers around base64 encoding.
15 -* With base64 encoding, we mean: turning the string into an encoded string that the external party can handle.
14 +We mean turning the string into an encoded string that the external party can handle.
16 16  
16 +Essential characteristics of this functionality are:
17 +
18 +* Encoding (and decoding) of base64 strings take up additional memory (up to 33%)
19 +* Separate integration for the base64 strings apart from metadata is advisable
20 +* The component in eMagiz needs a base64 encoded string as input
21 +* Multiple times encoding and decoding in the same integration is **not** advisable
22 +
17 17  == 3. Base64 encoding ==
18 18  
19 19  Most of the time, you can use the standard tooling of eMagiz to manipulate the data so that it makes sense for the (external) party that receives the data. However, sometimes there are cases in which you need a little bit of extra complexity. This microlearning will explain one of those more complex scenarios. In this microlearning, we will learn how to use base64 encoding on your (input) message. This functionality is beneficial when the message is not encoded, but you need to send the data encoded to the external party.
... ... @@ -47,10 +47,10 @@
47 47  
48 48  Essential characteristics of this functionality are:
49 49  
50 -* Encoding (and decoding) base64 strings can increase memory usage by up to 33%. Plan your integrations accordingly to avoid performance issues.
51 -* It's advisable to keep base64 strings and metadata in separate integrations to prevent potential complications.
52 -* The eMagiz component used for this process requires a base64 decoded string as input.
53 -* Encoding and decoding multiple times in the same integration is **not** advisable.
56 +* Encoding (and decoding) of base64 strings take up additional memory (up to 33%)
57 +* Separate integration for the base64 strings apart from metadata is advisable
58 +* The component in eMagiz needs a base64 encoded string as input
59 +* Multiple times encoding and decoding in the same integration is **not** advisable
54 54  
55 55  == 5. Suggested Additional Readings ==
56 56