General (change form)

The General page provides the basic information about the change form: its name, its identifier number, its lifecycle state, who originated it and when, and descriptive information.

Change type (Executing/Advisory) §

The Type defines the change form's properties such as numbering, workflow, participants, effect on items listed in its Affected list, etc. These are controlled by its Change Forms collection member. The type shows that it is an Executing or Advisory change form.

The class icon shows the current change lifecycle:

• Originated
• Submitted to analyst
• Routed for approval
• Held awaiting more information
• Stopped after disapproval, wait for an analyst to select the next step
• Accepted, and waiting for analyst final review
• Released. All reviewers approved the change. The analyst completes the change.
• Completed. The affected items are dispositioned.
• Canceled, after a reviewer disapproved. The analyst deletes the change.
• Rejected, after a reviewer disapproved. The change form is kept permanently.

The Type cannot be edited.

Number §

The number, with the Type above, uniquely identifies the change within PDXpert. In most cases, this value is automatically given based on the Change Forms member's Identifier sequence selection.

Problem source §

If the change is the result of a problem that was found in an existing item, you can identify how or where that problem was discovered based on the Problem Sources collection.

Originator (Trustee) §

This is the person with overall responsibility for the change form's contents. The originator can edit various fields, build the Affected list, submit the change to an analyst, and designate a new originator.

Analyst §

This person manages the change after the originator has finished. When the change is in the Submitted state, the analyst can modify any of the trustee's work, add or remove file attachments, and route the change to the reviewing groups. The analyst may separately receive workflow notices.

Other analysts cannot modify the change or its file attachments. However, they may set the change workflow (for example, move the change from Routed to Submitted), and can replace the analyst with a different analyst, including themselves.

Change reason §

This selection categorizes why the change form is necessary, and is selected from the Change Reasons collection.

Change lifecycle §

Changes are given a lifecycle state based on their progress through your organization's workflow. This state can be changed only by using the workflow specified in its Change Forms collection member.

Origination date §

The date when this change form was made.

Release date §

The date when this change form's lifecycle was set to Released. All items on the Affected list of an executing change form are given this date for their own released/canceled dates.

Product families §

Product families are automatically added as you add items to the change's Affected list. The change form's product families list is obtained from each affected item's product families. The list cannot be edited, but will be recalculated if you change an affected item's product families.

This field is shown if any Affected items have been assigned product families, or the change has not been Routed.

Change description §

Gives the change form's purpose and expected results. The label may be different to reflect the particular change form, such as Request proposal or Deviation description.

1091