Create Folder CA behavior anomoly

PB3.2 is permitting the “creation” of a folder with no associated pathway.

Create an Ask For Folder CA then type an invalid pathway into the text box, for example
InvalidFolder
omitting any drive or backslashes at the start and pass it to %DestPath%

Create a Check for Folder CA with %DestPath% which should return False
Create a Create a Folder CA using the %DestPath% from above
This time, the Check for Folder CA %DestPath% returns True

Proceed through the file extraction and then after extraction
Create a Check for file CA for one of the extracted files which returns True
but looking for the above folder or extracted file within Windows Explorer returns nothing.

Sample pbpx is available upon request.

It appears that the correction needs to be at 2 levels, first is the CA Create folder should fail without a pathway to write to and second, the CA to check for the existence of the folder should continue to return False.

Allowing users to type their own pathway is certain to produce an issue eventually.

Sorry for the run on appearance of the post. Several carriage returns were stripped out.

Create an Ask For Folder CA then type an invalid pathway into the text box, for example

InvalidFolder\

omitting any drive or backslashes at the start and pass it to %DestPath%

Create a Check for Folder CA with %DestPath% which should return False

Create a Create a Folder CA using the %DestPath% from above

This time, the Check for Folder CA %DestPath% returns True

Hopefully this displays better.

Please send your PBPX file. You can zip it and upload it to http://demo.ovh.eu/en.
This is a free and ad-free hosting service: after upload, they will give you a
URL. Please send this URL so we can download the Zip archive. You can send it by PM if you don’t want to share it.

Thanks for responding.

File is available at:
http://demo.ovh.eu/en/ef477f57e332bd1b637e1e1debbd3258/

To recreate the issue on your end, edit the Files to extract list and after the file extraction, edit the test.

Got the file, thank you. We’ll look at it for the next release.

Working on next update, this is not a bug unfortunately.
Having a simple InvalidFolder\ in the “Create a folder” custom action works, because it will create the “InvalidFolder” subfolder in the system’s current directory.
To find the full path, just create an “Open a document file” CA to explore the folder.

For instance, paste this custom action in the editor:
In the test, the subfolder is created in the package’s temporary folder (given by %PBSFXPATH%). Since this folder is removed when the package closes, that’s why you can’t find it.