The File Catalog (available for package-based projects only) represents an inventory of files, which may be assembled into packages, built, and deployed to one or more environments.
| Table of Contents |
|---|
| Note |
|---|
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. Most special characters work on Linux, but 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. You can open a support ticket if you find an issue with special characters or have any other issues. Starting with FlexDeploy 9.0.0.3, : character is handled differently in Folder or File name, if you use any files that contain : character, you should rediscover with the inactivate checkbox checked. |
The items in the catalog contain metadata, differing for each project type. If using source control for the project, the items are automatically discovered into the catalog. For some project types, the items are discoverable from the underlying source system (e.g. a development repository). The files represent metadata only, as the referenced source file is pulled from source control or the source system during the build.
...
Some project types allow creating files manually. When you click the Create button, the following screen will pop up.
...
Enter the File Name (with Path) as indicated above, then click the Evaluate button. Based on the rules for that object type and configured project properties, the remaining fields will populate. These fields will vary based on the plugin and object type. Optionally, you can adjust the configuration based on you requirements. In the example above, if you adjust the Target Location and click the Evaluate button again, all fields except Target Location will be reevaluated and Deploy Command will reflect manual change done on Target Location.
...