File Operation Package Action

AETLE x64 v6.4.2.30

Hi, I noticed an issue after upgrading from v6.4.1.xx that required me to revert back.

I use the File Operation and File Check Package action widgets to move files around during a package workflow. Typically, triggered by a Directory Monitor event. In which case the "Directory Monitor File Name" variable is then copied to another variable <SourceFile> which is used by some downstream and reused subpackages. 

I found that the widget would report that it had failed and that no file could be found and yet the file would be moved. The execution log indicates that no file matching <SourceFile> was found.

I put a ShowMessage in the flow and it reported the full path and filename as expected.

I suspect that it may have something to do with the file having a double slash at the front and possible the regex change. I did put a regex expression in as well but that didn't seem to help. So, I am not sure if regex expressions are expected or not for the action item. In our case it nearly always be a specific fully qualified filename.

This was a showstopper for us and I reverted back to v6.4.1.xx


 

Thanks

I had a look at the source code. We do not use regular expressions for file search it is just standard windows file mask.
And no modifications were made to this part of application.

So I can't see any issues from our site.
 

Thanks Mike

The issue definitely resolved itself after a rollback from v6.4.2.30 to v6.4.1.14 so maybe unrelated to that new feature.

I have attached the .wfp save of the subPackage. So for some context.

1. Parent Package is triggered from a directory monitor. 
2. <Directory Monitor File Name> is saved into another variable <SourceFileName> so that it can be used in a downstream subpackage that may not have been called from a monitor event
3. <SourceFile> variable is created from the original pickup folder name and <SourceFileName>. Resulting in the fully qualified file name and path that triggered the workflow
4. the workflow progresses and calls a subpackage to take the trigger file and MOVE it somewhere else. Thus protecting the file from loss and allow other files to come and go

It is this subpackage that underpins nearly all of our parent packages and as been in place since we first started to use AETL in 2018.

After correcting our directory monitors to now use the regex pattern rather than file masks I triggered the package by pushing a file in to the folder. The packages fires as expected and then flow to this subpackage. Which records a failure and yet the file in question ends up being MOVED. After attempting a number of things including openig the packages and forcing a change so they could refresh the repo database. But nothing seemed to work. I was running out of time and so reverted back to 6.4.1.14 and changing all the monitors back to using file masks instead of the regex equivalent worked as expected. 

You have confirmed the file operation doesn't use regex and I convinced myself that the filename and path were also correct.

As mentioned, the only thing I can think of is the use of a UNC path (eg. \\abc\dfs\sharename\foldername\filename.ext).

Maybe the WFP file may help
 
 

 

There is slight chance that there are some not so obvious issues with the variables

Eg trailing or leading spaces.

Can you try the following please.

Create new package
Add check file action
point to the file in question
and run it.

Do not use any variables