Content Comparison

Starting with FlexDeploy version 9.0.0.3, following a new escape sequence is now used. This means that if you use any your files that contain these certain characters, you should will need to rediscover them with the inactivate "Inactivate Missing Files" checkbox checked. A After doing so, a new file will appear. The name will be , with a name that is similar but will be percent-encoded. Files with \ in them didn’t work previously. Files with a colon will be in different places in the file catalog as of 9.0.0.3, so any files with : in there will lose their history and packages containing them will need to be modified to have the file in the new location Previously, files containing backslashes (\) didn't work with FlexDeploy. Also, any files with colons in their names will be rediscover with escape sequence and not have any history. Packages containing these files will need to be updated to reflect their new location, and builds will need to be redoneexecuted again.

If you want to use one of these characters in a project property or an input for one of the operations, you should escape it as well.

In addition, Oracle requires escaping \ ? * and / that are used inside of folder names when making SOAP calls.

For instance if you create a folder named

?|//?|<\\>%3a"{})((\*&^%$#@!++=/\.TF1.TF1_

in the folder

/shared/Custom/Financials/Test Workflow Notifications/Test_V1

You must escape it as

/shared/Custom/Financials/Test Workflow Notifications/Test_V1/\?|\/\/\?|<\\\\>:"{})((\*&^%$#@!++=\/\\.TF1.TF1_

to use it in a SOAP call, so enter it that way in FlexDeploy.

When you discover that folder, in FlexDeploy it will show up encoded after being escaped so that it can be stored on the filesystem and in zip files.

Known Limitations

On Windows, folders and files cannot start or end with spaces. If it is done, Windows endpoints cannot be used, and FlexDeploy on Windows will have similar issues.

If you are exporting to SCM, most special characters should still work on Linux, but more failures on Windows are likely. Windows has protected names for files and folders like COM2 and CON. If you use a protected name as a folder name, this will also fail on Windows. Git SCM is tested the most with special characters. It is likely that other SCMs will have issues handling special characters.

You can open a support ticket if you find an issue with special characters or have any other issues.