@sabrish/power-platform-solution-blueprint 1.1.0 → 1.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -5,6 +5,39 @@ All notable changes to Power Platform Solution Blueprint will be documented in t
5
5
  The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
6
  and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
 
8
+ ## [1.1.2] - 2026-03-17
9
+
10
+ ### Changed
11
+ - **Cross-Entity Automation chain map redesigned** — trigger operation column added to show the specific operation (`Create`, `Update`, `Delete`) that causes the downstream automation; message code support expanded to handle all response scenario codes
12
+
13
+ ### Fixed
14
+ - **Debug logging removed from production paths** — all `debugLog` calls removed from `FlowDefinitionParser.ts`, `FlowDiscovery.ts`, and `CrossEntityAnalyzer.ts`; conditional debug logger remains available opt-in via `ppsb-debug` localStorage flag for development diagnostics
15
+
16
+ ---
17
+
18
+ ## [1.1.1] - 2026-03-17
19
+
20
+ ### Added
21
+ - **Conditional debug logger** (`src/core/utils/debugLogger.ts`) — lightweight `debugLog(tag, msg, data?)` utility active only in dev server, `http:` origins, or when `localStorage.setItem('ppsb-debug', 'true')` is set; completely silent in production PPTB Desktop installs under `pptb-webview://`
22
+ - **Debug logging for flow scope labelling** — `[PPSB:flow-scope]` diagnostic logs added to `CrossEntityAnalyzer.ts` to surface real-world data for flows appearing as "Solution Flow (unscoped)"; opt-in via `ppsb-debug` localStorage flag
23
+ - **Debug logging for flow parse and discovery** — `[PPSB:flow-parse]` and `[PPSB:flow-discovery]` logs in `FlowDefinitionParser.ts` and `FlowDiscovery.ts`; aid diagnosis of trigger-entity resolution edge cases
24
+
25
+ ### Fixed
26
+ - **Business rules: full IF/THEN/ELSE structure** — `BusinessRuleParser` rewritten to produce `conditionGroups: ConditionGroup[]` (IF/ELSE IF blocks) and `elseActions: Action[]`; `BusinessRulesList` now renders IF / ELSE IF / THEN / ELSE labels correctly; HTML and Markdown exports updated to reflect full rule structure
27
+ - **Business rules: conditionCount in HTML and Markdown reporters** — was reading a stale flat `conditions` array; now correctly derived from `conditionGroups.reduce((sum, g) => sum + g.conditions.length, 0)`
28
+ - **Custom APIs row click conflict** — `onSelectAPI` removed from row `onClick`; clicking a row now only toggles expansion; the select action is no longer triggered on every expand
29
+ - **Environment Variables eye icon layout shift** — added dedicated 32 px grid column for the visibility toggle so the grid no longer reflows when the icon is clicked
30
+ - **CDS Default Solution filter** — `ScopeSelector` predicates extended to include `solution.friendlyname === 'Default Solution'` and `solution.friendlyname === 'CDS Default Solution'` alongside the existing `ismanaged === true` guard
31
+ - **HTML cross-entity export structure** — `HtmlTemplates.ts` updated to use pipeline-first layout (automation nodes at top level, entity children with `← inbound` badges) matching the v1.1.0 UI redesign
32
+ - **Missing `JSX.Element` return types** — explicit return type annotations added to `ResultsDashboard` and `BusinessRulesList` `renderRuleDetails` inner function
33
+
34
+ ### Changed
35
+ - **DRY/SOLID refactoring — shared utilities** — extracted `normalizeGuid`/`normalizeBatch` (`guid.ts`), `extractOwnershipMetadata` (`metadata.ts`), `resolveEntityName` (`entityName.ts`), `buildOrFilter` (`odata.ts`), and `calculateComplexityScore` (`complexity.ts`) from inline duplication across 80+ call-sites
36
+ - **DRY/SOLID refactoring — shared hooks** — `useExpandable` hook extracted; `IDiscoverer<T>` interface implemented on 11 discovery classes; all processors in `src/core/generators/processors/` call `discoverByIds()` via the interface
37
+ - **DRY/SOLID refactoring — component extraction** — `CrossEntityAutomation/` sub-components extracted from `CrossEntityAutomationView.tsx`; `ERDView/` utilities (constants, stylesheet, export, traversal) extracted
38
+
39
+ ---
40
+
8
41
  ## [1.1.0] - 2026-03-12
9
42
 
10
43
  ### Added
@@ -564,6 +597,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
564
597
  - **No Telemetry**: No usage data collected or transmitted
565
598
 
566
599
 
600
+ [1.1.1]: https://github.com/sabrish/power-platform-solution-blueprint/compare/v1.1.0...v1.1.1
567
601
  [1.1.0]: https://github.com/sabrish/power-platform-solution-blueprint/compare/v1.0.1...v1.1.0
568
602
  [1.0.1]: https://github.com/sabrish/power-platform-solution-blueprint/compare/v1.0.0...v1.0.1
569
603
  [1.0.0]: https://github.com/sabrish/power-platform-solution-blueprint/compare/v0.9.0...v1.0.0
package/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  > Complete architectural blueprints for your Power Platform solutions.
4
4
 
5
- ![Version](https://img.shields.io/badge/version-1.1.0-blue)
5
+ ![Version](https://img.shields.io/badge/version-1.1.2-blue)
6
6
  ![Status](https://img.shields.io/badge/status-stable-green)
7
7
 
8
8
  Generate comprehensive technical documentation for Dataverse and Power Platform solutions with automated discovery, analysis, and export capabilities.