Sql with result and process step parameter types

Question

Hello 
 I hope someone could help me understand how data types are handled in process step parameters. 
 My first question is about the SQL with result component. I seem to be able to get only a single field as a string from this component, i.e. I am unable to use it for queries that produce more results. I am unsure if this is working as intended or caused by the way I handle the output. I assume I am doing it wrong, but is this component intended to return more than a single field? 
 Secondly, I am using 'Value = "&OUT(<parameter name>)&"' to pass output values from previous steps as arguments into my receiver scripts. The data types I can pass seem to be limited by string conversion. Am I getting this wrong? If not, is there a way to pass data as any type? 
 Thanks!

Barry Jackson · Accepted Answer

Hi, 
 The short answer is that all parameters (JobRunParameter) on a job step are (and have to be) of type string. 
 If you need to do something more complicated you should consider using a script. 
 HTH, Barry.

Markus Weiss-Ehlers · Answer

Do not use Variables() as these are connection specific (that why they are definitely not working cross-queue) and may even fall running on the same queue due to the multiple execution slots. 
 You could either use the script result as out-parameter and use the out-paramter in the second script or you are using the parameter collection in your second script and add more to this collection in your first script. Please check this thread for more information https://www.oneidentity.com/community/identity-manager/f/forum/31220/is-it-possible-through-a-process-to-pass-the-entire-pram-collection-to-a-script

Endpoint Privilege Management

Sql with result and process step parameter types

Top Replies