Enfocus Community

You should not order and then rename, you should rename and then order. The way the hierarchy works is that it is attached as information to the job regardless of its name, and it materializes at the moment the job hits "Archive hierarchy". Renaming a job does not change its hierarchy info...

I have to disappoint you, Thomas. Patrick893 is no longer with us. I killed him and hanged him on the cybergallows alongside some of his botfriends. Now they are hanging there and are being tossed around by the wind. Rain has washed them and the sun has dried and blackened them. Magpies and crows ha...

This is typically something that you should also report to support: https://enfocus-community.force.com/customers/s/cases . I am personally not aware of any such problems. I am using an M3, though. Could it be related to the version of the OS? Support for MacOS 15 was added to the Fall release that ...

I missed that one. Good catch, Matthew.

It will certainly be helpful to go through a debug session, so you can see exactly where in the code the problem pops up. If you do not know how to do that, please refer to the training videos in the Learn section of our website. Glancing briefly over your code I suspect your problem lies with the q...

That is indeed your problem.There is an Action "Change blending color space" with an option to set it to "None" so you have an easy fix. Just do that with a "Select all" to make sure you change them all (there may be more than you expect, see below). Some background. A ...

This post was brought to my attention because of a bot message that slipped in and since the post was published there is something useful I can add: there is an app for that.
https://www.enfocus.com/en/appstore/product/fastlane

Thanks for sharing this, Jan. Not tested, but the modification to make sure all dependent fields are processed too, will be to replace: <!-- Root element --> <xsl:template match="/field-list"> by <!-- All field-list elements --> <xsl:template match="//field-list">

Our fault: the warning message will be removed in the next version.

There will still be a warning message when diacritical marks have been replaced, but the message is a different one.

Look at the possible return values of flowElement.getPropertyStringValue. It is a so-called overloaded function, which means that it can return more than one type of variable. In this case the return values can be string or string[]. For a single-line text you will get a string and for a multiline t...

I have no experience with the "Run Command" app. As to "Execute command" the mistake is that "Command or path" should point to powershell.exe, the path to the script is part of the "Arguments". If you need to delete files and folders have a look at the "F...

If you assemble the XMLs in a job folder first, you can use the app "File Sorter and Spacer" (part of the Folder apps bundle) to get the files out of the folder one by one with an interval.

There is no need to remove anything. On the contrary. Just open the JSON file in a text editor, scroll to the bottom and you will see it is incomplete: it ends with a comma. Editors that are JSON-aware (like VSC) will show there is an error, or you can copy&paste the file into an online JSON val...

The JSON file is incomplete so you cannot do anything with it in an automated way (or did you remove a part because otherwise it would be too big?). I could open the file as text of course. It contains URL links to the files. Do these also have to be downloaded as part of the process? Conceptually, ...

A common mistake is not being in the correct folder in VSC when attaching. You should have the script folder open at the level of the main.ts. One level too high, one level too low and you do not see the right things.