Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

AEM Watch Folders

Tim_Goodman_BTE
Level 4
Level 4

I am trying to create a simple Watch Folder:

1) Take input of an XML file

2) Create a PDF using XML and XDP (Using "Generate Non-Interactive PDF") - Using a workflow

3) Write PDF to output folder

The workflow works (I've tested it).

The Watch folder gives a PathNotFound Exception on the payload:

crx:/etc/fd/watchfolder/staging/watch-folder/Pxc70daf9d779acfdd9e95d9bf/report.xml'

However, if I pause the Workflow instance using a "Participant Step", I can see that the input XML has actually written to the path:

crx:/etc/fd/watchfolder/staging/watch-folder/Pxc70daf9d779acfdd9e95d9bf/input/report.xml'

Is this a bug?

Additionally - the documentation is quite unclear - there is a setting on the Watched Folder "Payload Mapper Filter" which is not described

AEM 6.3 Forms Help | Watched folder in AEM Forms

I can't see how to get a file output from the Watched Folder...

Caused by: com.adobe.granite.workflow.WorkflowException: com.adobe.granite.workflow.WorkflowException: com.adobe.fd.output.internal.exception.OutputServiceException: AEM_OUT_001_003:Unexpected Exception: Error of type 'javax.jcr.PathNotFoundException' thrown on attempting operation 'CONNECT' on URL 'crx:/etc/fd/watchfolder/staging/watch-folder/Pxc70daf9d779acfdd9e95d9bf/report.xml'. Message = [Node with path /etc/fd/watchfolder/staging/watch-folder/Pxc70daf9d779acfdd9e95d9bf/report.xml does not exist.]

1 Accepted Solution
Tim_Goodman_BTE
Correct answer by
Level 4
Level 4

Sorry looping back - solved the problem.

The Watched folder Output folder pattern needed to be set to:  %F.pdf

As mentioned, this is a common use case that should be in the online documentation

View solution in original post

12 Replies
smacdonald2008
Level 10
Level 10

I asked our team to look at this question.

TundraSteve
Level 8
Level 8

Recreated the issue looking into it and will report back.

Tim_Goodman_BTE
Correct answer by
Level 4
Level 4

Sorry looping back - solved the problem.

The Watched folder Output folder pattern needed to be set to:  %F.pdf

As mentioned, this is a common use case that should be in the online documentation

View solution in original post

Tim_Goodman_BTE
Level 4
Level 4

Additionally, in the workflow:

Input: 

  • Set to relative to Payload folder
  • input/report.xml

Output

  • Under Payload folder
  • output/output.pdf
briankasingli-4
Level 2
Level 2

Hello Tim,

Can you please give me a use case to why you would want to use a watch folder?

Couldn't we just set a launcher to watch a folder in DAM assets for any file uploads?

Tim_Goodman_BTE
Level 4
Level 4

Wow - old post!

The Watch Folder functionality allows for another system to generate asynchronous file transformations without actually ingesting the file into the JCR. 

This functionality originally existed in LiveCycle (which was the forerunner to AEM Forms).  There are clients that still want to perform this kind of transformation

ak_gfb
Level 2
Level 2

This has frustrated me for weeks, so thank you for sharing.

Setting workflow input to "input/<file.extension>" seems to work only if you know what the input file name is.  Is there a way around this?

I've tried "input/%F.pdf", "input/%F.%E", "input.pdf", "*.pdf", "input", the 'use payload' setting, etc.  All throw the same or similar error about not finding the node.

Tim_Goodman_BTE
Level 4
Level 4

It sounds like you are setting the input to include a subfolder

I think you'll need to use separate attributes for folderpath and includeFilePattern

also note that I think that a subfolder called "input" is created under your folder path automatically

ak_gfb
Level 2
Level 2

Thanks for the reply on an old post.  I made a new thread with my full question since I think I'm getting into something different.

Regarding your suggestions, I don't believe I am or should be dealing with subfolders beyond including "input/" in the workflow input.  I don't how to tweak folderPath and includeFilePattern to make the workflow look into a specific path.  I imagine I want to include everything for testing purposes so I left includeFilePattern wide open.

Tim_Goodman_BTE
Level 4
Level 4

Ah, yes - I see the problem you are facing.  Yes, in this example I hardcoded the input filename, I can't remember if the use payload option worked

I think I solved this already (it was a while ago!) - let me have a look and I'll reply on the other thread