Internal Enhancements

Internal Only:
This information is internal only, do not share outside of CivicPlus.

Accelerated Fetch: Customer Egress Assertion Schema (Phase 1)

Phase 1 of the accelerated-fetch initiative introduces a schema for asserting customer egress behavior. This lays the structural foundation for validating data leaving the system at the customer boundary, part of a multi-phase rollout.

Pendo Product Analytics Installed

Pendo analytics has been integrated into the application. This gives the product team visibility into how features are being used in practice, enabling data-driven decisions about product direction and prioritization.

On-Demand Processing: Pre-2023 Date Thresholds Blocked

Date threshold options prior to 2023 have been removed from the on-demand processing interface. This prevents staff from triggering processing runs against data ranges that are no longer reliable or supported.

Canvas User Enrollment: Idempotent Find-or-Create Flow

The Canvas integration now uses an idempotent find-or-create flow for user enrollment and {{glossary.Admin}} assignment. Running the same provisioning operation multiple times will no longer produce duplicate user records.

Workbench Document Editing Improvements

The document workbench now shows an edit button on every document row, replaces the embedded docviewer with a direct raw {{glossary.PDF}} display, and adds dynamic tooltips. These changes streamline the review-and-edit workflow for staff working through document queues.

Staff Identity Preserved in API Audit Log

{{glossary.API}} actions taken by staff members are now attributed to the correct staff identity in the audit log. This improves traceability for audits and investigations where it was previously unclear whether an action came from staff or an automated process.

Internal Resolved Problem Tickets

Internal Only:
This information is internal only, do not share outside of CivicPlus.

DT-10601: Stale {{glossary.CMS}} tags were not being cleared when a document was migrated to a different platform, leaving the document tagged for the wrong platform.
- Expected Functionality: When a document is migrated, any outdated CMS platform tags are now evicted so the document reflects its current platform accurately.
The Salesforce contract discount (cp_sf_discount) was not being applied during the wet-signature signing path for agreements.
- Expected Functionality: The Salesforce discount field is now correctly applied when a customer proceeds through the wet-signature signing flow.
Deleting stuck, stuck-links, or stale-links in the admin panel would display a misleading “{{glossary.JSON}} error” message even when the deletion succeeded.
- Expected Functionality: Delete operations now complete without surfacing a false error notification.
The “Legacy Processing Detected” banner in the workbench was appearing for documents that had never been processed at all, not just those processed using legacy pipelines.
- Expected Functionality: The banner is now suppressed for completely unprocessed documents, appearing only where legacy processing has actually occurred.
Several aspects of the internal Slack bot were broken; heartbeat stability, thread participant tracking, native file input handling, and ticket link formatting.
- Expected Functionality: The Slack bot now reliably sends heartbeats, correctly tracks thread participants, handles file uploads natively, and formats ticket links properly.
The document viewer was treating a manifest value of ‘deferred’ as if hash-based document identification was disabled, causing incorrect behavior for documents in that state.
- Expected Functionality: A ‘deferred’ manifest value is now correctly interpreted as enabled, ensuring hash-based document lookup functions properly.
Documents with no hash (orphan documents) were causing the manifest processing worker to crash rather than recover gracefully.
- Expected Functionality: The worker now degrades gracefully for hashless orphan documents, logging the situation and continuing without a crash.
Staff-initiated Slack chats were incorrectly retaining a customer_id from a prior context, potentially associating internal conversations with the wrong customer account.
- Expected Functionality: When a staff member initiates a Slack chat, the customer_id is now cleared so the conversation is not associated with any customer.
Optional fields in the TimelineEvent API response were missing their default None values, causing serialization errors for consumers of that endpoint.
- Expected Functionality: Optional TimelineEvent fields now correctly default to None when omitted, resolving response format inconsistencies.
The audit log record_id was not being bound as a UUID type, which was causing the /documents/{id}/history endpoint to fail entirely.
- Expected Functionality: The record_id is now correctly typed as a UUID, restoring full functionality to the document history endpoint.

May 20, 2026 DocAccess Release Notes