Transaction List Block

From Genesys Documentation
Jump to: navigation, search
This topic is part of the manual Designer User's Guide for version Current of Designer.

Use this block when you want to assign transaction list values to variables.

Related documentation:

Using this block

You can use the Transaction List block when you want your Designer application to lookup a certain value in a transaction list and store it in a variable.

To use this block, add it to your application and click Add Assignment. Select the variable that will hold the assigned value, and then specify the details for the transaction list value you want Designer to lookup.

Using a Transaction List block can be useful in certain scenarios. But for more advanced database handling in Designer, Data Tables are recommended.


In this example, we want our application to obtain a password value from a transaction list.

Des transaction list.png

We've defined a variable called TxListValue to hold this value. After adding the block to the application, we select that variable and provide the details for the transaction list value we want to assign it. In this case, we've told Designer to assign it the value for password in the APIKey section of the CaseLookupAPI transaction list.
Variables are assigned string values when List, Item, and Key are all specified, or key-value pairs if you only specify List and Item (for example, {Key1:value1, Key2:Value2}).
Here is how our example lookup request maps back to the actual transaction list resource (you may not have access to view or modify transaction lists, so this is just provided for informational purposes):Des gax txlist.pngNotice that the password value is encrypted (i.e. masked by asterisks). If the Key of a transaction list option is specified as being a password, the Value of the field is automatically hidden. However, Designer is able to read these encrypted values and use them in applications, while maintaining the secure handling.

To learn more about how Designer handles secured data in variables, see Securing Variables.

Retrieved from " (2024-05-26 22:22:17)"
Comments or questions about this documentation? Contact us for support!