Post-Update Steps in Windchill QMS 12.1.2.9
If you have updated from Windchill Quality Management Solutions (QMS) 12.1.2.x to Windchill (QMS) 12.1.2.9 and would like the complete QMS sample setup, use the following examples to set up your QMS environment.
Example Association Rule
If the following association rules are not available, navigate to > > to create these rules in the Association Rules table. For each rule, specify the Association Type, Role A Type, and Role B Type as mentioned below.
|
Association Type
|
Role A Type
|
Role B Type
|
Cardinality
|
|
Regulatory Submission Subject
|
Adverse Event Regulatory Submission
|
Customer Experience Regulatory Report Decision
|
Many:1
|
|
Regulatory Submission Driver
|
Adverse Event Regulatory Submission
|
Customer Experience
|
1:1
|
|
Regulatory Submission Driver
|
Unique Device Identifier Submission
|
UDI Super Set
|
1:1
|
|
Regulatory Submission Driver
|
Unique Device Identifier Submission
|
UDI Super Set (Revisable)
|
1:1
|
For more information on association rules, see
Association Rules.
Example Workflow Subject Layout
To create the Workflow Subject Layout on the Customer Experience Regulatory Report Decision type, an administrator should complete the following steps:
1. Navigate to > > .
2. Click Customer Experience Regulatory Report Decision.
3. In the Actions menu, click Edit.
4. In the Layouts tab, click Create New Layout.
5. Specify Workflow Subject Layout as the name and Information Page - Workflow Task Attributes as the Screen Type.
6. Click OK.
7. Specify the same attribute groups as in the Primary Attributes Info Page Layout.
8. Click Done.
Example OIRs
If OIRs are defined for the following types, update the respective OIR files:
• Regulatory Submission
• Customer Experience Regulatory Report Decision
• Regulatory Submission (Revisable)
• Adverse Event Regulatory Submission
To update the OIR files, complete the following steps:
1. Navigate to > >
2. Download the OIR files.
3. Update the OIR files as mentioned below:
◦ In the OIR for the Regulatory Submission type, update the attribute value of lifecycle.id to Regulatory Submission via Approval Life Cycle Version 1, and the attribute value of teamTemplate.id to Regulatory Submission Team.
◦ In the OIR for the Customer Experience Regulatory Report Decision type, update the attribute value of lifecycle.id to Customer Experience Regulatory Decision Version 4, and remove information about the state.state attribute value.
◦ In the OIR for the Regulatory Submission (Revisable) type, update the attribute value of lifecycle.id to Regulatory Submission via Change Life Cycle Version 2, and the attribute value of teamTemplate.id to Regulatory Submission Team.
◦ In the OIR for the Adverse Event Regulatory Submission type, update the attribute value of lifecycle.id to Regulatory Submission via Approval Life Cycle Version 1, and the attribute value of teamTemplate.id to Regulatory Submission Team.
4. Save and upload the modified OIR files to the same location.
For more information on working with OIRs, see
Understanding Object Initialization Rules.
If OIRs are not defined for the OIR Types mentioned above, execute the command windchill wt.load.LoadFromFile -d <Directory>/<Name of the file> in a Windchill shell to manually add the OIR files from their directories:
• loadFiles/regmstr/RegulatorySubmission_InitRule.xml
• loadFiles/cem/CERegulatoryReportDecision_InitRule.xml
• loadFiles/regmstr/RegSubmission2_InitRule.xml
• loadFiles/regmstr/AERRegSubmission2_InitRule.xml
Example Category Tree Constraint
You can use the category tree for a
Customer Experience Regulatory Report Decision type as a constraint on an attribute. For more information, see
Using Category Tree as a Constraint on an Attribute.