Differences

This shows you the differences between two versions of the page.

--- reports:start [2025/11/20 20:43] – [Unresolved Process Interfaces] Fryer, Kathryn
+++ reports:start [2025/11/26 15:37] (current) – [Unresolved Process Interfaces] Fryer, Kathryn
@@ Line 5: / Line 5: @@
 ===== Association Overview =====
-For all elements of the selected type, the report lists their associations to other elements in the same or different workspace.  It also identifies elements of the selected type that have no associations.
+For all elements of the selected source element type, the report lists their associations to other elements in the same or different workspace.  It also identifies elements of the selected type that have no associations. The report excludes sequence associations (Predecessor and Successor relationships) between Workflows and Activities and between Value Stream Steps.
 **Purpose**: Verify element associations within context of overall process. Identify elements with no associations that require integration or might be unused.
-PLEASE NOTE: This report runs on Stages V7.11.8 and above.  For earlier versions, please contact your Stages consultant or Stages Support.  Earlier versions of this report (prior to V7.11.5) were limited to Excel output and 100 elements.
+**PLEASE NOTE**: This report runs on Stages V7.11.8 and above.  For earlier versions, please contact your Stages consultant or Stages Support.  Earlier versions of this report (prior to V7.11.5) were limited to Excel output and 100 elements.
 [[https://download.stages.digital/stages/Standard_Reports/AssociationOverview.zip|Download]]  Available since: Stages V7.11.5 (previous report since V7.5) (Updated 2025-11-06; Build 6179; [[reports:change-history#association-overview|Change History]])
 ===== Comments Analysis =====
-This report shows all comments added to process elements in the current workspace and optionally its subworkspaces.
+This report shows all comments added to process elements in the current workspace and optionally its subworkspaces. The report lists comments grouped by workspace, process element type, and element. Information for each comment includes creator, creation date, when it was last changed, and by whom.
-**Purpose**: Analysis of user or reviewer feedback on the process.
+**Purpose**: Analysis of user or reviewer feedback on the process. Review the comments to identify feedback and requested changes for the process elements.
 [[https://download.stages.digital/stages/Standard_Reports/CommentsAnalysis.zip|Download]]  Available since: Stages V7.5 (Updated 2025-09-15; Build: 6014; [[reports:change-history#comments-analysis|Change History]])
 ===== Compliance Overview =====
-**This report has to be executed from a reference-model workspace!**
+**You must run this report from a reference-model workspace!**
-This report gives an overview of compliance traceability for a reference model from all processes in Stages.\\  The report shows the reference model requirements and processes that map to them, with the number of elements in the process and compliance rating.
+This report gives an overview of compliance traceability for a reference model from all processes in Stages. You must run this report from a reference model workspace. The reference model must have at least one defined scope. The report shows the reference model requirements and processes that map to them, with the number of elements in the process and compliance rating.
 **Purpose**: Understand how your processes comply with the reference model requirements. Identify gaps in coverage and compliance. You can also identify where elements have been mapped, but no compliance rating has been assigned.
 [[https://download.stages.digital/stages/Standard_Reports/ComplianceOverview.zip|Download]]  Available since: Stages V7.7 (Updated 2025-11-19; Build: 6227; [[reports:change-history#compliance-overview|Change History]])
 ===== Compliance Traces - Process Perspective =====
-For the current process version this report shows the mapping from process elements to regulatory requirements in reference models to indicate compliance.\\  You must run this report from a process workspace (not from the reference model).
+For the current process version this report shows the mapping from process elements to regulatory requirements in reference models to indicate compliance. You must run this report from a process workspace (not from the reference model) and select one or more reference model scopes defined for this process. The report excludes elements that have been tailored out of the process.
-**Purpose**: Understand how your processes comply with the reference model requirements. Identify gaps in coverage and compliance.
+**Purpose**: Understand how your processes comply with the reference model requirements. Identify gaps in coverage and compliance. You can also identify where elements have been mapped, but no compliance rating has been assigned.
-PLEASE NOTE: This report runs on Stages V7.11.8 and above.  For earlier versions, please contact your Stages consultant or Stages Support.
+**PLEASE NOTE**: This report runs on Stages V7.11.8 and above.  For earlier versions, please contact your Stages consultant or Stages Support.
 [[https://download.stages.digital/stages/Standard_Reports/ComplianceTraces.zip|Download]]  Available since: Stages V7.1 (Updated 2025-11-10; Build: 6195; [[reports:change-history#compliance-traces-process-perspective|Change History]])
 ===== File List =====
@@ Line 53: / Line 57: @@
 This report lists all guidance elements in the selected version of the process workspace, including any files provided for the element. Set the Guidance Type parameter to limit results to a specific subtype of guidance element.
-**Purpose**: Review all available guidance for the process without having to navigate through the process.You can also verify that the correct files and file versions are provided for the guidance elements, or identify elements that are missing files.
+**Purpose**: Review all available guidance for the process without having to navigate through the process. You can also verify that the correct files and file versions are provided for the guidance elements, or identify elements that are missing files.
-PLEASE NOTE: This report runs on Stages V7.11.8 and above.  For earlier versions, please contact your Stages consultant or Stages Support.
+**PLEASE NOTE**: This report runs on Stages V7.11.8 and above.  For earlier versions, please contact your Stages consultant or Stages Support.
 [[https://download.stages.digital/stages/Standard_Reports/GuidanceOverview.zip|Download]]  Available since: Stages V7.5 (Updated: 2025-11-06 Build: 6180; [[reports:change-history#guidance-overview|Change History]])
 ===== License Usage =====
-This report shows how many licenses of each type were used during the selected timeframe.
+This report shows how many licenses of each type were used during the selected timeframe. The report generates a scatter chart with the X-axis showing dates on the timeline and the Y-axis showing the peak number of licenses used at that time.
 **Purpose**: Understand overall system usage, usage trends, and license demands.
-Note: This report runs on Stages 7.11.6.1 and higher. For earlier Stages versions, please contact your Stages consultant or Stages Support.
+**PLEASE NOTE**: This report runs on Stages 7.11.6.1 and higher. For earlier Stages versions, please contact your Stages consultant or Stages Support.
 [[https://download.stages.digital/stages/Standard_Reports/LicenseUsage.zip|Download]]  Available since: Stages V7.1  (Updated 2025-08-26; Build 5886; [[reports:change-history#license-usage|Change History]])
 ===== Local Elements =====
-This report lists elements created locally or overwritten in this workspace, as well as locally created associations for the current version of the workspace.
+This report lists elements created locally or overwritten in this workspace, as well as associations created locally (meaning they were not imported with process modules).
-**Purpose**: Use this report in integrated and instantiated workspaces to understand any changes made directly in the workspace and how the workspace content varies from the original process content.
+**Purpose**: Use this report in integrated and instantiated workspaces to understand any changes made directly in the workspace and how the workspace content varies from the original process content. When updating content from modules, identify overwritten elements that require manual update.
-PLEASE NOTE: The current version of this report requires Stages 7.11.5 or later. For earlier versions, please contact your Stages consultant or Stages Support.
+**PLEASE NOTE**: The current version of this report requires Stages 7.11.5 or later. For earlier versions, please contact your Stages consultant or Stages Support.
  [[https://download.stages.digital/stages/Standard_Reports/Local_Elements.zip|Download]]  Available since: Stages V7.5 (Updated 2025-11-06; Build: 6176; [[reports:change-history#local-elements|Change History]])
 ===== MS Project Export with Phases =====
@@ Line 85: / Line 92: @@
 **Purpose**: Export process information from Stages and import the process into a project planning tool for execution and tracking.
-PLEASE NOTE: This report runs on Stages V7.11.8 and above.  For earlier versions, please contact your Stages consultant or Stages Support.
+**PLEASE NOTE**: This report runs on Stages V7.11.8 and above.  For earlier versions, please contact your Stages consultant or Stages Support.
 [[https://download.stages.digital/stages/Standard_Reports/MSProjectExportWithPhases.zip|Download ]] Available since: Stages V7.5 (Updated 2025-11-06; Build: 6182; [[reports:change-history#ms-project-export-with-phases|Change History]])
 ===== Process Changes =====
@@ Line 99: / Line 107: @@
 ===== Process Interfaces =====
-This report lists all associations to other workspaces from the current version of the workspace. Interfaces are grouped by target workspace.
+This report lists all interfaces to other workspaces from the current version of the workspace. Interfaces are grouped by target workspace. The report shows and resolves interfaces as Stages does:
+  * When run against the working version of a process, interfaces resolve to the working version of the target process.
+  * When run against the valid version, interfaces resolve to the valid version of the target.
+  * When run against any other process version, if that version has ever been valid, interfaces resolve to the valid version of the target. If that version has never been valid, interfaces resolve to the working version.
 **Purpose**: Understand the dependencies between workspaces as well as what interfaces are available. To avoid missing associations, these workspaces should be released together.
-PLEASE NOTE: The current version of this report requires Stages 7.11 or later. For earlier versions, please contact your Stages consultant or Stages Support,
+**PLEASE NOTE**: The current version of this report requires Stages 7.11 or later. For earlier versions, please contact your Stages consultant or Stages Support,
  [[https://download.stages.digital/stages/Standard_Reports/ProcessInterfaces.zip|Download]] Available since: Stages V7.5 (Updated 2025-09-19; Build 6031; [[reports:change-history#process-interfaces|Change History]])
 ===== Process Version Usage =====
@@ Line 111: / Line 124: @@
 This report shows all the process modules used by the current process, or all of the processes using the current process module. The report recurses through up to 4 levels of module usage and includes versions for each process and module.
-**Purpose**: Overview for the Process Architect which modules are integrated. Use the version information to identify where you might need to update modules to the current valid version.
+**Purpose**: Analyze how process module versions are used across different process versions to understand reuse, patterns, and impacts of module changes. Use the version information to identify where you might need to update modules to the current valid version.
 [[https://download.stages.digital/stages/Standard_Reports/ProcessVersionUsage.zip|Download]]  (Updated: 2025-09-19; Build: 6035; [[reports:change-history#process-version-usage|Change History]])
 ===== Project Plan Export =====
@@ Line 129: / Line 143: @@
 **Purpose**: Use this report for project-specific process instances to understand who is involved in the project and in what capacity. You can also identify roles where no user is assigned.
-PLEASE NOTE: This report runs on Stages V7.11.8 and above. For earlier versions, please contact your Stages consultant or Stages Support.
+**PLEASE NOTE**: This report runs on Stages V7.11.8 and above. For earlier versions, please contact your Stages consultant or Stages Support.
 [[https://download.stages.digital/stages/Standard_Reports/RoleUserAssignment.zip|Download]]  Available since: Stages V7.5 (Updated 2025-11-06; Build: 6181; [[reports:change-history#role-user-assignments|Change History]])
@@ Line 155: / Line 169: @@
 ===== Unresolved Process Interfaces =====
-This report lists all interfaces to other workspaces from the Working Version and Valid Version of the current workspace. Interfaces are grouped by target workspace.
+This report lists all interfaces to other workspaces from the Working Version and Valid Version of the current workspace, identifies whether they resolve in both versions, and if not, the release status in both current and target workspace. Interfaces are grouped by target workspace.
+A red "N" in the Valid Version column indicates the interface is not available in the Valid Version. A red "N" in the Working Version column indicates a previously released interface has been removed in the Working Version and the change has not been released to the Valid Version.
+Both current and target workspaces must release interfaces in a Valid Version for interfaces to resolve.
-**Purpose**: Understand dependencies between workspaces, including what interfaces are released in the Valid Version. Identify unreleased interfaces and which target workspaces must be released to resolve those interfaces.
+**Purpose**: Understand dependencies between workspaces, including what interfaces are released in the Valid Version. Identify unreleased interfaces and which workspaces must be released to resolve those interfaces. To focus only on the unreleased interfaces, set the Show Only Missing Associations parameter. You can then investigate and take action to release those interfaces.
-PLEASE NOTE: This report runs on Stages V7.11.8 and above. For earlier versions, please contact your Stages consultant or Stages Support.
+**PLEASE NOTE**: This report runs on Stages V7.11.8 and above. For earlier versions, please contact your Stages consultant or Stages Support.
- [[https://download.stages.digital/stages/Standard_Reports/UnresolvedProcessInterfaces.zip|Download]]  Available since: Stages V7.10 (Updated 2025-11-06; Build: 6183; [[reports:change-history#unresolved-process-interfaces|Change History]])
+ [[https://download.stages.digital/stages/Standard_Reports/UnresolvedProcessInterfaces.zip|Download]]  Available since: Stages V7.10 (Updated 2025-11-26; Build: 6268; [[reports:change-history#unresolved-process-interfaces|Change History]])