You're not gonna be in a lot of luck - it uses a heavily customized version of JS 1.8.5 (Spidermonkey) and I rarely find GPT generated scripts to be super helpful as it tends to want to constantly use newer functions/methods etc.There's a super helpful custom agent that was fed all of the classic do...

Also if you're looking to do the external signal method you originally posted about, have a look at:https://blog.floriancourgey.com/2018/07/call-another-workflow-in-adobe-campaign 

You can use the queryDef() function within your JS script to access things! https://www.martechnotes.com/master-querydef-in-adobe-campaign/ Where they talk about picking a schema, you can just designate that you're using the temporary table created within your workflow by using vars.targetSchema, eg...

Hmm! Just checking, you may need to amend the delivery script node, because it's zero indexed. delivery.variables._var[0].stringValue would correspond to the FIRST variable you've set up in the properties > variables section. In my example, delivery.variables._var[0].stringValue would be for mobileE...

It's actually an annoyingly obtuse process! You need to define a variable in the properties section, then assign the instance.vars.XXXX variable to it in the initialisation script section. I wrote a quick guide here:https://alexlangridge.com/adobe-campaign--use-defined-variables-in-an-email

Hey Shaun!I'd probably just put a split on the workflow after your data loading activity. While setting up the query targeting/filtering dimensions, just swap it to use the temporary schema from the data loading activity, and then you'll have access to all the columns from your file to filter on. Yo...

Oh gotcha! I just realised I was doing the same thing as you in your original code, using a "*.*" mask - which of course would ignore folders haha. 

Bad news: I don't know of any way to work with directories via the File() class and methods. Good news: When previously using AEP, our exports were all going to the same folder - it would just have a date stamp at the end of the name. Annoying news: We're no longer using AEP, so I can't confirm spec...

Hello! Instance variables are connected with the workflow itself - if you want to make variables accessible within a subworkflow pass in event level variables with vars.myVariableName on that specific arm of your workflow.  "The event variables (vars.xxx) enable the exchange of data between the elem...

Nah, they're all static - they're only updated if you run some sort of an activity to update the contents of the list.