Resolving a SQLI as bind parameter within another SQLI does not work

book

Article ID: 87484

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Error Message :
N/A

When a SQLI is used as a bind parameter in another SQLI, it returns 0 rows. 

Example:

VARA.SEC_SQLI.NESTED_VARA - Notice that column {2} for UC_CLIENT_SETTINGS is 1000003

<Please see attached file for image>

0EMb0000001QM74.png

When used as a Bind Parameter, the SQL returns 0 rows.

Use VARA.SEC_SQLI.NESTED_VARA as a parameter in VARA.SEC_SQLI.LIST_STATIC_VARA_VALUES.

{VARA.SEC_SQLI.NESTED_VARA,UC_CLIENT_SETTINGS,2} returns 0 rows when it should be returning 1000003

<Please see attached file for image>

0EMb0000001QM79.png

 

Cause

Cause type:
Defect
Root Cause: Nested variables with type SEC_SQLI did not work if variable is used within {} expression as bind-parameters. Preview did not return any result.

Environment

Release: AUTWAB99000-11.0-Automic Workload Automation-Base Edition
Component:

Resolution

Update to a fix version listed below or a newer version if available.

Fix Status: Released

Fix Version(s):
Automation Engine 12.0 - Available
Automation Engine 11.2.3 - Available

Additional Information

Workaround :
Use a regular SQLI instead of SEC_SQLI.

Attachments

1558693115007000087484_sktwi1f5rjvs16m1t.png get_app
1558693113051000087484_sktwi1f5rjvs16m1s.png get_app