Release Notes - ProntoCase

Releases in this section

• The Session Sync batch has been updated to send additional fields to DEX during both addSession and updateSession, based on the defined Service Type mappings.

  • For the following Service Types:

    • Accompanied activities

    • Assistance to maintain personal affairs

    • Cultural support

    • Digital education and support

    • Individual social support

  • DEX receives the following additional fields:

    • Time

    • IsSubcontractorDelivered

    • IsVolunteerDirectService

    • ServiceLocationSettingCode

  • For all other Service Types, the Time field and the additional 15 fields are not sent to DEX.

Verify Session Location / Service Location Reference Data

Check the Reference Data configuration for the Session Location / ServiceLocationSetting entries.

• If the records already exist, no further action is required.

• If the records do not exist, manually create the following Reference Data entries:

• The new fields are added to the Session object and record page.

• The Reference Data for Session Location / ServiceLocation Setting are added. (POST CONFIG)

• If middleware is already updated,

  • When a new session is created and synced to DEX, (addSession)

    • The listed fields' values are also passed to DEX.

      • If Service Type → Outlet Activity Id = Individual social support,

        • If Service Type → Service Type Name = Accompanied activities,

          • Only the following additional fields, IsSubcontractorDelivered, IsVolunteerDirectService, ServicelocationSettingCode, with the values are passed based on the Mapping.

        • If Service Type → Service Type Name = Assistance to maintain personal affairs,

          • Only the following additional fields IsSubcontractorDelivered, IsVolunteerDirectService, ServicelocationSettingCode with the values are passed based on the Mapping.

        • If Service Type → Service Type Name = Cultural support,

          • Only the following additional fields, IsSubcontractorDelivered, IsVolunteerDirectService, ServicelocationSettingCode with the values are passed based on the Mapping.

        • If Service Type → Service Type Name = Digital education and support,

          • Only the following additional fields, IsSubcontractorDelivered, IsVolunteerDirectService, ServicelocationSettingCode with the values are passed based on the Mapping.

        • If Service Type → Service Type Name = Individual social support,

          • Only the following additional fields IsSubcontractorDelivered, IsVolunteerDirectService, ServicelocationSettingCode with the values are passed based on the Mapping.

      • If Service Type → Outlet Activity Id = Transport,

        • If Service Type → Service Type Name = Direct transport,

          • Only the following additional fields IsSubcontractorDelivered, IsVolunteerDirectService, EngagementTimeMinutes, TriptimeMinutes, TripDistanceKm with the values are passed based on the Mapping.

        • If Service Type → Service Type Name = Indirect transport,

          • Only the following additional fields IsSubcontractorDelivered, IsVolunteerDirectService, TriptimeMinutes, TripDistanceKm with the values are passed based on the Mapping.

  • When an existing session is updated and synced to DEX, (updateSession)

    • The listed fields' values are also passed to DEX.

      • If Service Type → Outlet Activity Id = Individual social support,

        • If Service Type → Service Type Name = Accompanied activities,

          • Only the following additional fields IsSubcontractorDelivered, IsVolunteerDirectService, ServicelocationSettingCode with the values are passed based on the Mapping.

        • If Service Type → Service Type Name = Assistance to maintain personal affairs,

          • Only the following additional fields IsSubcontractorDelivered, IsVolunteerDirectService, ServicelocationSettingCode with the values are passed based on the Mapping.

        • If Service Type → Service Type Name = Cultural support,

          • Only the following additional fields IsSubcontractorDelivered, IsVolunteerDirectService, ServicelocationSettingCode with the values are passed based on the Mapping.

        • If Service Type → Service Type Name = Digital education and support,

          • Only the following additional fields IsSubcontractorDelivered, IsVolunteerDirectService, ServicelocationSettingCode with the values are passed based on the Mapping.

        • If Service Type → Service Type Name = Individual social support,

          • Only the following additional fields IsSubcontractorDelivered, IsVolunteerDirectService, ServicelocationSettingCode with the values are passed based on the Mapping.

      • If Service Type → Outlet Activity Id = Transport,

        • If Service Type → Service Type Name = Direct transport,

          • Only the following additional fields IsSubcontractorDelivered, IsVolunteerDirectService, EngagementTimeMinutes, TriptimeMinutes, TripDistanceKm with the values are passed based on the Mapping.

        • If Service Type → Service Type Name = Indirect transport,

          • Only the following additional fields IsSubcontractorDelivered, IsVolunteerDirectService, TriptimeMinutes, TripDistanceKm with the values are passed based on the Mapping.

      • If Service Type → Outlet Activity Id is not Individual Social Support OR Transport,

        • All the additional fields are passed with values based on the Mapping below.

Update the AboriginalOrTorresStraitIslanderOrigin Reference Data

Manually update the AboriginalOrTorresStraitIslanderOrigin in the Reference Data to add the Contact’s Indigenous Status picklist value to the newly added Reference Data field named Salesforce Value according to its matching Code.

1. Navigate to Setup.

2. Open Custom Settings.

3. Select Reference Data, then click Manage.

4. Filter or locate the records where CodeType = AboriginalOrTorresStraitIslanderOriginCode.

5. For each record, populate the Salesforce Value field as follows:

Description	Code	Salesforce Value

