|
Case Number
|
Defect Number
|
Description
|
Fixed Version
|
|---|---|---|---|
|
00186786
|
068202
|
When a Work Order was unscheduled in Service Board, the status change appeared in Salesforce but not in Service Board because the delete appointment HTTP notification was incorrectly marked outdated after the appointment's workflow field reached its final Canceled state.
|
45.0
|
|
00186346
|
067998
|
Service Board incorrectly reassigned technician ownership on multi-technician work orders when events were created and saved using the custom Ordre de longue durée button.
|
45.0
|
|
00186337
|
068125
|
Service Board displayed a blank screen and did not redirect to the Work Order when launched via SFM on work orders linked to work plans or test cases.
|
45.0
|
|
00184170
|
067627
|
The Service Board prevented users from adjusting appointment start or end dates and automatically reset the values to 8 March 2026 before saving. The issue occurred with the calendar timezone set to Eastern Daylight Time/Eastern Standard Time (EDT/EST), and the cause was related to the US daylight saving time transition.
|
Service Board 25.2 Patch 3
|
|
00182716
|
066936
|
Technician, Service Team, and User records intermittently failed to synchronize from Salesforce to Service Board. The issue occurred due to missed EMP platform events, and recovery required reinitialization of the connection.
|
Service Board 25.2 Patch 3
|
|
00184759
|
067495
|
HTTP notifications failed with response status 500 during service call assignment in Service Board, and the system did not retry the failed notifications automatically. The issue caused customers to submit the notifications manually after errors reported an inability to obtain exclusive access to records.
|
Service Board 25.2 Patch 3
|
|
00184058
|
067245
|
The Recommended Resource feature did not perform optimally under data distribution conditions that included a high volume of credentials and qualifications, and no resource-matching constraints such as Account, Location, Installed Product, or job resource preferences were configured. The issue occurred specifically in scenarios where the absence of matching constraints combined with large credential and qualification datasets, which caused the feature to be insufficiently optimized for that configuration.
|
Service Board 25.2 Patch 3
|
|
00181794
|
066634
|
A validation error occurred when some appointments of the job could not be synchronized to Salesforce due to a deleted appointment. When users accessed the affected work order in Service Board, the system showed an error indicating that a deleted appointment record was not synchronized, even though the job was associated with a single active appointment and no corresponding HTTP notification failures were found.
|
Service Board 25.2 Patch 2
|