Data Management Capabilities > Managing Change > Change Management Administration > Administration of Problem Reports and Variances in Projects
Administration of Problem Reports and Variances in Projects
An organization can extend the change management process for problem reports and variances to members of a project. For example, if an object in a product is shared to a project, members of the project can create and edit problem reports and variances for that object.
The host organization creates a project to be used as a repository for these objects.
Preferences
There are two preferences, found in the Change Management category of the Preference Management utility, that enable using problem reports and variances in projects. They are:
• Problem Reports in Projects
• Variances in Projects
The preferences can be set at the site, organization, or project level.
Object Initialization Rule (OIR)
The OIR defines rules on the object type at the each context level. Such rules stipulate whether the value of an attribute is assigned by the server or if it is entered by the user. For problem reports and variances in projects, the attributes of interest include the following:
• Number
• Folder location
• Life cycle
• Team template
Use the OIR to manage these attributes. When rules are defined, ensure that rules defined for projects do not interfere with rules defined for products and libraries.
Project Team Roles
The project manager should add team roles to the project team based on the roles needed by the life cycle and workflow process templates to be assigned to the change objects in projects. If you are using the workflows in Windchill PDMLink, Change Administrator I is needed for problem reports in projects and Variance Approver is needed for variances in projects.
See Adding Roles for information about adding roles to the team.
Custom Numbering Schemes
By default, the number attribute is auto-generated for change objects. You can change that by using the OIR for the problem report or variance to allow the number to be manually entered. Other configurations could be used, as supported by Windchill. For more information, see Object Numbering.
Basic Access Policies for the Project
The minimal policies that are required to successfully create, edit, and view problem reports and variances in projects include the following:
Context
Object Type
State
Participant
Permissions
Project
WTChangeIssue
All
Project Creator
+
Full Control(All)
Project
WTChangeIssue
All
Team Members
+
Read,Download
Project
WTChangeIssue
Open
Team Members
+
Create,Modify,Modify Content
Project
WTChangeIssue
All
Change Administrator I
+
Full Control(All)
Project
WTVariance
All
Project Creator
+
Full Control(All)
Project
WTVariance
All
Team Members
+
Read,Download
Project
WTVariance
Open
Team Members
+
Create,Modify,Modify Content
Project
WTVariance
Under Review
Variance Approvers
+
Read,Download
Project
WTVariance
All
Change Administrator I
+
Full Control(All)
Optional policies recommended for problem reports and variances in projects include the following:
Context
Object Type
State
Participant
Permissions
Project
WTChangeIssue and WTVariance
All
Organization Administrator
+
Full Control(All)
Project
WTChangeIssue and WTVariance
All
Guest
+
Read
Project
WTChangeIssue and WTVariance
All
Site Administrator
+
Full Control(All)
Project Folders
By default, the folder location is auto-generated for change objects. When new change objects in projects are created, they are saved in the root folder of the project.
Use the Object Initialization Rules Administrator to change the default.
Project Template
An organization can choose to configure suitable rules and policies that meet their business needs using a project template. For more information, see About Context Templates
Isto foi útil?