Index from scriptask output

RE: Index from scriptask output

mollyn126 — Sun, 06 Nov 2022 14:44:27 GMT

I just found out the reason which was the scriptask outcome, not the MNI or subprocess itself, so after I fix it and configue the MNI in subprocess appropriately, the data was passed into sub-process successfully. Thanks a lot for your help :D

RE: Index from scriptask output

adityae736199 — Wed, 02 Nov 2022 05:26:34 GMT

Could you check pv!scriptaskOutcome has any value in the instance or not. And what is the datatype configured for this variable is it of type Map which allows multiple values?

RE: Index from scriptask output

mollyn126 — Wed, 02 Nov 2022 02:38:28 GMT

Thanks for the detailed explaination Dimitris. I did configure the MNI and paste below code into the Run as many box

However the sub process still wasn't able to receive any value. I guess it's the issue with the sciptask outcome data type or the index() thing.

RE: Index from scriptask output

Dimitris Soulovaris — Tue, 01 Nov 2022 18:37:11 GMT

The problem is that he has not configured the subprocess node to run as an MNI and at the same time he is using the tp!instanceIndex variable. The expression index(pv!scriptaskOutcome,"updatedRelationships",tp!instanceIndex, null) will work fine if he makes the MNI config.

RE: Index from scriptask output

Naresh — Tue, 01 Nov 2022 18:18:11 GMT

Hi Mollyn,

I see you you are providing 4 values inside index function - index(pv!scriptaskOutcome,"updatedRelationships",tp!instanceIndex, null). it may be causing your issue. try update your index function it may solve your problem. I would suggest debug this issue first by passing the entire list to your sub process without running MNI and see if the values are coming to sub process or not.

ex: index(pv!scriptaskOutcome,"updatedRelationships", null)

RE: Index from scriptask output

Dimitris Soulovaris — Tue, 01 Nov 2022 17:48:16 GMT

After selecting the "Automatically run multiple instances of this node" option you have to define how many instances of this subprocess will have to run. In the expression editor next to the "Run this many" option you have to insert the following piece of code:

count(
  index(
    pv!scriptaskOutcome,
    "updatedRelationships",
    "entityId",
    null
  )
)

I'm using count() function and not length() because it's counting the null values also of the entityId

RE: Index from scriptask output

Chris — Tue, 01 Nov 2022 13:51:19 GMT

As Peter noted, tp!instanceindex is not available until you actually configure the node to run as MNI using this checkbox:

RE: Index from scriptask output

mollyn126 — Tue, 01 Nov 2022 04:03:57 GMT

Hi Peter, I want to use the expression output values as the input variables for my sub-process (fileId, relationshipToRemove, updatedRelationships, documentDetails, runDocumentCleanUp, etc. ), below is what I'm doing at the moment:

However, I tested and the values didn't pass into subprocess successfully. I tried your recommendation of removing the "tp!instanceIndex" and it didn't work either....

RE: Index from scriptask output

Peter Lewis — Mon, 31 Oct 2022 13:00:43 GMT

In this case you aren't using the option for "Automatically run multiple instances of this node", so the tp!instanceIndex variable won't have a value.

It's still unclear to me what you are trying to do - are you trying to create a different sub-process for each item in your list of "updatedRelationships"? If so, then you need to check that box above and then tp!instanceIndex will work. If you're not doing that, are you trying to pass a certain index (e.g. the first item)? If so, you can just hardcode 1 into your index() function above. Or another option is you can just pass the entire list into the sub-process and use it there however you need to.

RE: Index from scriptask output

mollyn126 — Mon, 31 Oct 2022 04:39:31 GMT

I just checked, seems like tp!instanceIndex is needed... I'm I right?

RE: Index from scriptask output

GopalK — Mon, 31 Oct 2022 04:11:13 GMT

Hi, are you using MNI on subprocess? if not then you dont need to use tp!instanceIndex. Just index into correct output from the process variable.