No more #%&:” -\’uploads!

No… I’m not ranting with some naughty explicative.

We are literally extracting these characters from file names on the upload, inserting the <_ > in their place. Oh yes, we are also closing any space as well with the same < _ >
We have run regressive scripts to update all prior files in the system with one of the special characters so any upload will version properly.

Did you know we had nearly nine thousand files with an “&” in the name?

Before you panic these changes only effect intangible Asset files loaded into Project Folders. It does not affect the names of tangible Assets in Inventory.

Here are some protocols to keep in mind when uploading and downloading files.

A File is uploaded if it has a space or one of the special characters listed.

The system will strip away the special characters and replace them with < _ >.
The system will fill any spaces with an < _ >.
The system append a SqID# to the left of a leading < _ > at the front of the file name. This SqID# is not visible in the system unless a user attempts to download the file.
The file will be stored as the “0” Revision with no revision number displayed and marked in the status of Pending.
The file is now named and indexed in the system.

The uploaded file is downloaded for use off-line.

When the user does a < Save As > the system’s SqID# will be visible.
While in use off-line the SqID# can be deleted including the leading < _ > or not, based of the user’s needs in off-line file management.
If the downloaded file is re-uploaded there must have been NO EDIT to the file name other then the SqID# or versioning will be lost.
Provided the file name has not been edited, the system will recognize the file and restore the SqID# if it has been removed.
The system will convert any prior version of the file to a status of Rejected and mark it Invisible.
The system will append and display the next Revision number (Rev. #) in sequence to the file re-uploaded and marks the file in the status of Pending.

Changes are made to a entirely new version of the file and uploaded.

If a new copy of the previously uploaded file is uploaded there must be NO EDIT to the file name that was originally uploaded or versioning will be lost.
Provided the file name exactly matches the original the system will recognize the file.
The system will strip away the special characters and replace them with &lt; _ >.
The system will fill any spaces with an < _ >.
The system, recognizing the file, will append the original SqID# to the left of a leading < _ > at the front of the file name. This SqID# is not visible in the system unless a user attempts to download the file.
The system converts any prior version of the file to a status of Rejected and mark it Invisible.
The system will append and display the next Revision number (Rev. #) in sequence to the file uploaded and mark the file in the status of Pending.

Tip: Watch out for designers who add their own unique versioning key and customers who edit the file name while working off-line.