Production Release Notes – PFTAD (AN_PFTADN_V4)

Adds Full CRUD Support for Coverage Entities

What’s New

You can now create, read, update, and delete Coverage entities through the API. Additional actions include status updates, as well as lock and unlock controls to manage editability. The system also supports both manual and scheduled synchronization with external data sources to keep coverage data current.

Why It Matters

You no longer need separate workflows or tools to manage coverage data. You can now fully manage Coverage entities programmatically and keep them in sync automatically, reducing manual overhead and data inconsistencies.

Adds Full CRUD Support for Policy Entities

What’s New

The API now supports full lifecycle management for Policy entities, including create, read, update, and delete operations. It also introduces manual and scheduled synchronization with external policy data sources to ensure records remain up to date.

Why It Matters

You can now manage policies entirely through the API without relying on external processes. Automated sync ensures your policy data stays consistent across systems with minimal effort.

Introduces Admin Portal Data Sync Framework

What’s New

A new data synchronization framework is implemented in the Admin Portal UI. This enables direct interaction with backend entity APIs such as Program, Carrier, Coverage, General Agent, and Broker management.

Why It Matters

You can now trigger and manage data sync operations directly from the UI instead of relying solely on backend processes. This improves visibility and control over how data flows between systems.

Updates OpenAPI Specification Across All Modules

What’s New

The OpenAPI (Swagger) documentation is updated across all modules. This includes standardized naming, consolidated program definitions, improved version metadata, and support for manual sync endpoints.

Why It Matters

You now have a more consistent and accurate API contract. This makes integration easier, reduces ambiguity, and ensures your client applications align with the latest API behavior.

Enforces Required and Unique Alias for QuoteConfig

What’s New

The alias field in QuoteConfig is now mandatory for both create and update operations. The system enforces case-insensitive uniqueness, and requests with missing or duplicate values will fail with validation errors.

Why It Matters

You can rely on alias as a stable and unique identifier across configurations. This prevents duplication issues and improves consistency when referencing QuoteConfig records.

Upgrade

1. Ensure all create and update requests include a non-empty alias field.
2. Validate that the alias is unique (case-insensitive) before sending requests.
3. Update any existing records that may not meet the new requirement.

Enforces Required and Unique Alias for CommsConfig

What’s New

The alias field in CommsConfig is now required for all create and update operations. The API enforces case-insensitive uniqueness and rejects invalid or duplicate values with clear error responses.

Why It Matters

You can now depend on a consistent and unique identifier for communication configurations. This reduces ambiguity and prevents conflicts across records.

Upgrade

1. Update all create and update requests to include the alias field.
2. Ensure alias values are unique across all existing configurations.
3. Handle validation errors for missing or duplicate aliases in your integration logic.

Release Date: UAT Mar 26, 2026

Release Status: Deployed to Production

This release bundle primarily consists of premium finance development for the coverage, policy, and data sync between IPFS and anddone system using the admin portal.

PFTAD | Coverage Management (Entity API) [AN- 28221]

Introduced full CRUD support for Coverage entities (create, update, status update, lock/unlock, delete).
Added manual and scheduled (cron) sync with Datalink Coverages to keep coverage data up-to-date.

Client facing impact: No

PFTAD | Policy Management (Entity API) [AN-28221] Introduced full CRUD support for policy entities (create, read, update, and delete). Added manual and scheduled (cron) sync with Datalink policy to keep data up-to-date.

Client facing impact: No

PFTAD | Admin Portal – Data Sync [AN-38556]Implemented front-end data sync framework for the Admin Portal
Enables UI integration with new entity-based APIs (Program, Carrier, Coverage, GA, Broker Management).

Client facing impact: Yes

Required PFTAD swagger update for all modules
Updated PFTAD Open API/Swagger specs across all modules, including PF4 → PFTAD renaming, consolidated program definition, added Manual Sync

Client facing impact: No

API, corrected naming, and standardized missing x- version metadata.

[CR] Quote Config – make alias unique and required
Enforced that alias in quote Config is now mandatory for both Create and Update APIs.
Added case-insensitive uniqueness validation for alias ; requests with missing alias return
MISSING_REQUIRED_FIELD and duplicate aliases return DULPICATE_ALIAS .

Client facing impact: No

[CR] CommsConfig – Make alias field required and unique
Enforced that alias in communication Config is now mandatory for both Create and Update APIs; requests without it return MISSING_REQUIRED_FIELD .
Implemented case‐insensitive uniqueness validation on alias ; if the value matches any existing alias , the API returns DUPLICATE_ALIAS .

Client facing impact: No