Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Deleted: | ||||||||
< < | ||||||||
APPX Source Code Control SystemThis page describes the Source Code Control System feature of APPX Application Design. | ||||||||
Line: 23 to 22 | ||||||||
Scope can be defined for Projects, Jobs, and Tasks. Scope can also be defined for Suites, Versions, and Applications. If you define scope for a Suite, then all projects tied to that Suite, its Versons, or its Applications will be constrained by the scope defined for the Suite. If you define scope for a specific Version of a Suite, then all projects tied to that Version or its Applications will be constrained by the scope defined for the Suite and the Version. The scope defined for a Project, Job, or Task cannot broaden the scope defined for the Suite, Version, or Application that the projected is tied to.
Notes | ||||||||
Deleted: | ||||||||
< < | ||||||||
Notes can be attached at many different points within the structure of the source code control system. Notes can be attached to Suites, Versions, Applications, Projects, Jobs, Tasks, Scopes, and Objects.
Suites | ||||||||
Line: 54 to 51 | ||||||||
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 | ||||||||
Deleted: | ||||||||
< < | ||||||||
Allow Add? | ||||||||
Line: 75 to 71 | ||||||||
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 AttributesScope | ||||||||
Added: | ||||||||
> > | Scopes allow you to control what objects can be accessed as part of this Application, Suite, Task or Project. Scopes work with Design Access, and in some cases, have no meaning. For example, if Design Access is NO ACCESS, then Scope is irrelevant, since design access is prohibited. Scopes can be specified at the Suite, Version, Application, Project, Job and Task levels (highest to lowest). A scope at a lower level modifies or overrides a scope at a higher level. Scopes at the same level are combined to get a net effect. For example, you might have a Scope that allows changes to all subroutines, and another Scope that disallows changes to a specific subroutine. | |||||||
ProjectsProjects 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. | ||||||||
Changed: | ||||||||
< < | 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. | |||||||
> > | Depending on which level a project is defined, 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 | ||||||||
Added: | ||||||||
> > | A Job is the intermediate level of work. Jobs are subordinate to Projects. Each Project may contain multiple Jobs, and each Job may contain multiple Tasks. If you have set Design Access to TRACKED in any of your Suites / Versions / Applications, then the designer will have to pick a Project / Job / Task to log the activity against. | |||||||
Tasks | ||||||||
Added: | ||||||||
> > | A Task is the lowest level of work. Task are subordinate to Jobs, which are subordinate to Projects. Each Project may contain multiple Jobs, and each Job may contain multiple Tasks. If you have set Design Access to TRACKED in any of your Suites / Versions / Applications, then the designer will have to pick a Project / Job / Task to log the activity against. | |||||||
Notes | ||||||||
Added: | ||||||||
> > | Use this option to enter or view any free form notes. Notes can be associated with Suites, Versions, Applications, Projects, Jobs, Tasks and Objects. | |||||||
Bugs:
| ||||||||
Line: 98 to 107 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Line: 112 to 121 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Enhancements:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
-- SteveFrizzell - 29 Oct 2007 | ||||||||
Added: | ||||||||
> > | ||||||||
|