AD Orchestration Activities - Output

[stevejarman]

I'm working on some AD Orchestration stuff at the moment and hitting a bit of a documentation roadblock.

The thing I'm trying to sort out is, say I have a "Query AD" activity in my workflow, and it says that one of its outputs is "output" (which contains the main returned payload), how do I then ACCESS that output from the next activity in the workflow?

e.g. my next activity is a "Run Script" and all I'm attempting to do is gs.log() whatever was returned as output by that previous "Query AD" activity.

I've been through the doco, watched a dozen YouTube videos... just can't find an answer on how this hangs together. I can see the outputs available under the "Data" tab, but the drag and drop functionality doesn't work into something like a Script box. I'm guessing it only works when dragged into an "input",

[Ted Jennings · Accepted solution]

Hi Steve,

Yeah, this took me awhile to figure out as well. The output will go to the databus, which you can see in the Data tab.

That number in the parentheses is what you'll use to feed to the next activity.

I created the AD account in the first activity (Create AD Account) which outputs the SAM account name to Output2. I then feed that into the Sam variable of the next activity (Create Password) with the format ${data.get(databus number).Output(output number)}

Keep in mind, that if you change the activity it will usually create a new databus number, and you'll need to update the string in any other activities that rely on it.

Ted

[stevejarman]

Oh - that's awesome! Thanks 🙂

I didn't realise that whole Data tab was accessible as the "data" object, or what the number in brackets meant!

This is now doing exactly what I wanted - gs.log(data.get(3).output); - Perfect!