Disable postprocessing for a folder
By default, all uploaded assets are processed using the DAM Update Asset workflow. Experience Manager Guides runs an additional processing, called postprocessing, as a part of this workflow. This also helps in generating the UUIDs
While uploading your files and folders to the Adobe Experience Manager Assets server, you can also disable the postprocessing and the generation of UUIDs.
Perform the following steps to disable the postprocessing on a given path or ignore the postprocessing for a folder:
-
Open the Adobe Experience Manager Web Console Configuration page.
The default URL to access the configuration page is:
code language-http http://<server name>:<port>/system/console/configMgr -
Search for and click on the com.adobe.fmdita.config.ConfigManager bundle.
-
Select the Ignored Paths for Post Processing option, to ignore a folder for post processing.
String value to set any standard NODE_OPTIONS (multivalued property, strings with path that omit
/at the end)Default Value:
/content/dam/projects/translation_outputnote note NOTE This property is disabled by default and the translation tab is available on the map dashboard. -
Select the Enabled Paths for Post Processing option, to enable a path for post processing.
String value to set any standard NODE_OPTIONS (multivalued property, strings with path that omit
/at the end)Default Value:
/content/dam/note note NOTE This property is disabled by default and the translation tab is available on the map dashboard. -
Click Save.
Rules to enable or disable postprocessing
By default, postprocessing is done for every folder path under the Experience Manager DAM folder. Configurations are applied for any folder according to the following rules:
- If the parent is ignored for postprocessing but the child folder is enabled, then the child and all its successors are considered enabled.
- If the parent is enabled for postprocessing but the child is ignored, then the child and all its successors are considered ignored.
- If the same folder path exists in both ignored.post.processing.paths and enabled.post.processing.paths configurations, then it’s considered ignored for postprocessing.