Encoding/storage mechanism of MX_USER_PREFS attribute

Dear experts,

I was wondering whether it's possible to programmatically set a default for users' UI task favourites, i.e. the push buttons that will be displayed in their IDM Web Dynpro UI.

When investigating the AVALUE column of attribute MX_USER_PREFS in database view IDMV_VALUE_BASIC, I expected to find the same key=values pairs in clear text that are displayed when editing this attribute from a UI task. However, that's not the case. The actual AVALUEs look very different; examples are shown below.

Questions:

1. What encoding is used to transform the key=value pairs to their encoded form (example 1)?
2. Where is the actual value stored when the size exceeds AVALUE's size limit and only the MD5 hash is stored in AVALUE (example 2)?

Best regards,

Lambert

Iy0tTm8gaGVhZGVyLS0KI01vbiBTZXAgMDEgMTY6MDg6NTUgQ0VTVCAyMDE0CkVudHJ5U2Vh

cmNoQ29tcC5UYWJsZVNvcnQuMTQuc29ydENvbHVtbj1jb2x1bW5fMQpFbnRyeVNlYXJjaENv

bXAuUmVzdWx0VGFibGUuVmlzaWJsZVJvd3M9MjUKRW50cnlTZWFyY2hDb21wLkZhdm9yaXRl

LjE1LjE9MzA2MnwwfEFjdGl2ZSBEaXJlY3RvcnkgR3J1cHBlIGFubGVnZW4KRW50cnlTZWFy

Y2hDb21wLlRhYmxlU29ydC4xNC5zb3J0RGlyZWN0aW9uPVVQCkVudHJ5U2VhcmNoQ29tcC5U

YWJsZVNvcnQuMTEuc29ydERpcmVjdGlvbj1ET1dOCkVudHJ5U2VhcmNoQ29tcC5GYXZvcml0

ZS4xMS4xPTI4OTN8MHxQcm9kdWt0IGFubGVnZW4KRW50cnlTZWFyY2hDb21wLlRhYmxlU29y

dC4xMS5zb3J0Q29sdW1uPWNvbHVtbl8xCg

!<MD5=10AF3BF3D32F656ED90DF79BF989250C SIZE=2128>