Triggering Automator process with specific file names

Tony_20992
Tony_20992 Altair Community Member
edited September 2020 in Community Q&A

Hello, 
Our team created a visual process within Automator where 2 different files are used.  Within the File Input properties, I've specified a filename with a wildcard (e.g. CRJ Weekly Test\AUD200G1#72M*) due to different dates added each day.  The process is setup with an input monitored trigger for any file added to the "CRJ Weekly Test" folder.  

Even when adding a file that is named outside of "AUD200G1#72M" the process is still triggered.  It does complete with warning that no file was processed, but I wanted to know if there was a way to avoid the process from triggering when filenames do not match.  Please let me know if you need any additional information. 

Thanks!

------------------------------
Tony Ruffy
Sr Analyst

------------------------------

Tagged:

Best Answer

  • Steve Caiels_21881
    Steve Caiels_21881
    Altair Employee
    edited September 2020 Answer ✓
    Hi Tony,

    You should be able to use the same file specification for the monitoring that you are using for the input (e.g. CRJ Weekly Test\AUD200G1#72M*).

    If there is a possibility that the 'trigger file' could arrive before the second file, then it may be possible to also add the second file to the monitoring and select the 'All Files Must Exist' in the monitoring options.  This would only be viable if there was a separate unique file specification for the 2nd file or use separate folders (as shown below).
    image

    Regards,
    Steve.


    ------------------------------
    Steve Caiels
    Professional Services
    Altair
    ------------------------------
    -------------------------------------------
    Original Message:
    Sent: 09-29-2020 01:15 PM
    From: Tony Ruffy
    Subject: Triggering Automator process with specific file names

    Hello,
    Our team created a visual process within Automator where 2 different files are used.  Within the File Input properties, I've specified a filename with a wildcard (e.g. CRJ Weekly Test\AUD200G1#72M*) due to different dates added each day.  The process is setup with an input monitored trigger for any file added to the "CRJ Weekly Test" folder.

    Even when adding a file that is named outside of "AUD200G1#72M" the process is still triggered.  It does complete with warning that no file was processed, but I wanted to know if there was a way to avoid the process from triggering when filenames do not match.  Please let me know if you need any additional information.

    Thanks!

    ------------------------------
    Tony Ruffy
    Sr Analyst

    ------------------------------

Answers

  • Steve Caiels_21881
    Steve Caiels_21881
    Altair Employee
    edited September 2020 Answer ✓
    Hi Tony,

    You should be able to use the same file specification for the monitoring that you are using for the input (e.g. CRJ Weekly Test\AUD200G1#72M*).

    If there is a possibility that the 'trigger file' could arrive before the second file, then it may be possible to also add the second file to the monitoring and select the 'All Files Must Exist' in the monitoring options.  This would only be viable if there was a separate unique file specification for the 2nd file or use separate folders (as shown below).
    image

    Regards,
    Steve.


    ------------------------------
    Steve Caiels
    Professional Services
    Altair
    ------------------------------
    -------------------------------------------
    Original Message:
    Sent: 09-29-2020 01:15 PM
    From: Tony Ruffy
    Subject: Triggering Automator process with specific file names

    Hello,
    Our team created a visual process within Automator where 2 different files are used.  Within the File Input properties, I've specified a filename with a wildcard (e.g. CRJ Weekly Test\AUD200G1#72M*) due to different dates added each day.  The process is setup with an input monitored trigger for any file added to the "CRJ Weekly Test" folder.

    Even when adding a file that is named outside of "AUD200G1#72M" the process is still triggered.  It does complete with warning that no file was processed, but I wanted to know if there was a way to avoid the process from triggering when filenames do not match.  Please let me know if you need any additional information.

    Thanks!

    ------------------------------
    Tony Ruffy
    Sr Analyst

    ------------------------------
  • Tony_20992
    Tony_20992 Altair Community Member
    edited September 2020

    Hi Tony,

    You should be able to use the same file specification for the monitoring that you are using for the input (e.g. CRJ Weekly Test\AUD200G1#72M*).

    If there is a possibility that the 'trigger file' could arrive before the second file, then it may be possible to also add the second file to the monitoring and select the 'All Files Must Exist' in the monitoring options.  This would only be viable if there was a separate unique file specification for the 2nd file or use separate folders (as shown below).

    image

    Regards,
    Steve.


    ------------------------------
    Steve Caiels
    Professional Services
    Altair
    ------------------------------
    -------------------------------------------
    Original Message:
    Sent: 09-29-2020 01:15 PM
    From: Tony Ruffy
    Subject: Triggering Automator process with specific file names

    Hello,
    Our team created a visual process within Automator where 2 different files are used.  Within the File Input properties, I've specified a filename with a wildcard (e.g. CRJ Weekly Test\AUD200G1#72M*) due to different dates added each day.  The process is setup with an input monitored trigger for any file added to the "CRJ Weekly Test" folder.

    Even when adding a file that is named outside of "AUD200G1#72M" the process is still triggered.  It does complete with warning that no file was processed, but I wanted to know if there was a way to avoid the process from triggering when filenames do not match.  Please let me know if you need any additional information.

    Thanks!

    ------------------------------
    Tony Ruffy
    Sr Analyst

    ------------------------------
    Thanks Steve, adding multiple file specifications within the trigger worked!  Thanks for your help

    ------------------------------
    Tony Ruffy
    Sr Analyst
    Gap Inc Store Labs
    San Francisco CA
    505-462-0613
    ------------------------------
    -------------------------------------------
    Original Message:
    Sent: 09-30-2020 04:35 AM
    From: Steve Caiels
    Subject: Triggering Automator process with specific file names

    Hi Tony,

    You should be able to use the same file specification for the monitoring that you are using for the input (e.g. CRJ Weekly Test\AUD200G1#72M*).

    If there is a possibility that the 'trigger file' could arrive before the second file, then it may be possible to also add the second file to the monitoring and select the 'All Files Must Exist' in the monitoring options.  This would only be viable if there was a separate unique file specification for the 2nd file or use separate folders (as shown below).
    image

    Regards,
    Steve.


    ------------------------------
    Steve Caiels
    Professional Services
    Altair
    ------------------------------

    Original Message:
    Sent: 09-29-2020 01:15 PM
    From: Tony Ruffy
    Subject: Triggering Automator process with specific file names

    Hello,
    Our team created a visual process within Automator where 2 different files are used.  Within the File Input properties, I've specified a filename with a wildcard (e.g. CRJ Weekly Test\AUD200G1#72M*) due to different dates added each day.  The process is setup with an input monitored trigger for any file added to the "CRJ Weekly Test" folder.

    Even when adding a file that is named outside of "AUD200G1#72M" the process is still triggered.  It does complete with warning that no file was processed, but I wanted to know if there was a way to avoid the process from triggering when filenames do not match.  Please let me know if you need any additional information.

    Thanks!

    ------------------------------
    Tony Ruffy
    Sr Analyst

    ------------------------------