You can do it in two steps:

1. Encrypt with AES (using the CryptoAPI extension).
2. Convert the resulting binary to Hex (using BinaryData).

1. Encrypt with AES

• Add the CryptoAPI extension to your module.
• Use the server action CryptoAPI_AES_Encrypt (name may vary slightly depending on version).
• Inputs typically are:
  • PlainText (Text)
  • Password / Key (Text or Binary, depending on which action you use)
  • Optional: Salt, IV, Iterations, etc.
• The action usually returns a Binary output (EncryptedData) or a Base64 Text, depending on the CryptoAPI version you’re using. If it returns Base64 Text, convert it to Binary first with BinaryData\Base64ToBinary.

Example (server action flow):

PlainText (Text) → CryptoAPI_AES_Encrypt → EncryptedBinary (Binary)

If the encrypt action returns text (Base64):

PlainText → CryptoAPI_AES_Encrypt (returns Base64Text)
          → Base64ToBinary(Base64Text) = EncryptedBinary

2. Convert AES result to Hex

Use the BinaryData extension:

• Call BinaryToHex with the AES binary output.
• The result is a Text containing only [0-9A-F], which is what you want.

Example (continuing the flow):

EncryptedBinary → BinaryToHex → EncryptedHex (Text)

Now EncryptedHex is your AES-encrypted value in hexadecimal format (no special characters).

3. Decrypt from Hex back to original text

To decrypt, reverse the process:

1. Hex to Binary: use HexToBinary(EncryptedHex).
2. AES Decrypt: call CryptoAPI_AES_Decrypt with that Binary (and the same key/parameters).

Example (server action flow):

EncryptedHex (Text)
  → HexToBinary = EncryptedBinary (Binary)
  → CryptoAPI_AES_Decrypt(EncryptedBinary, Password/Key, …)
  → PlainText (Text)

This pattern is aligned with how AES + hex is usually suggested in OutSystems (encrypt with AES, then format with Hex instead of Base64). SH1 Encrypt with key