| |
| META TOPICPARENT |
name="APPXAdministrator" |
APPX Source Code Control System |
| | If checked, this option will allow objects to be changed for applications within the suite.
Versions |
|
<
< | A Suite may have one or more Versions. For example, a suite may have a Production version, a Development version, and a Test version. Versions are identified by a two-character code. |
>
> | A Suite may have one or more Versions. For example, a suite may have a Production version, a Development version, and a Test version. Versions are identified by a two-character code. The same version code may be used in more than one suite. However, the applications for a specific version may not be assigned to more than one suite. |
| | Version Attributes
Applications |
|
<
< | Each Version of a Suite may have one or more Applications. The same Application may exist in more than one Version. |
>
> | Each Version of a Suite may have one or more Applications. The same Application may exist in more than one Version. However, a specific application/version may only be assigned to a single suite. |
| | Application Attributes
Scope
Projects |
|
>
> |
Projects can be defined for a Suite, a Suite/Version, or for a Suite/Version/Application. Each project is identified by a 10-character Project ID. Project ID's must be unique at each Suite/Version/Application level. In other words, you can create more than one project with the same Project ID as long as the projects are defined for different Suites, Suites/Versions, and Suites/Versions/Applications.
Depending on which level a project is define, there is an implied scope constraint. For example, if a project is defined for a specific Suite/Version/Application, then that project can only apply to that specific application and version. |
| | Jobs
Tasks
Notes |
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.