DecryptText

This activity enables users to decrypt text by using the same key encoding and decryption algorithm that were employed during the encryption process. To successfully decrypt the text, it is crucial that the key and algorithm match those used for encryption.

Properties

INPUT

Algorithm: This parameter indicates to choose the algorithm type from the drop-down menu that is used to decrypt the text based on it.

1. AES(Deprecated)
2. AES GCM
3. DES (Deprecated)
4. RC2 (Non-FIPS) (Deprecated)
5. Rijndael (Non-FIPS) (Dperecated)
6. Triple DES.

Refer to the documentation below to view the types of algorithms.
By default, the activity recommends the most commonly used type, “AES GCM”.

DelayAfter: It assists the user to add a delay before initiating subsequent activities. The delay duration here is in milliseconds. By default, it is set to “1000” milliseconds.
When the option is left blank, the delay will not be considered.

DelayBefore: It assists the user in adding a delay before starting the execution of the activities. The delay duration here is in milliseconds. By default, it is set to “1000” milliseconds.
When the option is left blank, the delay will not be considered.

Input Text*: This parameter indicates to provide the encrypted input text which needs to be decrypted.

It accepts the values in “String” datatype. You can either hardcode the values in “String” format or can provide the variable in “String” datatype.

Key Encoding: It assists the user to choose the key encoding type from the drop-down menu that is used to perform the encryption algorithm.

Click here to refer the documentation to view the types of key encoding.

By default, the activity recommends the most commonly used type, “Unicode UTF-8”.

Secret Key*: This parameter indicates to provide the key which is used by algorithm chosen to encrypt as well as decrypt the file.

This field accepts values in “String” datatype. You can either hardcode the values in “String” format or can provide the variable in “String” datatype.

MISC

DisplayName: Displays the name of the activity. The activity name can be customized, which aids in troubleshooting.

SkipOnError: Specify the “Boolean” value as “True” or “False.”

True: Continue executing the workflow regardless of any errors thrown.
False: Halt the workflow if it encounters any errors.
None: If the option is left blank, the activity will, by default, behave as if “False” were chosen.

Version: It indicates the version of the feature being used.

OUTPUT

Output Text: It assists the user in declaring a variable here to view the decrypted text as output.

This field returns values in the “String” datatype. You can either hardcode the values in “String” format or provide a variable in the “String” datatype.

Result: It provides the ability to view the execution status of the activity. It returns values in “Boolean.”

True: Indicates that the activity has been executed successfully without any errors.
False: Indicates that the activity has been unsuccessful due to an unexpected error being thrown.

* Represents mandatory fields to execute the workflow.

Here’s an example of how the activity is used in the workflow:

In this example, the “Decrypt Text” activity is used to decrypt text that was previously encrypted. Click here to learn how the “Encrypt Text” activity works.

Steps to build the bot:

1. Open a workflow.
2. Drag and drop the “DecryptText” activity into the workflow and place it next to the “WriteLog” activity.
a. Double-click on the activity to provide the details.
b. Proceed with the default algorithm type (AES GCM).
c. Navigate to the “Input Text” field in the properties section to provide the input. Use the text that was encrypted in the “EncryptText” activity as the input.
d. Next, go to the “Secret Key” field and provide the same key that was used in the “Encrypt Text” activity to decrypt the text. Use “ABC123456789TEXT” as the key.
e. Keep the other options at their default values.
f. Next, navigate to the “Output Text” field in the output section of the properties to declare a variable to store the decrypted text. Here it is as “DecryptText”.
2. Now, place the “WriteLog” activity to view the decrypted text.
a. Provide the input as “Text” and set the log level to “Info”.
3. Save and execute the workflow.