0.2.2

Report library

Core adds a standalone Report library that reuses the authorized Resource Composition contract. Reports retain immutable definition revisions and can be shared without granting source-resource access; Dashboard placements pin an explicit report revision, while existing data-widget placements remain compatible snapshots. Schema-v4 compositions add typed expressions, nested filters, conditional measures, having, comparison, sorting, bounded limits, and exact pivot rollups. Revision-bound CSV, XLSX, and PDF exports and owner-managed schedules recheck current access. Update integrations that persist Dashboard composition nodes to preserve reportRef when present.

This Report library requires App SDK 0.2.2. Its revisions, sharing, exports, schedules, and export-expiry records are created through the normal tenant migration path; do not create those tables manually.

Fixed

• API error messages and boolean labels now use the localized catalogs; Core adopts Time & Absence 0.2.3 with lexically sorted locale files.
• Report exports retry one transient composition query timeout before failing, while preserving a terminal timeout as its diagnostic result.
• Report authoring previews keep chart titles and metadata, and report tables, charts, pivots, and exploration filters show source labels instead of raw enum or reference values.
• Saving or restoring a report revision refreshes its open revision history without requiring a browser reload.
• Dashboard placements retain their chosen saved Report target.
• A newly saved Dashboard stays available after its initial save, a page reload, or reopening its Work Tab.
• Report authoring now offers pivot and gauge when the saved source has the required capabilities.

Developers changelog publication

Developers now renders Core and adopted App SDK release notes from their canonical changelog sources, with localized release lists, product filtering, and release detail pages.

At release finalization, publish matching English and Korean versioned records with the release metadata required by the changelog policy.

Finance App portfolio

Finance now has eight separate App baselines: General Ledger, Asset Accounting, Expenses, Receivables, Payables, Treasury, Controlling, and Financial Planning. They expose only their generated overview and package metadata; domain business functions are not implemented. General Ledger, Asset Accounting, Controlling, and Financial Planning are marked beta; the other four retain available readiness.

General Ledger is required by the other seven Finance Apps. Existing tenants must install and initialize it before those Apps become operational. Budget & Controlling is removed from the selected package graph; existing Central and tenant records are retained without automatic reassignment. Its remote repository remains archived for older Core locks. A database reset is not run automatically.

The initial beta tags remain available for historical locks. Core selects 0.2.1-beta.1 for the four beta Apps; Expenses, Receivables, Payables, and Treasury retain stable 0.3.0 releases. The SDK requirement is unchanged. Package loading does not publish a Central catalog entry: operators reconcile package metadata and explicitly approve new offerings through Central policy.

Tenant signup recommendations

Industry selection again recommends a Central-administered starting App set. The signup catalog removes any recommendation that is not currently public, published, code-loaded, and installable, including Apps with an unavailable prerequisite. Operators configure recommendation industries on each catalog entry; initial official catalog seeding supplies the starting policy without overwriting an existing choice. The Central App Catalog now shows App family and defaults to the same family and launcher order used by Shell surfaces.