Hi,
I'm playing around with the functionality in 12.1 and found the Dynamic Transaction Call Action block quite interesting. One of the options it gives you is to run that transaction you're calling in a parallel thread as an Asynchronous Call - see below. This will obviously speed up the execution of the transaction if some tasks can be run "later".
Asynchronous Call
If this checkbox is selected, a message is sent to run the transaction on a separate thread and the runtime is not predetermined.
What I've found is that if I send through the parameters to the transaction (while Asynchronous Call is checked), they're not persistant when the transaction is run.
For example, if I have a transaction which has an input parameter called Field_1 and it's default value is set to "temp". I call that transaction using the Dynamic Transaction Call Action Block with the "Asynchronous Call" selected. When I call the transaction from the action block, I dynamically assign the Field_1 value to be "johnny".
When I view the output of the dynamic call, it uses the value for Field_1 to be "temp" and not "johnny" as I'd assigned. I can only reason that this is because the calling transaction has already completed and the value "johnny" is no longer persistant.
Is this the case (that the inputs are not persistant when the txn is called), or is there something I need to be doing before I dynamically call the action block?
Thanks,
Lawrence
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.