|
|
Application RequirementsRecords can be created in various ways. You can add a brand new record to your application or copy an existing one. Existing rules can be specialized by creating a copy into a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. Data instances may be copied but do not support specialization as they are not versioned.
Based on your use case, the Create, Save As or Specialization form is used to create the record. The number of fields and available options vary by record type. Start by familiarizing yourself with the generic layout of these forms and their common fields:
This help topic then identifies the key parts and options that are applicable to the record type you are creating.
Create an Application Requirement rule by selecting Application Requirement from the Application Definition category.
Key parts:
An Application Requirement rule has two key parts:
Field |
Description |
|
Application Name |
Select an Application. Requirements are directly associated with an existing application but cannot be applied to a class. |
|
Requirement ID |
Enter an identifier of your choice for this requirement. Begin the identifier with a letter and use only alphanumeric, ampersand, underscore, and dash characters. Typically, the identifier starts with the same letter as the work item prefix, followed by a numeric, and then a short description. For example, if the work item prefix is |
NOTE: If you have selected the Auto Increment option on the current Application rule form's Requirements tab, the system automatically generates a unique identifier (prefix and integer) for the Requirement ID key part. The Short Description field appears instead of the Requirement ID field. Enter text used for the rule's Description label. See Application form - Working with the Requirements tab.
Rule resolution
Rule resolution does not apply to this rule type.
About Application Requirements