AEM Watch Folders | Community
Skip to main content
T
Tim_Goodman_BTE
June 6, 2017
Solved

AEM Watch Folders

  • June 6, 2017
  • 12 replies
  • 9082 views

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.]

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Tim_Goodman_BTE

    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

    12 replies

    smacdonald2008
    smacdonald2008
    June 6, 2017

    I asked our team to look at this question.

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    August 11, 2017

    TundraSteve any help here?

    ~kautuk

    Kautuk Sahni
    U
    Adobe Employee
    user7587541Adobe Employee
    Adobe Employee
    August 11, 2017

    Recreated the issue looking into it and will report back.

    T
    Tim_Goodman_BTEAuthorAccepted solution
    August 13, 2017

    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

      smacdonald2008
      smacdonald2008
      August 13, 2017

      Thank you for posting solution!

      T
      Tim_Goodman_BTEAuthor
      August 13, 2017

      Additionally, in the workflow:

      Input: 

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

      Output

      • Under Payload folder
      • output/output.pdf
        briankasingli-4
        briankasingli-4
        June 1, 2018

        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?

        T
        Tim_Goodman_BTEAuthor
        June 3, 2018

        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

          A
          ak_gfb
          April 29, 2019

          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.

          T
          Tim_Goodman_BTEAuthor
          May 1, 2019

          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

          Show more replies
          Terms & ConditionsAccessibility statement

          Loading footer...