Update the COTS workflow templates using the PSP-derive-problem-solving-items workflow handler

Description

A user would be able to update the COTS workflow templates using the PSP-derive-problem-solving-items workflow handler to automate deriving a change request from a problem report, or a change notice from a change request.

The workflow handler provides additional arguments to derive multiple changes based on the number of secondary objects. If the action handler passes all the validations, then the action handler will derive multiple changes corresponding to each secondary object.

Setting auto_derive to true will automatically derive the proper result when submitted using the default workflow template.

Syntax

PSP-derive-problem-solving-items [-from_type=]

[-to_type=]

[-synopsis=]

[-description=]

[-template=]

[-propagate_secondary_as=]

[-source_property_name=]

[-source_property_value=]

[-source_relation=]

[-target_relation=]

[-description_from_secondary=]

[-synopsis_from_secondary=]

Arguments

-from_type

Target object type to derive from. Derive will derive from all workflow targets of this type, or subtypes of this.

-to_type

The change object type to be created by the Derive operation. Must be a valid change type that can implement the designated –from_type.

-synopsis

Synopsis to be assigned to the created change object.

-description

Description to be assigned to the created change object.

-template

Name of the workflow template the newly created change object should be submitted to. Or, if empty, then use the default workflow template configured for this newly created change type. Note If this argument is not provided, then the newly create change object will not be submitted to a workflow.

-propagate_secondary_as

Type of propagation being done to the secondary object when it is being propagated from the source change item (from_type) to the derived change item (to_type). Valid values are Carryover and Duplicate. All other values are invalid. When Carryover is specified, the object is propagated from the source change item to the derived change item as a reference. The same object is attached to the derived change item with the relation specified in the Argument list. When Duplicate is specified, the object is propagated from the source change item to the derived change item as an object. The existing object is saved as a new object, and the new object is attached to the derived change item with the relation specified in the Argument list.

-source_relation

Valid relation name to get the secondary objects from the source target object. If no secondary object is found, the action handler derives the change item only once. It does not propagate a secondary object with this relation to the target relation. An invalid relation name generates an error. If this argument is used with a valid relation name, the -target_relation argument is required with a valid relation name.

-target_relation

Valid relation name to attach the object to the new derived object. An invalid relation name generates an error. This argument must be used with -source_relation.

-source_property_name

Property name to read from the secondary objects for validation. If this argument is used, source_property_value is required too. This argument is optional.

-source_property_value

Value should match the value from secondary object’s property value. If the validation is false, the change object not derived for the corresponding secondary object. An empty value is valid. This argument must be used with - source_property_name.

-description_from_secondary

Description to be sourced from the secondary object’s description. This argument takes precedence over the -description argument. An empty value is valid.

-synopsis_from_secondary

Synopsis to be sourced from the secondary object’s synopsis. This argument takes precedence over the -synopsis argument. An empty value is valid.

Placement

Place on any action. Typically attached to the Complete action.

Restrictions

None.

Examples

• This example derives a Problem Solving object from a Quality Issue object only once, without propagating any secondary objects.

Argument

Values

-to_type

C2CapaRevision

-from_type

C2IssueRevision

• This example generates an error because a value is not specified for the -propagate_secondary_as argument.

Argument

Values

-to_type

C2CapaRevision

-from_type

C2IssueRevision

-propagate_secondary_as

• This example generates an error because the -source_relation and -target_relation arguments are not specified.

Argument

Values

-to_type

C2CapaRevision

-from_type

C2IssueRevision

-propagate_secondary_as

Carryover

• This example generates an error because values are not specified for the -source_relation and -target_relation arguments.

Argument

Values

-to_type

C2CapaRevision

-from_type

C2IssueRevision

-propagate_secondary_as

Carryover

-source_relation

-target_relation

• This example generates an error because invalid relation names are specified for the -source_relation and -target_relation arguments.

Argument

Values

-to_type

C2CapaRevision

-from_type

C2IssueRevision

-propagate_secondary_as

Carryover

-source_relation

Invalid relation name

-target_relation

Invalid relation name

• This example derives a Problem Solving object from a Quality Issue object for each source secondary object from the source relation. If there are two source secondary objects, the Problem Solving object is derived twice from the Quality Issue object. The action handler propagates each secondary source object from the source Quality Issue to the target derived Problem Solving object with the specified target relation.

Argument

Values

-to_type

C2CapaRevision

-from_type

C2IssueRevision

-propagate_secondary_as

Carryover

-source_relation

CPA0SymptomDescription

-target_relation

CPA0ProblemDescription

• This example generates an error because a value is not specified for the -source_property_name argument.

Argument

Values

-to_type

C2CapaRevision

-from_type

C2IssueRevision

-propagate_secondary_as

Carryover

-source_relation

CPA0SymptomDescription

-target_relation

CPA0ProblemDescription

-source_property_name

• This example generates an error because the -source_property_value argument is not specified. This argument is required with the -source_property_name argument.

Argument

Values

-to_type

C2CapaRevision

-from_type

C2IssueRevision

-propagate_secondary_as

Carryover

-source_relation

CPA0SymptomDescription

-target_relation

CPA0ProblemDescription

-source_property_name

caw0Evaluation

• This example derives a Problem Solving object from a Quality Issue object for each source secondary object from the source relation. If there are two source secondary objects, before deriving, the action handler validates that caw0Evaluation of the secondary object has an empty value. If it has an empty value, the Problem Solving object is derived from the Quality Issue object. If it does not have an empty value, the Problem Solving object is not derived from the Quality Issue object for the secondary object.

Argument

Values

-to_type

C2CapaRevision

-from_type

C2IssueRevision

-propagate_secondary_as

Carryover

-source_relation

CPA0SymptomDescription

-target_relation

CPA0ProblemDescription

-source_property_name

caw0Evaluation

-source_property_value

• This example derives a Problem Solving object from a Quality Issue object for each source secondary object from the source relation. If there are two source secondary objects, before deriving, the action handler validates that caw0Evaluation of the secondary object is Investigating. If it is Investigating, the Problem Solving object is derived from the Quality Issue object. If it is not Investigating, the Problem Solving object is not derived from the Quality Issue object for the secondary object.

Argument

Values

-to_type

C2CapaRevision

-from_type

C2IssueRevision

-propagate_secondary_as

Carryover

-source_relation

CPA0SymptomDescription

-target_relation

CPA0ProblemDescription

-source_property_name

caw0Evaluation

-source_property_value

Investigating

• This example derives a Problem Solving object from a Quality Issue object for each source secondary object from the source relation. If there are two source secondary objects, before deriving, the action handler validates that caw0Evaluation of the secondary object is Investigating. If it is Investigating, the Problem Solving object is derived from the Quality Issue object. If it is not Investigating, the Problem Solving object is not derived from the Quality Issue object for the secondary object.When you use the description_from_secondary and -synopsis_from_secondary arguments, for each new derived object, the synopsis and description are taken from each secondary object.

Argument

Values

-to_type

C2CapaRevision

-from_type

C2IssueRevision

-propagate_secondary_as

Carryover

-source_relation

CPA0SymptomDescription

-target_relation

CPA0ProblemDescription

-source_property_name

caw0Evaluation

-source_property_value

Investigating

-description_from_secondary

-synopsis_from_secondary