Enfocus Community

This CASE example works fine: printed=[Database.Text:SQL="SELECT CASE WHEN PrintedOn IS NULL OR PrintedOn = ' ' THEN 'was not printed yet' ELSE 'was already printed' END FROM EnfocusTeam WHERE Initials = '[Metadata.Text:Dataset="Submit",Model="XML",Path="/field-list/fie...

Here is an example: name=[Database.Text:SQL="SELECT Name FROM EnfocusTeam WHERE Initials = '[Metadata.Text:Dataset="Submit",Model="XML",Path="/field-list/field[tag='Initials']/value"]'",Connection="SwitchPublishPrint"] email=[Database.Text:SQL="...

I would indeed go for private data.
Easy to define now in a folder properties, and easy to map when you get the XML file.
If the XML contains multiple subjobs, Variable XPath Repeater can loop into the XML to produce many jobs each with corresponding private data.

Use the Data with log connection after each SQL query.
Define different dataset names on the outgoing connections.

[Job.Name] is a Switch variable, is not recognized by PitStop Pro or Server, so using it in an action list will not work. Create a variable set in PitStop, and define a JobName Text variable. Use this variable in your action list. Go to Switch, use the PitStop Server element, select your action list...

Are you using v4 or higher?
The job repository check was added with v4.
I just tested it with v6 on Mac and Win, it works as expected.

You have to stop Switch Server and use the SwitchDataRootMove tool (renamed ApplicationDataRootTool with more recent versions of Switch).

More info here.

You can use the report to count the comments.
nbComments=[Metadata.Integer:Dataset="PDFReviewCollectionReport",Model="XML",Path="count(/PDFReviewReport/Collection/file/stickynotes/contents)"]

I have an out of the box "workaround". If you use Switch and the PDF Review module , the PDF Review module detects the TEXT annotations already in the pdf file. Then the reviewer can add annotations if needed. Maybe you don't need this step, but you will need to approve or reject the docum...

Well, you don't know in advance how many files will be added to a folder. In the Assemble Job properties, you can define a very large number of jobs to wait for (Every N jobs), (a number you will never reach), and an orphan timeout value. When the first file arrives, Switch will wait n minutes (the ...

Hi Thomas,
Here is the trick:
const xpath = "string(/root/tag1)";

Subfolder search levels: Root level only
Inject: files only
Injected jobs name filter: *
Name should: match filter

Yes, there is an app for that: Inject Wildcard.
It has even more possibilities, like filtering based on name, wildcard, regex, time, depth level.
You have to use a trigger with it, FireStarter is a good candidate.

You can also document your flows.
It will create an html document of each flow.
In there you can also easily look for the flow stages.