Enfocus Community

Unfortunately we do not (yet) have the job.getVariableAsString function in NodeJS scripting. The recommended workaround for this is to place whatever it is you need in your script expression in private data and then use that private data in your script expression. It is not perfect, but it is not di...

Open the Color Picker in PitStop; you can do that via the PitStop Color tools or via the Actions in the Inspector in the Fill window. There you can create a new color in the Local group and you can name it the way you want. Make sure to check the box "Define as Spot Color alternate values"...

I was a bit puzzled by the last part of your your statement: If PitStop does not know how each individual DFE changes the color content of a file, why does it interpret neutral RGB as black and white? DFEs do not do that. but not being familiar with all settings of all DFEs out there I have been ask...

You can use the copy/paste actions: Select spot color (now one or more objects are selected) Copy Select all (this is necessary because pasting is done on the page level, not on one more objects) Paste (make sure not to move it) Select last added objects Change color Add objects to layer with name (...

It is not "Nice solution, but ...", it is "Nice solution!". Period. Using TextIndexed is the way you handle an unknown number of nodes. You can use <br> as a separator as suggested, or you could use <li> as a prefix and </li> as a postfix, and when you enclose this in the mail te...

In PitStop you cannot combine a variable with static text but when defining the value of the variable in Switch you can combine any Switch variable with static text, so it is possible.

Placing jobs in subfolders and subsubsubsubfolders requires the use of "Archive hierarchy". Here is learning session that explains how to work with hierachies: https://learning.enfocus.com/course/view.php?id=40

PitStop does not know what each and every DFE will do to modify the color content of a file. The only thing the report can tell us is what it theoretically should be ... without any additional transformations. The correct approach is that you should apply the same (or at least similar) transformatio...

We have not been able to reproduce this. What version are you using?

Right, I left that one out: the prompt goes into Parameters. Background: posting a file with parameters is like posting a form. A MIME is created with the following structure: MIME-Version: 1.0 Content-Type: multipart/related; boundary=i7wMePDuTqA3JHHXpDUEXVORVjtiNIdJVvktuGrDPUtnjZLvr --i7wMePDuTqA3...

HTTP request with the following settings:
Request type: POST (not POST a body, because you are also posting a file)
Attached file: [Job.Path], that should be the JPG
Use MIME encoding: Yes
File variable: file
Headers: x-api-key:apikey

Moreover, the code that sets Content-Length is not correct. Just opening the code in VSC showed an error on line 170.

In Folder apps bundle there is an app "File Sorter and Spacer". What you can do is first assemble all the XMLs that have to be processed into a folder and then using the app you can send them out in a specific order one by one with an interval.

The sendTo functions are not executed immediately. There can be multiple of them in a script and they are all gathered until the end of the script. Suppose you had access to the path of the outgoing connection and there were no files in the folder. Testing the number of files in the outgoing folder ...

Why do you need this? By using sendTo like you are doing the output job ends up in the correct location. Displaying the location in a message does not really add value. For input jobs you can get the path because there it makes sense: you may have to read the job input file or search for something i...