Difference: APPXSourceCodeControlSystem (15 vs. 16)

Revision 162010-02-09 - SteveFrizzell

Line: 1 to 1
 
META TOPICPARENT name="APPX500Features"

APPX Source Code Control System

This page describes the Source Code Control System feature of APPX Application Design.

Added:
>
>		The Source Code Control System in APPX 5.0.1 has a variety of issues which prevent it from being used successfully. The status of the Source Code Control System has therefor been changed from "Released" to "Experimental". You should not attempt to use this feature until the issues have been resolved and the status is changed to Released.
 

Concepts

Line: 22 to 24
 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

Changed:
<
<		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.
>
>		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

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.

Line: 36 to 40
 

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:
<
<
  • NO ACCESS - Does not allow design objects to be viewed or edited.
  • VIEW ONLY - Allows design objects to be viewed but not edited.
  • NOT TRACKED - Allows design objects to be viewed and edited.
  • TRACKED - Requires that a Project/Job/Task be identified before a design object can be viewed or edited.
>
>

  • NO ACCESS - Does not allow design objects to be viewed or edited.

  • VIEW ONLY - Allows design objects to be viewed but not edited.

  • NOT TRACKED - Allows design objects to be viewed and edited.

  • TRACKED - Requires that a Project/Job/Task be identified before a design object can be viewed or edited.

 

Scope Defaults

Each 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.

Line: 86 to 91
 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

Changed:
<
<		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.
>
>		 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: 107 to 113
 
  1. Projects/Jobs/Tasks Maint - Add mode is not allowed. I can only add a project from within Application Suites maint.
  2. Projects/Jobs/Tasks Maint - Object record does not show correct notes count.
  3. projects/Jobs/Tasks maint - When viewing Full Log Detail, Object record has no owner. What is the owner field used for?
Changed:
<
<

  1. Fields are missing documentation -Fixed

>
>

  1. Fields are missing documentation -Fixed

 
  1. Design - Source Code Control panel should not refer to "# for Xfer"
Changed:
<
<
  1. Design - Source Code Control panel refers to "# In Use". Don't know what this means. - It's the number of Objects with an Active status.
>
>
  1. Design - Source Code Control panel refers to "# In Use". Don't know what this means. - It's the number of Objects with an Active status.
 
  1. Design - Source Code Control - Select Project. Column headings are screwed up.
  2. Design - allowed me to select a task that had a status of pending. - Changed the status to Active automatically. Seems like the status should be Assigned before it can be selected.
  3. Design - SCC - Select Project - Does not show all available projects. Maybe because they all had the same Project ID?
Line: 121 to 127
 
  1. Design - Help pulldown list all items twice
  2. Design - SCC panel on menu still showed 0 in use after I had made a change to an input object.
  3. Design - SCC Log detail - shows changed=N for an input object after I made a change.
Changed:
<
<
  1. Design - Fixed - Tried to add a comment to an audit history record. Would not save comment.
>
>
  1. Design - Fixed - Tried to add a comment to an audit history record. Would not save comment.
 
  1. Design - SCC panel on design menu has a label "Control Level". System Admin uses "Design Access". We need to be consistent.
  2. XFER - SCC let me select object that was not complete.
  3. XFER - SCC Status values are IDENTIFIED, ACTIVE, and COMPLETED? What is this field??
Changed:
<
<
  1. XFER - SCC needs to allow xfer of Project, Job, or Tasks based on Dependence & Mgt Status. Should individual objects be allowed to be excluded?
  2. XFER - Fixed - status column not lined up.
>
>
  1. XFER - SCC needs to allow xfer of Project, Job, or Tasks based on Dependence & Mgt Status. Should individual objects be allowed to be excluded?
  2. XFER - Fixed - status column not lined up.
 
  1. XFER - two counts in footer - What are they?
  2. XFER - Clear All and Select All buttons don't seem to work.
  3. XFER - Selected For Xfer logic field should not allow null value
  4. SCC Inquiries - Menu says "Object History" - screen says "Object Inquiry".
  5. SCC Inquiries - Menu says "Objects Inquiry" - screen says "Audit Information - Search".
Changed:
<
<
  1. Project Maint - Fixed - need to enter field doc.
>
>
  1. Project Maint - Fixed - need to enter field doc.
 
  1. SCC Note - Entered notes via Opt 96. Did not select a Project/job/task. Now those notes show on every object via Opt 96.
  2. SCC Note - There is a 'Process' pulldown menu that shows one item - 'SC- SCTRACK- CUR STATUS' throughout Application Design. Is this supposed to be there?

Enhancements:

  1. Scope Maint - Need to be able to scan on Object Name field.
  2. Scope Maint - Need to be able to see all higher level scope records.
  3. Projects - need to be able to change the level that a project is attached to - Suite, Version, Application. For example, if attached to suite, need to be able to move the project to a version or individual application.
Changed:
<
<
  1. Projects - it would be nice if we could add a Project directly & specify which Suite/Ver/App it pertained to, instead of adding it in Suite/Versions/Applications first. See #12 above.
>
>
  1. Projects - it would be nice if we could add a Project directly & specify which Suite/Ver/App it pertained to, instead of adding it in Suite/Versions/Applications first. See #12 above.
  -- SteveFrizzell - 29 Oct 2007
View topic | History: r19 < r18 < r17 < r16 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback