AWI Location Filter Shows Invalid Path Error with Backslashes

Products

• Automic Automation

Issue/Introduction

When performing object searches in the Automic Web Interface (AWI), entering a folder path using backslashes in the Location filter may result in an "Invalid path" validation error. This issue occurs because the filter expects forward slashes, despite the "In Folder" column displaying backslashes.

Steps to reproduce:

1. Make sure you're in a system/client with many objects in different folders.
2. Use the global search textbox and search for something like JOBS that will come back as being in a folder\subfolder - instead of clicking on a single item, choose the "View # objects" option at the bottom of the "Objects" list
3. Note that the "In Folder" column will have some objects that show something like: \FOLDER\SUBFOLDER (for instance, \TEST\SUBFOLDER)
4. Click on the filter button in the upper right of the Object Search screen
5. Click into the Location text box (not using the picker, but going to type something)
6. Type in exactly what is in the "In folder" column that has a \FOLDER\SUBFOLDER

Expected behavior:
As the "In Folder" shows backslashes, it should allow this, or if not allowed, the warning sign should say "invalid character \ in path"

Actual behavior:
Warning icon shows up. It says "Invalid path"

Environment

Version: 24.4.5 and earlier, 26.0

Cause

DE210797

Resolution

This will be fixed in a future release of Automic Automation so that both forward slashes and backslashes are allowed.  Subscribe to this article for updates on releases.

Workaround:
Use forward slashes: /FOLDER/SUBFOLDER in the Location bar search
OR use the folder picker