Enfocus Community

I searched the existing posts, didn't find an exact fit for what I want to be able to do. I'm simply looking for a code example showing the combining of perhaps a data field from the job, and perhaps some other static custom text, and writing it to a local file (on Windows), UTF-8. So: defining the ...

Call me a hack, I'm new to JS (worse yet, within Switch), this worked for me - a blend of observations by Gabriel. I used a previous folder in the flow to attach the field I needed as the JobState like so: '[Metadata.TextIndexed:Path="/field-list/field[6]/value",Dataset="Submit",...

You are on the right track. The only thing you still have to do is to send the job to the output folder. In your case a single output connection will be enough, so in the properties of the script you define it as having just one output connection and the end of the jobArrived function you add: job....

Thanks! Turns out I did have to use "IndexOf", and I'm golden!

What am I missing? I'm attempting to stash a piece of text in the JobState to be retrieved later by a configurator. // Is invoked each time a new job arrives in one of the input folders for the flow element. // The newly arrived job is passed as the second parameter. function jobArrived( s : Switch,...

Thank You both Gentlemen! I knew about "It's much easier to understand what //field[tag='Gramvikt']/value is than what /field-list/field[2]/field-list/field[1]/field-list/field/field-list/field/value is... " but never having dealt with it in the context of a script and not sure how "d...

Rather than my spaghetti folder configuration to do this, I decided to try and conquer a script. The purpose of the script is to grab data from 1 (of several) fields submitted to a Submit Point by a Connector (XML job ticket), and use if/then's to determine which additional email address should be a...

mclarke wrote: ↑Thu Apr 12, 2018 6:57 pm I will make the change, thank you.

Enfocus doesn't really make interpreting the help file easy for beginners.

Right??! It doesn't translate well, there's a "layer"missing I'd say.

With XML chosen as the Delivery Format in my Connector, and the "Include File Info" option checked: I had been using <xsl:value-of select="//*[tag='JobName']/value"/> in my .xsl file, and that works fine but only with *legal* XML element names (meaning it didn't work with the 2 f...

What I need to accomplish is really very simple, I just want to output a CSV file from the metadata submitted in a connector. And one of the pieces of data I need is the file name being submitted. I finally noticed the "Include File Info" option in ConnectALL 2018. And a basic XSLT transfo...

gabrielp wrote: ↑Thu Oct 29, 2015 2:59 pm For me, what always helps me to learn scripting/programming languages or concepts is to first start with a problem and tackle something new in my attempts to solve it.

Couldn't agree more. Any hints on learning the fixture panel in Switch Scripter?

Peace,

Rick

Actually I haven't even tried it, I *assumed* it was a no-go, guess I'll have to at least try it.

I have a flow receiving ConnectALL submitted jobs where some fields may not exist depending on the options chosen in the connector. Challenge is, I want to include those optional fields in an email from Switch (when they *are* populated) - but need to not error out if they're *not* included. And the...

I will try that, thanks!

That at least highlights the opening value tag <value> for the correct node and doesn't give an error in that dialog. For testing purposes I was playing with an existing SQL call (just some place I could define a variable) and it gives this error in response to the following in the "Text with v...