|
Case Number
|
Internal Defect
|
Description
|
Product/ Feature
|
Fixed Version
|
||
|---|---|---|---|---|---|---|
|
00184511,
00185633
|
067997
|
All-day events in the Dispatch Console automatically shifted the end date by one day after they were edited and saved. The issue occurred for all-day events that spanned a daylight saving time transition, where events with dates crossing the DST boundary displayed the correct dates initially but changed the end date to the following day after editing. The behavior was observed in DST-observing time zones such as America/Chicago and caused overlapping events and incorrect scheduling information in the Dispatch Console. The issue occurred because the scheduler automatically calculated the event end date based on duration values, and the daylight saving time adjustment added an extra 60 minutes during the calculation, which caused the end date to roll over to the next day.
|
Dispatch Console
|
25.20000.33
|
||
|
00185590
|
068235
|
Scheduled end dates displayed in the Dispatch Console changed unexpectedly when users edited work order events. In such cases, an event displayed one end date in the Dispatch Console, but opening the event for editing showed the end date as the following day. The issue affected past, current, and future events and was observed across multiple users and regions. The issue occurred because the scheduler automatically calculated event end dates based on duration values, and daylight saving time transitions introduced an additional 60-minute offset that caused the calculated end date to advance by one day.
|
Dispatch Console
|
25.20000.33
|
||
|
00188395,
00188503
|
068496
|
The Calculate button in the Dispatch Console caused the appointment date and departure time to shift to the next day during work order scheduling. The issue occurred after dispatchers assigned a work order to a technician and used the Calculate action, which resulted in the calculated departure date displaying the following day instead of the scheduled date. The issue occurred because the event start date and time duration were applied twice during the calculation process, causing the system to incorrectly advance the appointment date to the next day.
|
Dispatch Console
|
25.20000.33
|
||
|
00187511
|
068348
|
The output document appeared without borders after a user saved or updated content in the Output Document Designer using the new editor. This issue occurred as the new editor did not retain border formatting after the save action.
|
Output Document Designer
|
25.10000.67,
25.20000.33
|
||
|
00186141
|
067862
|
The Work Plan Assignment section disappeared from the page after a user without delete access selected Remove option for a Work Plan Assignment, even though the delete action is blocked. This issue made the record appear deleted.
Additionally, an error message is displayed after the delete action is blocked, but the message did not clear after subsequent actions and persisted until the user performed a manual component refresh.
|
Work Plans and Task Management
|
25.10000.67,
25.20000.33
|
||
|
00187222,
00187521
|
068314
|
PM schedule and schedule definitions were not created for the PM Plan due to excessive query volume.
|
Preventive Maintenance
|
25.20000.33
|
||
|
00185256
|
067669
|
The Tab key failed to move the cursor to the Time field in the inline edit of a child object after a user selected a date from the date picker. As a result, users could not enter a time value using tab navigation. This issue occurred after the upgrade to version 25.2.
|
SFM Delivery
|
25.20000.33
|
||
|
00187058,
00188902
|
068190
|
The Enter key failed to move the cursor to a new line in text area fields of a Service Flow Manager form. Users failed to insert line breaks.
|
SFM Delivery
|
25.10000.67,
25.20000.33
|