Case Number
|
Description
|
Fixed Version
|
---|---|---|
00161135
|
Scheduling failed with an error when the user scheduled work orders in Long Job Scheduling mode with multiple technicians even when there was sufficient technician capacity.
|
September 2024 Patch
|
Case Number
|
Description
|
Fixed Version
|
---|---|---|
00160799
|
The MultiDay Work Orders with a few events in the past and a few events in the future that were marked as locked by DC were reassigned in the subsequent batch run.
|
October 2024 Patch
|
Case Number
|
Description
|
Fixed Version
|
---|---|---|
00153199
|
The individual records in the IB Hierarchy did not open in a new browser tab.
|
July 2024 Patch
|
00156109
|
The Technical Attributes were not updated properly when invoked from Core-Technical Attributes LWC component on a Work Order. This issue occurred when Technical Attributes History was deleted on the Installed Product.
|
July 2024 Patch
|
00154280
|
When the auto-entitlement was performed on a Work Order, the Work Order was incorrectly entitled with a Service Contract when there were multiple Service Contracts. The Auto Entitlement Rule was configured for Product in the Entitlement Settings. For more information, see Choosing Auto Entitlement for Multiple Service Contracts.
|
July 2024 Patch
|
00156147
|
The Technical Attribute on the Work Order allowed users to save the record without filling in mandatory fields. Also, the order of the sections did not match the Technical Attribute template after the values were updated and page was refreshed. This occurred when the setting, "is display all attributes" was set to "From matching templates" in the Edit page.
|
July 2024 Patch
|
00157333
|
When the admin configured the Weekly AutoFill Frequency in the AutoFill tab of Timesheet , the "Create Timesheet On" field was reset to "Monday" when the page was reloaded.
|
July 2024 Patch
|
00155069
|
When a user clicked on an event in the IP Timeline, the pop-up was misaligned with the respective icon.
|
August 2024 Patch
|
00156097
|
The classic SLA clock on the Work Order did not adjust for the minutes it was paused after the user resumed it.
|
August 2024 Patch
|
00156154
|
The user could not complete the Inventory process due to permission issues.
|
September 2024 Patch
|
00159478,
00160239
|
When the user tried to set up a Stock Adjustment to remove all the serialized parts from a product stock, an error occurred indicating that the number of serial numbers entered did not match the actual quantity for the line.
|
September 2024 Patch
November 2024 Patch
|
00160511
|
The Salesforce page did not refresh, and field values were not updated after the successful launch of the background SFM.
|
September 2024 Patch
|
00159896
|
The configured fields were not available in the Custom Action SFM for the Case object.
|
October 2024 Patch
|
00160103
|
An error message was displayed when the user hovered over the list of Installed Products in the Installed Product Hierarchy.
|
October 2024 Patch
|
00161251
|
The SCON Scheduler executed the Timesheet engine when the Autofill flag was false in the Timesheet configuration template.
|
October 2024 Patch
|
00164499
|
Go app push notifications did not re-direct to the record page due to incorrect payload.
|
November 2024 Patch
|
00164568,
00156359
|
When a large number of PM plan records were processed at a time, the operation failed with an SOQL error. This issue occurred because of exceeding the Salesforce governor limits.
|
November 2024 Patch
|
00152227,
00151551
|
When the Immediate type Dispatch process is loaded with high volume assignment rules, user experienced performance issues for immediate Dispatch process.
|
Core 24R3
|
00152344
|
For PM plans generated via the PM Template with the 'Generate all Recurrences Upon Creation' checkbox selected, the generated PM Work Orders displayed an incorrect Preferred End Date starting from the second Work Order onward,
|
Core 24R3
|
Case Number
|
Description
|
Fixed Version
|
---|---|---|
00161164
|
When the user created multiple records for a custom object, not all SFA notifications were sent.
|
September 2024 Patch
|
Case Number
|
Description
|
Fixed Version
|
---|---|---|
00160099
|
The existing SFM expressions with boolean fields displayed an error at the field level, indicating that the user could not select the configured values.
|
September 2024 Patch
|
00159366
|
After the org was upgraded to v23.2, a new ‘ Part’ record type was added when an active ‘Part’ record type existed in the Product object.
|
October 2024 Patch
|
00162213
|
The transactions were failed and DVR error was displayed when the user deployed SFM Process with associated standard lookup via CLI tool.
|
October 2024 Patch
|
Case Number
|
Description
|
Fixed Version
|
---|---|---|
00158156
|
The Hide Empty Section On Load configuration in the Child section of the SFM transactions of type “Convert existing child records into new child records and create new child records” did not function as expected. Tabs containing records were hidden when the configuration was enabled.
|
August 2024 Patch
|
Case Number
|
Description
|
Fixed Version
|
---|---|---|
00154496
|
The list of States/Provinces displayed was not relevant to the selected country in the custom address field.
|
July 2024 Patch
|
00161194
|
The validation message did not display correctly when the user added or edited Parts or Labor lines in the work order.
|
September 2024 Patch
|
00161155
|
The incorrect number of columns was displayed in extended edit screens instead of displaying the number of columns configured in the page layout.
|
October 2024 Patch
|
00161716
|
The UI button labels in confirmation windows were not translated and displayed in the configured language.
|
October 2024 Patch
|
00162686
|
Dependent picklist fields were not displayed correctly on SFMs when the controlling field was of type Boolean.
|
October 2024 Patch
|
00164128
|
A blank page was displayed for price details when the user invoked the Get Price option for a work order. This issue occurred only when Get Price was configured via Web service.
|
November 2024 Patch
|
00164072
|
The first checkbox field value was set to True by default on the SFM when the user added a new child line, without allowing user selection.
|
November 2024 Patch
|
00155814, 00152967
|
The child line field moved to the top of the SFM anchored area when the user edited the field in details data grid.
|
Core 24R3
|
Case Number
|
Description
|
Fixed Version
|
||
---|---|---|---|---|
00153624
|
The Migration Tool became unresponsive when the user tried to import an SFM with a Linked SFM process into a target org.
|
August 2024 Patch
|
||
00158064
|
Migration of SFM wizards failed because of mismatched child sections in the page layout when the user migrated an SFM Wizard that contained two or more SFMs. The SFMs had child sections with identical names but different sequences in the page layout.
|
August 2024 Patch
|
||
00159642,
00159735,
00159582
|
Migration of SFM transactions and SFM Wizards related to Output Documents failed because of a mismatched page layout error.
|
August 2024 Patch
|
||
00159845,
00160373
|
User was unable to retrieve SFM transactions through command plugins when the SFM transactions had a large number of validation rules and Formula fields.
|
August 2024 Patch
|
||
00161254
|
SFM Wizard step titles were not updated correctly in the target org if the step name and step title differed when the user migrated configuration items using command plugins.
|
September 2024 Patch
|
||
00162212
|
The DML error was displayed when the user deployed the SFM Transactions using the command plugins.
|
November 2024 Patch
|