Help: SDP Add

FieldDescription
Submitter (Required)The first and last name of the person submitting the pattern idea.
OwnerThe first and last name of the person actually writing the pattern.
Title (Required) [60 Character Limit]A short title for the pattern showing what it's going to do.
DescriptionA more detailed pattern description. This should briefly explain what the pattern will check or do. The Steps to Identfiy explain how the pattern will work.
ClassThe major product class to which the pattern applies. This is the collapsible field in the SCA report. Pick from the drop down list.
Category (Required)A subset of the Class.
Component (Required)A subset of the Category
StatusA drop down list that shows the current status of the pattern. Making a change to the database does not affect the actual pattern in the patterns/local directory. That must be done manually.
ProposedAvailable to be written by any available pattern writer.
AssignedAssigned to an owner or pattern writer.
In-ProgressThe pattern is actively being developed.
CompleteCode complete and ready for general testing.
StagingMoved to the staging area for beta and pre-release testing.
ReleasedReleased to the public. NOTE: You still need to manually copy the developed pattern to the patterns/local directory.
MaintenanceA mature pattern that is under maintenance.
ObsoleteThe pattern is no longer valid and has been removed from the public. NOTE: You still need to manually remove the file from the patterns/local directory.
RejectedThe pattern submission has been rejected with the reasons documented in the Notes field.
Pattern IDThis is an internal tracking number unique to each pattern submission that cannot be changed.
Pattern FileThe pattern filename that will be comitted to the supportconfig diagnostic pattern (SDP) repository. This must be a unique file name within the SDP category directory with the format, prodID-00000.pl. For example, lvm-00001.pl
Pattern TypeThe kind of pattern file to be written, such as Bash, Pythong or Perl. The pattern type will determine the pattern file template to be generated.
TID URLTID URL solution to which the pattern will be linked. A TID tag is assumed; do not include it.
BUG URLBUG URL to which the pattern will be linked. A BUG tag is assumed; do not include it.
URL Pair [1-5]The tag and URL for a solution to be linked to the pattern in the form of TAG=URL. For example, SUSE=http://www.suse.com is a URL Pair; SUSE is the tag and http://www.suse.com is the URL. The URL pair is separated by an "=" sign.
SubmissionThe date the pattern submitted in the SDP Submissions database.
NotesA space in which to keep notes regarding this pattern.