Fixed Update skyvvasolutions__BulkReprocessScheduledJobId__c Field Issue on Interface Records #
Previously, the scheduler would update the ‘skyvvasolutions__BulkReprocessScheduledJobId__c’ field on the interface record with the Schedule Job Id. This field was used to store the job ID for the scheduler. However, this was caused by users auto-modifying the interface record. The field was used in an earlier version of our bulk feature but is no longer needed in the current version, as we now store the job ID directly on the skyvvasolutions__IScheduler_Setting__c object instead. This issue has been resolved, and the interface records are no longer updated with the Schedule Job ID.
Resolved Error: ‘Too Many Query Rows (50001)’ on Bulk Control Board #
There is an issue when accessing the Bulk Control Board. A Message Error Alert appears with the text “skyvvasolutions: Too many query rows: 50001”. This error occurs due to the large number of baskets being queried. For example, the Bulk Control Board queries 50,000+ Baskets and History Baskets. To resolve this, we have set a limit of 10,000+ History Baskets to display on the screen.
Fixed Duplicate Sequence in Mapping Records #
We encountered duplicate sequences in the mapping records, which caused the payload to be generated incorrectly. This issue has been resolved by generating the numbers in order, ensuring that duplicate numbers are no longer generated.
Fixed Check Adatper Status Before Creating the Message of InvokeCalloutV3() Processing #
In the previous version, the InvokeCalloutV3() function did not check the adapter status while creating the message. However, in the adapter, it would follow the status rules. If the status was not active, we would not have created the message before calling InvokeCalloutV3(). This issue has been fixed, and we have now provided validation to create the message based on the status of the adapter.
Fixed Issue related to “Delete child not present in the payload” While Using Workflow #
We previously encountered an issue where the deletion of child records was affecting parent records that were updated through different target interfaces in the workflow. For example, if you had defined an interface called ‘AccountIn’ with the ‘Ichiain Contact (Delete child not in the payload)’ option, and then defined another workflow target called ‘AccountParentIn’, any contacts associated with accounts that were updated through the ‘AccountParentIn’ interface would be incorrectly deleted. This issue has been resolved by ensuring that the child records are not deleted if the interface does not have the ‘Delete child in the payload’ option set.
Resolving Scheduler Display Issues on the Agent Control Board #
In the previous version, we encountered an issue where the Salesforce agent’s next-run scheduler would fail, and the scheduler records did not display on the scheduler tab of the agent control board. This issue has now been fixed. The scheduler records and their associated comments are now correctly displayed on the scheduler tab, with any issues or errors marked in red.
Issue Fixed – Saving Name Edits on Restore Interface Screen #
We previously encountered an issue where users would receive an error message when attempting to save edits made to the name field on the Restore Interface screen. The error message stated: ‘TypeError: Action failed: skywvasolutions:ImportSKYVVASobjectsScriptScontroller$handleSaveEdition [mapping[j]( sn + “Full Source_ Path_c’)] is undefined]. This issue has been resolved.
Fix for IStructure Deletion When Updating Query Old Design Outbound Interface #
There was an issue where, upon updating the query of the old design outbound interface, the old IStructure created by the Agent would be deleted immediately. This issue has now been fixed, preventing the deletion of the Agent’s IStructure.
