Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX Source Code Control System | ||||||||
Line: 6 to 6 | ||||||||
This page describes the Source Code Control System feature of APPX Application Design. | ||||||||
Added: | ||||||||
> > | Concepts
| |||||||
Suites | ||||||||
Changed: | ||||||||
< < | Suite ID | |||||||
> > |
The APPX Source Code Control system requires suites that are to be managed must first be defined. The Suite Maintenance program can be used to enter and edit suites.
AttributesSuite ID | |||||||
Each Suite is uniquely identified by a 10-character Suite ID. | ||||||||
Changed: | ||||||||
< < | Suite Description | |||||||
> > | Suite Description | |||||||
Each suite has a 30-character description. | ||||||||
Changed: | ||||||||
< < | Design Access | |||||||
> > | Design Access | |||||||
Design access controls what level of access is allowed for the applications within a suite. Design access must be specified for each suite and is inherited by each application in the suite in the event that design access is not specified for the application or the application's version. The following design access levels are allowed:
| ||||||||
Changed: | ||||||||
< < | Default Scope | |||||||
> > | Scope DefaultsEach Suite must include default scope specifications indicating that all design objects are to be automatically included or excluded and which design modes are allowed for included objects. Scope Defaults must be specified for each suite and are inherited by each application in the suite in the event that scope defaults are not specified for the application or the application's version. The scope default fields provide a quick way to specify the equivalent of a scope record for the suite. | |||||||
Changed: | ||||||||
< < | Each Suite must include a default scope specification indicating that all processes are to be automatically included or excluded. | |||||||
> > | Scope defined at the suite level cannot be overridden by project scope records. In other words, a project manager cannot define a project that is outside of the scope defined for the suite. | |||||||
Changed: | ||||||||
< < | Scope records defined at the suite level cannot be overridden by project scope records. In other words, a project manager cannot define a project that is outside of the scope defined for the suite. | |||||||
> > | The scope default values are not inherited by individual scope records when the fields are null (The fields should not be null in individual scope records.)
Scope Type
Allow Add? | |||||||
Changed: | ||||||||
< < | The scope default values in the suite record define the equivalent of a default scope record. They are not values that are inherited by individual scope records when the fields are null (The fields should not be null in individual scope records.)
Versions | |||||||
> > | If checked, this option will allow new objects to be added to applications within the suite.
Allow Del?If checked, this option will allow objects to be deleted from applications within the suite.Allow Chg?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. | ||||||||
Changed: | ||||||||
< < | Applications | |||||||
> > | Applications | |||||||
Each Version of a Suite may have one or more Applications. The same Application may exist in more than one Version. | ||||||||
Added: | ||||||||
> > | ScopeProjectsJobsTasksNotes | |||||||
Bugs: | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
Enhancements:
| |||||||
-- SteveFrizzell - 29 Oct 2007 | ||||||||
Added: | ||||||||
> > |
|