Viewing Summary Reports
Summary reports are available in the Attachments tab of the package.
To access this tab,
1. In the Object Collector or Context Collector page of your package, add a new tab.
2. Click the Customize menu in the upper-right corner.
3. Select > .
The following image illustrates the objects added to the package and marked as Locked for Replication.
• the part Bolt is checked out
• the part Nut is the common affected object for ChangeTask001 and ChangeRequest005
• Actuator_Baseline is managed baseline
• the part Left_Actuator is parent of Left_Arm and is also associated with the document Doc1
Generated Reports
The reports generated are listed below:
Summary_Dependency_Chain
Displays a chain of objects that are dependent on those selected and marked as Locked for Replication. Only objects configured to be collected as dependents are listed.
For more information, see Dependent Objects Included in Replication Locks.
Column Breakdown:
• Column 1 - Identity of the selected object
• Column 2 - Identity of its dependent
• Column 3 - Identity of the object dependent on the second column, and so on.
Row Highlights:
• Rows 2 to 6: Dependents of Change Request – 00002 are collected. The first row captures the master of the change request, followed by different versions of the affected object - Nut A.1 and A.2. Additionally, Change Task – 00023 is collected because Nut serves as a common affected object for both the change task and the change request.
• Rows 7 to 9: The affected object Nut, the associated change notice, and the master are collected as dependents of Change Task 00023.
• Row 10: Only the master is collected as a dependent for Change Notice 00023.
• Rows 11 to 17: Different versions of selected parts are collected with their master.
• Row 18: Bolt is checked out, so it’s working copy identity is displayed as Secured Information.
• Row 19: Master of the selected document is collected.
• Row 20: Although Managed Baseline is listed in the report, it will not be locked for replication. Unsupported objects are detailed in Summary_ExcludedObjects report.
Summary_Objects_ToBe_Marked
Lists objects marked as Locked for Replication, along with their identity and context path.
The report identifies the listed parts, change task, change notice, change request, document, and the working copy of the checked-out part Bolt as objects that will be marked as Locked for Replication.
Summary_ToBe_Deleted_Links
This report outlines the links scheduled for deletion following replication.
The change task is an exception and will be removed from the target system during the import process.
The report includes details such as the identity of the selected object, the type of link, the Role A and Role B objects associated with the link, and the dependent object.
Links identified as eligible for deletion include: Object History, Part Describe Link, Implemented By, Affected Activity Data, Relevant Request Data, Checkout Link, Part Usage, and Holder To Content.
Summary_ExcludedObjects
Lists objects that are either not eligible to be marked as Locked for Replication or are not supported for replication. The report also includes objects that have already been replicated. Each entry displays the object's identity and the context path indicating its location.
The Managed Baseline appears in the report as it is not supported for being marked as Locked for Replication.
Summary_Open_Workflows
Lists objects that are eligible to be marked as Locked for Replication but currently have active workflow processes. These workflows are terminated before the replication lock is applied, following an approval vote. If the package is rejected, the workflows remain active. The report displays the identity of each object along with its associated running processes. In the provided report, workflows for the change request, change task, and change notice are shown as active for their respective change objects.
Summary_Violators
Lists objects that prevent the in-transit lock from being applied. Violations occur when an object intended to be marked as Locked for Replication is either checked out, exists as a working copy, or falls into one of the following categories:
• Reserved working copy: The object is checked out in Creo.
• Private working copy: A private copy of the object is modified and uploaded to the database without being checked out in Creo.
• Workspace only: The object is created in Creo, but not uploaded to Windchill.
• Checked out to sandbox: The object is checked out from PDM to a project.
• Terminal iteration: The object that is checked out to a project is sent back to PDM.
• One-off Version: The object is created as a one-off version, which will not be reflected in the main version sequence. Checking out an object to a project also creates a one-off version.
When violations are detected, a rework task is generated, and the routing process is set to Rework. These issues must be resolved before re-routing the package for dependency review.
The report displays the identity of each violating object along with TRUE or FALSE values for the categories listed above. In the provided report, Bolt is flagged as checked out.
 | • The Copy delivery information checkbox in the Revise dialog box does not function for Object Collector or Context Collector packages. Selecting the checkbox does not transfer delivery information to the new package revision. • To access the contents and summary reports generated for a Context Collector package, users assigned the Package Approver role must be members of both the Replication Package Administrators group and the Replication Authority group. |