Skip to Content

Changes for page Base64 decoding

Last modified by Danniar Firdausy on 2024/09/17 21:20
From version 16.7
edited by Danniar Firdausy
on 2024/09/17 21:15
Change comment: There is no comment for this version
To version 16.6
edited by Danniar Firdausy
on 2024/09/04 16:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,8 +1,9 @@
1 1  {{container}}
2 2  {{container layoutStyle="columns"}}
3 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 focuses on one such scenario, that is, to use base64 decoding for handling base64 encoded messages. By the end of this microlearning, you will understand how to implement this feature and when it's most useful, especially when working with encoded data that needs further manipulation.
5 5  
5 +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 decoding on your (input) message. This functionality is beneficial when the message is encoded, but you need to manipulate part of the data.
6 +
6 6  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7 7  
8 8  == 1. Prerequisites ==
... ... @@ -12,8 +12,15 @@
12 12  == 2. Key concepts ==
13 13  
14 14  This microlearning centers around base64 decoding.
15 -* With base64 decoding, we mean: turning the encoded string into a readable format that eMagiz can manipulate further downstream.
16 +We mean turning the encoded string into a readable format that eMagiz can manipulate further downstream.
16 16  
18 +Essential characteristics of this functionality are:
19 +
20 +* Decoding (and encoding) of base64 strings take up additional memory (up to 33%)
21 +* Separate integration for the base64 strings apart from metadata is advisable
22 +* The component in eMagiz needs a base64 encoded string as input
23 +* Multiple times encoding and decoding in the same integration is **not** advisable
24 +
17 17  == 3. Base64 decoding ==
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 decoding on your (input) message. This functionality is beneficial when the message is encoded, but you need to manipulate part of the data.
... ... @@ -47,10 +47,10 @@
47 47  
48 48  Essential characteristics of this functionality are:
49 49  
50 -* Decoding (and encoding) 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 encoded string as input.
53 -* Encoding and decoding multiple times in the same integration is **not** advisable.
58 +* Decoding (and encoding) of base64 strings take up additional memory (up to 33%)
59 +* Separate integration for the base64 strings apart from metadata is advisable
60 +* The component in eMagiz needs a base64 encoded string as input
61 +* Multiple times encoding and decoding in the same integration is **not** advisable
54 54  
55 55  == 5. Suggested Additional Readings ==
56 56