The General subscreen is where many of the most important standard fields on a Business Task are maintained.
Some of these values that you populate in these fields may drive some of the workflow and processes within your organisation’s ActiveControl setup.
Figure: General subscreen in the Business Task
| Field | Description |
|---|---|
| Reference | Unique identifier for the Business Task, in most Customers it will be the ticket number (eg Jira or ServiceNow etc). |
| Subject | Summary description of the Business Task. |
| Project | The Project to which a particular Business Task is linked. |
| Type | Typically used to present values such as “Incident”, “Change Request”, Project Change” etc. |
| Group | Typically used to reflect the SAP Modules or similar business groupings within an Organisation. |
| Priority | Typically used to indicate its urgency (eg Critical, High, Normal, Low). |
| Deployment Status | Automatically calculated for a Business Task, based on the location of the underlying Transport Forms in the workflow. |
| Planning Status | Optional field. Can be used to present a pre-Development status of a particular Business Task (eg Approved versus Not Approved). This field may be hidden in your local installation of ActiveControl. |
| Requirement Description | Long description of the Busines Task. |
| Custom Fields | Optional fields configured within your local installation of ActiveControl, to allow other data not available as part of the standard fields to be stored. |
Mandatory field are indicated by a red asterisk * on the screen.
Some of the fields are dropdown fields, the meta-data behind these is defined and configured for your own organisation by your local ActiveControl Administrator
Post your comment on this topic.