Description	Code	Salesforce Value
No	NO	Neither Aboriginal nor Torres Strait Islander Open
Aboriginal	ABORIGINAL	Aboriginal but not Torres Strait Islander origin Open
Torres Strait Islander	TSI	Torres Strait Islander but not Aboriginal origin Open
Aboriginal and Torres Strait Islander	BOTH	Both Aboriginal and Torres Strait Islander Open
Not stated/Inadequately described	NOTSTATED	Not stated/inadequately described Open

Open

6. Save all changes.

7. If the Salesforce Value field is not visible in the list view:

   1. Click Edit next to the View drop-down (for example, All).

      Open

      

   2. Proceed to Step 3 – Select Fields to Display.

      Open

      

   3. From Available Fields, move Salesforce Value to Selected Fields.

   4. Click Save.

The Salesforce Value field will now be visible in the Reference Data list view.

Open

• An update has been applied to the addClient and updateClient processes to conditionally pass AddressLine1 based on the Contact’s ConsentToProvideDetails field across all batches. When addClient or updateClient is executed and synced to DEX, ConsentToProvideDetails is populated based on the Contact’s consent field, and AddressLine1 is passed only when consent is provided.

  • If ConsentToProvideDetails is ticked, ConsentToProvideDetails is passed and set to true, and AddressLine1 is passed with the Mailing Street value.

  • If ConsentToProvideDetails is unticked, ConsentToProvideDetails is passed and set to false, and AddressLine1 is not passed.

• An update has been applied to the addClient and updateClient processes to populate AboriginalOrTorresStraitIslanderOriginCode based on the Contact’s Indigenous Status value across all batches. The value is matched against Reference Data where CodeType is AboriginalOrTorresStraitIslanderOriginCode and Salesforce Value matches the Contact’s Indigenous Status.

  • The Salesforce Value field has been added to the Reference Data custom settings and is populated for Reference Data where CodeType is AboriginalOrTorresStraitIslanderOriginCode. (POST CONFIG)

  • When a new client is added, AboriginalOrTorresStraitIslanderOriginCode under addClient is populated using the matching Reference Data Code.

  • When an existing client is updated, AboriginalOrTorresStraitIslanderOriginCode under updateClient is populated using the matching Reference Data Code.

Updates

• An update has been applied to the addClient and updateClient processes to support the Registered for My Aged Care? and MAC ID Contact fields across all batches. When addClient or updateClient is executed and synced to DEX, RegisteredForMacID is populated based on the Registered for My Aged Care? field, and MacId is populated based on the MAC ID field.

  • If Registered for My Aged Care? is ticked, RegisteredForMacID is passed and set to true, and MacId is passed with the MAC ID value.

  • If Registered for My Aged Care? is unticked, RegisteredForMacID is passed and set to false, and MacId is not passed.

• An update has been applied to the addClient and updateClient processes to support optional client fields with null values across client batches. When the client batch runs, the listed optional fields are passed to DEX only when populated and are not passed when null, while client creation and update processes continue to complete successfully.

  • When a new client is added, optional fields under addClient are passed if populated and not passed if null.

  • When an existing client is updated, optional fields under updateClient are passed if populated and not passed if null.

• An update has been applied to the addCase and updateCase processes to support optional case fields with null values across case batches. When the case batch runs, the listed optional fields are passed to DEX only when populated and are not passed when null, while case creation and update processes continue to complete successfully.

  • When a new case is added, optional fields under addCase are passed if populated and not passed if null.

  • When an existing case is updated, optional fields under updateCase are passed if populated and not passed if null.

• An update has been applied to the addSession, updateSession, updateSessionAssessments, and updateClientAssessments processes to support optional session fields with null values across session batches. When the session batch runs, the listed optional fields are passed to DEX only when populated and are not passed when null, while session creation, session update, and assessment update processes continue to complete successfully.

  • When a new session is added, optional fields under addSession are passed if populated and not passed if null.

  • When an existing session is updated, optional fields under updateSession are passed if populated and not passed if null.

  • For each session assessment under the session, optional fields under updateSessionAssessments are passed if populated and not passed if null.

  • For each client assessment related to a session participant under the session, optional fields under updateClientAssessments are passed if populated and not passed if null.

Updates

• An update has been applied to the addClient and updateClient processes to ensure JSON payloads are now consistently ordered according to the samples defined in the technical documentation.
  When addClient is executed, the generated JSON structure now follows the documented addClient sample format, and when updateClient is executed, the JSON output is ordered according to the updateClient sample specification.

• An issue related to handling special characters, specifically within password values, has now been addressed.
  Previously, unhandled special characters caused the request body to be incorrectly formed, which resulted in DEX returning incorrect data errors during synchronization.
  This has now been resolved to ensure request payloads are correctly generated and sync processes complete successfully.

Updates and Fixes

• New fields, Registered for My Aged Care? and MAC ID, have been added to the Contact object. If the middleware is updated, these fields are now included in DEX integration.
  When a Contact is updated (updateClient) and synced to DEX, RegisteredForMacID is populated based on the Registered for My Aged Care? field, and MacId is populated based on the MAC ID field.

• An issue was identified where no Sessions were uploaded due to a null pointer error in the BatchSyncSessions process (“Attempt to de-reference a null object”).
  This has been resolved by adding proper null handling and error management. As a result, batch sync processes now complete without runtime errors, and any failures are appropriately logged in the DSS Sync Log field across Contact, Client Cases, and Session records.

Fixes

Upgrade the API Version for Visualforce Components

• All visualforce components with an API Version lower than 45.0 are upgraded to version 60.0

Fixes

Upgrade the API Version for Apex Classes, Apex Triggers, and Visualforce Pages