Special Programs 25.7.0.0

Child Profile Tracking Columns and Duplicate Prevention

Child profile types that receive data from child templates include internal columns designed to track the source of each child profile. The columns are as follows:

• DocTemplateIDT#

• DocumentIDT#

• ChildTemplateIDT#

• ChildDocumentIDT#

These tracking columns play a crucial role in preventing the creation of duplicate child profiles during data flowback from documents.

Details:

• Current Issue: Upon receiving a transfer envelope, the tracking columns are not populated in the receiving database. As a result, when a live document is created with child documents, new child profiles are generated, leading to duplicates.

• Impact: This duplication results in inconsistencies and inefficiencies in the data.

• Resolution: To prevent the creation of duplicate child profiles, the following changes are necessary:

  • Envelope Creation in Source District:

    • The data for each document within the envelope should include a comprehensive list of all child profiles associated with that document, utilizing the original tracking columns (DocTemplateIDT#, DocumentIDT#, ChildTemplateIDT#, ChildDocumentIDT#).

    • This process involves iterating through any child profiles being transferred, identifying those linked to a document, and incorporating a specific child profile mapping tuple in the relevant document’s transfer data: {{{ChildProfileTypeIDT, ChildProfileIDT, ChildTemplateIDT#, ChildDocumentIDT#}}}.

  • Live Document Creation in Receiving Database:

    • The tracking columns (DocTemplateIDT#, DocumentIDT#, ChildTemplateIDT#, ChildDocumentIDT#) must be reinstated in the relevant child profiles.

    • The values for DocTemplateIDT# and DocumentIDT# will reference the current live document, while ChildTemplateIDT# and ChildDocumentIDT# will be remapped based on the values from the tuples described in the first step.

Configurable Captions for Document Fields

The Case Manager field caption on the Document Change Status screen is now configurable to support state-specific terminology. This update introduces an optional caption property for document fields, enabling customized captions without requiring field renaming. The captions of core document fields are editable only if they have not been set in the core model. The caption reflects the configured value, enhancing customization for international markets.

Staff Deactivation and Audit Logging Enhancements

This update ensures that staff with future end dates remain active, with deactivation occurring only if the end date is today or earlier. Additionally, audit logging has been enhanced to record deactivation activities.

Ability to use a field name or formula in Role Caption

The Role Caption in the window now displays the field value instead of static text. When selecting options in the Referral Committee Member List, such as Parent/Guardian or Other, the signer role dynamically reflects the chosen option, either from the keyword table or the value entered in a text box.

Choosing the lookup option in the Referral Committee Member List displays the content of the Description(Help Text) field as the signer role, allowing for the inclusion of field names, formulas, or static text in the signer role display.

Fix for HTML Code Display in Long Text Boxes

Issue:
After finalizing a document, editing sections in edit mode caused HTML codes to be displayed in long text boxes.

Resolution:
Now, while editing a finalized document, the HTML codes no longer appear within the long text boxes.

Fix for Screen Reader Compatibility with Stylized Text Fields

Issue:
Stylized text fields that allowed graphics were not being read by screen readers, causing accessibility issues for users who relied on assistive technologies.

Resolution:

Fixed the compatibility issue to ensure that screen readers can now properly read stylized text fields that include graphics.