Pharos Maintenance Release Scheduled - 1.850.56

Your instances are scheduled for upgrade starting January 3rd, 2025

Outline

Upgrade Process

Our upgrades are separated in 2 phases: sandboxes first, followed by production instances, typically a week later. The full release notes are sent prior to the first phase. We will send another reminder a few days prior to your production instance upgrade. Upgrades are typically deployed at 8pm Pacific Time on Fridays.

Upgrade Schedule

If you are receiving this notification your org is in the queue to receive this upgrade in accordance with our patch release schedule. For more details please refer to our release schedule published on Pharos Support Portal.

This upgrade will be released as follows:

  • January 3rd, 2025 — sandbox instances

  • January 10th, 2025 — production instances

Opting Out

If you do not wish to upgrade your instance at this time please let us know by sending an email to [email protected] and providing your Salesforce Organization ID.

Note: If you decide to opt-out of this upgrade, the next maintenance release will still proceed according to the release schedule and you will receive the current upgrade along with the planned one.

Release Notes

Pharos maintenance releases typically address known or reported bugs. However, we will sometimes include small functionality enhancements as well.

Bugfixes

Errors on cache item over 100K (LOG-2311)

Impacts: Core

Unable to select Github repository due to an error (LOG-2306)

Impacts: Change Tracking

Failed broadcast keeps retrying and going into an endless loop (LOG-2310)

Impacts: Connected Orgs

Unable to see the context tab in some flow logs (LOG-2312)

Impacts: Flow Errors

Transform element: tooltip UI issue in flow debug view (LOG-2281)

Impacts: Flow Errors

Flow Debug View: path overlapping starting flow element (LOG-2268)

Impacts: Flow Errors

Debug view (Integration log): The last line is overlapped on Body tab. (LOG-2273)

Impacts: Integration Logs

Incorrect font used to display impact report data on Windows (LOG-2249)

Impacts: Issue Tracker

Error occurs when saving Jira Defaults settings from Admin (LOG-2323)

Impacts: Jira Integration

JIRA Integration: Switching from Cloud to Hosted JIRA fails (LOG-2307)

Impacts: Jira Integration

Jira tickets created for older issues (LOG-2304)

Impacts: Jira Integration

Create Ticket (on Log, Issue): Issue with 'Complete the Form' option (LOG-2275)

Impacts: Jira Integration

Create Ticket (on Log, Issue): Ticketing Action forms are not displayed when a user changes values in the 'Send action to' field (LOG-2274)

Impacts: Jira Integration

Create Ticket (on Log, Issue). The Subject field does not display changes made in JIRA Ticketing Action. (LOG-2272)

Impacts: Jira Integration

Event Record Lightning Page is not assigned as Org Default (LOG-2328)

Impacts: Monitoring

Donut charts on event details are not showing correctly (LOG-2321)

Impacts: Monitoring

Intermittent Pharos errors for some monitoring rules (LOG-2314)

Impacts: Monitoring

Non-salesforce object ids are mislabeled as related objects (LOG-2329)

Impacts: Log Details

Error on very large issues processing. Too many query rows: 50001 (LOG-2320)

Impacts: Issue Tracker

Pharos error on very large issues with lots of related records. Related Objects: data value too large (LOG-2317)

Impacts: Issue Tracker

Trace Schedule - trace calendar on list view not show correctly (LOG-2254)

Impacts: Tracing

Attempt to de-reference a null object when processing Bulk API results (LOG-2340)

Impacts: Bulk API

Charts on Event don't show correct information (LOG-2339)

Impacts: Monitoring

Failed to create Log for Inbound Email: FlowExceptionParser: Attempt to de-reference a null object (LOG-2318)

Impacts: Flow Errors

Enhancements

Remove ticket link from Issue when ticket is removed in Jira or Azure DevOps (LOG-2260)

Impacts: Jira Integration, Azure DevOps

Add full error message to pharos log details if inbound email fails to create a log (LOG-2271)

Impacts: Error Tracking

Updated color scheme for showing related issues on occurrence chart (LOG-2022)

Impacts: Issue Tracker

Adjust ticket linking/duplication logic (LOG-2244)

Impacts: Jira Integration, Azure DevOps

Don’t show Event Log Records tab on Archival Event layout (LOG-2216)

Impacts: Log Retention