Changes for page Base64 decoding

Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.etorken

Content

...	...	@@ -33,7 +33,7 @@
33	33	* The component in eMagiz needs a base64 encoded string as input
34	34	* Multiple times encoding and decoding in the same integration is **not** advisable
35	35
36		-The Base64 decode algorithm converts plain text into original data. Technically, it can be said that it converts six-bit bytes into eight-bit bytes. So when you have the base64 string of QUJD, you could manually convert this to a readable format. You can find an excellent explanation of how it works [here](https://base64.guru/learn/base64-algorithm/decode). Luckily for us, eMagiz will do all the heavy lifting, and we do not have to take out pen and paper.
	36	+The Base64 decode algorithm converts plain text into original data. Technically, it can be said that it converts six-bit bytes into eight-bit bytes. So when you have the base64 string of QUJD, you could manually convert this to a readable format. You can find an excellent explanation of how it works [[here>>https://base64.guru/learn/base64-algorithm/decode||target="blank"]]. Luckily for us, eMagiz will do all the heavy lifting, and we do not have to take out pen and paper.
37	37
38	38	In the remainder of this microlearning, we will look at how you could implement this logic within the eMagiz tooling.
39	39
...	...	@@ -51,13 +51,8 @@
51	51
52	52	Now that we know how to implement it, we can quickly look at possible use cases for this logic. We see this logic popping up mainly when dealing with attachments/files (i.e., pictures, pdf) within XML messages.
53	53
54		-== 4. Assignment ==
	54	+== 4. Key takeaways ==
55	55
56		-Look for places where you could use this logic to aid your integration process within your (Academy) project.
57		-This assignment can be completed with the help of your (Academy) project you have created/used in the previous assignment.
58		-
59		-== 5. Key takeaways ==
60		-
61	61	Essential characteristics of this functionality are:
62	62
63	63	* Decoding (and encoding) of base64 strings take up additional memory (up to 33%)
...	...	@@ -65,18 +65,13 @@
65	65	* The component in eMagiz needs a base64 encoded string as input
66	66	* Multiple times encoding and decoding in the same integration is **not** advisable
67	67
68		-== 6. Suggested Additional Readings ==
	63	+== 5. Suggested Additional Readings ==
69	69
70	70	If you are interested in this topic and want more information, please read the help text provided by eMagiz and the following links:
71	71
72		-* https://base64.guru/learn/base64-algorithm/decode
73		-* https://www.base64decode.org/
	67	+* [[Decode Algorithm>>https://base64.guru/learn/base64-algorithm/decode||target="blank"]]
	68	+* [[Decode Online>>https://www.base64decode.org/||target="blank"]]
	69	+)))
74	74
75		-== 7. Silent demonstration video ==
76		-
77		-This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned.
78		-
79		-{{video attachment="intermediate-data-handling-base64-decode.mp4" reference="Main.Videos.Microlearning.WebHome"/}})))
80		-
81	81	((({{toc/}}))){{/container}}
82	82	{{/container}}