Release Notes
2.9
Date: Sep 30, 2024
Allow Valence to be installed in orgs with any standard fields encrypted
Enable table preferences such as number of records or filters to persist in browser
Add Valence Configuration record to allow scratch and trial orgs to go beyond max queueable depth of 5
Bugfix: Removing one side of a mapping resulted in a UI error message
Bugfix: Mapping wizard didn’t mark field usage on first display
Bugfix: Invalid field paths could result in corrupted UI artifacts in Transformation view
2.8
Date: August 9, 2024
Record Snapshot view can now search properties and messages †
Bugfix: Local Salesforce adapter configuration fails to load
† Manual Upgrade Step: Valence customers upgrading from prior to 2.8 will need to manually edit the Valence Record Snapshot object and check “Allow Search” to enable the improved search results.
2.7.1
Date: July 9, 2024
Bugfix: Record Snapshot Grid may not preserve Sync Event filtering
Bugfix: Record Snapshot Grid can crash on invalid JSON properties
2.7
Date: July 8, 2024
Bugfix: Resolve NoErrorObjectAvailable error thrown when viewing sync event.
Bugfix: Change interface evaluation strategy, failing due to Summer ‘24 bug.
Bugfix: Mapping editor doesn’t reset filtering when clicking away.
Bugfix: Large number of problems in a batch prevents the batch from resolving.
Group problem summaries by generic exception message.
When needed, compact problem summaries to fit Sync Event field space.
Update Record Snapshot grid, move properties view to modal.
Support IMF-fixdate/RFC7231 for inbound date format.
Mapping editor now visually indicates if a property is already used in another mapping.
Update SOQL and DML security enforcement.
Update to API version 61 (Summer ‘24).
2.6.1
Date: March 20, 2024
Bugfix: Resolve navigation break caused by enabling browser back and forward buttons.
2.6
Date: March 14, 2024
Bugfix: Resolve an issue with the save button on Adapter configurations remaining disabled when changing Named Credential.
Update to how Valence selects changed Salesforce records to catch potential misses. More work on this forthcoming.
Browser back and forward buttons will now affect the Valence UI.
UI improvements in Mappings and initial page load experiences.
Updated to API version 60 (Spring ‘24).
2.5
Date: January 12, 2024
PlanFetchAgain() will now always execute in an asynchronous context (higher limits), previous it was sync / async depending on how DELAY was called.
Expanded checks for errors when publishing Platform Events, will show up in Valence Logs if they occur.
Bugfix: Resolve an edge case with some exceptions that would cause an overcount in a Sync Event’s jobsCompleted value.
Bugfix: Resolve a rare race condition that would sometimes close a Sync Event too early.
Bugfix: Resolve a rare race condition that would sometimes mark a Sync Event as successful despite a failing batch.
Bugfix: Resolve an edge case with planFetch() that would sometimes fail to immediately close a Sync Event.
Bugfix: Resolve an edge case with CUMULATIVE_SCOPES that would sometimes fail to immediately close a Sync Event.
Increase the maximum number of encryptable bytes to handle serializing large records.
Update ValueConverter to correctly parse millisecond timestamps stored as string values when writing to DateTime fields.
Bugfix: Truncate recent values saved for records to avoid exceeding the maximum number of storable characters.
Updated documentation to improve clarity.
2.4
Date: December 4, 2023
Bugfix: Resolve a race condition with parallel batches that sometimes would leave a Sync Event in an incomplete state.
Updated documentation in a number of places to improve clarity.
2.3
Date: October 25, 2023
Update to Salesforce API version 59.0 (Winter ‘24).
2.2.1
Date: September 28, 2023
Bugfix: Correct a key matching edge case in RelationshipFilter introduced in 2.2.
Bugfix: Correct an issue with ChildDetective throwing errors about quotes in some circumstances.
2.2
Date: September 5, 2023
Add missing documentation on FieldBuilder.addChild().
New feature allowing Full Run mode to toggled on and off per-Link, allowing scheduled Links to fetch all data every time if desired.
Bugfix: correct an issue with numeric Salesforce fields used as keys when upserting into Salesforce, or doing relationship lookups.
Bugfix: better handle keys with unusual characters when upserting into Salesforce, or doing relationship lookups.
2.1
Date: April 18, 2023
Add the ability to store Additional Table Details, useful for Adapters with more complex table definitions.
2.0.4
Date: February 11, 2023
Expand the SF Value Groomer filter to handle a wider variety of value formats when writing to Time fields in Salesforce.
2.0.3
Date: January 23, 2023
Bugfix: fix a rare issue with an internal tracking value in high-volume orgs.
2.0.2
Date: January 19, 2023
Bugfix: fix an issue with the ChangeSet editor no longer parsing API responses as XML.
2.0.1
Date: November 17, 2022
Bugfix: fix a display issue on the Subscription Details screen when Lightning Web Security is enabled.
Bugfix: resolve a NullPointerException being thrown in certain circumstances of parallel batch processing.
2.0
Date: October 27, 2022
Update to Salesforce API version 56.0 (Winter ‘23).
Bugfix: avoid a javascript library issue when Lightning Web Security is enabled (LWS enabled by default in new orgs starting Winter ‘23).
Bugfix: certain UI screens show a javascript access denied error, suspected Winter ‘23 side effect.
1.102
Date: October 21, 2022
Add a sequence number to every batch that is processed so they can be arranged independently of the order in time where they are created.
When using custom fetch cursors, use the new sequence numbers to set the cursor to the one from the “last” batch (even if it was not the last batch processed).
More detailed stored info about the configured schedule for a Link:
Clearer explanation in the UI for what the schedule is.
Opening the schedule UI sets the form to the current configured values.
New feature: a warning if a Link has a saved schedule that is not active, with the ability to click to restore the schedule.
These new expanded behaviors will only be present on Links scheduled after this update is installed; re-schedule older Links if you want the new features on them.
Expand tracking and display of custom fetch cursors.
Bugfix: UI exception in a specific circumstance should block movement to next screen.
Performance improvement: one UI screen was not preloading its assets.
1.101
Date: August 1, 2022
Change how empty batches are marked and evaluated.
Bugfix: incorrect sync event tracked value in certain circumstances when using the CUMULATIVE_SCOPES FetchStrategy.
1.100
Date: May 21, 2022
Bugfix: Links scheduled to run every X minutes that take longer than X minutes for a run stop re-scheduling.
Delta syncing now has an additional mode that Adapters can use called Delta Sync With Cursors.
Typical delta sync is done using a timestamp and a last modified field, but some systems will use a different pattern.
This new feature allows Adapters to use their own custom cursor to track which records they want to fetch. Adapters can hand values to Valence for storage, and receive them back on future runs.
Update some of the documentation to correct typos and bring syntax up-to-date.
1.99.1
Date: April 25, 2022
Bugfix: Links scheduled to run every X minutes that take longer than X minutes for a run stop re-scheduling.
1.99
Date: January 24, 2022
Bugfix: incorrect help popup positioning in a few different UI screens.
Bugfix: regression where the max automated replay configured value is not respected when Automated Replays are turned on for a Link.
1.98
Date: December 3, 2021
Bugfix: correct an issue in the Change Set Editor UI screen.
Bugfix: subtle bug in the delta timestamps used in remote Salesforce record queries.
Bugfix: mapping drill-down button doesn’t work for nested object fields.
Bugfix: wrong default selector when starting a mapping from a target list field.
Bugfix: ugly formatting for configuration explanation when LocalSalesforceAdapter has custom SOQL added then removed.
Bugfix: Exception in ValenceUtil.createTestMapping() when target side is null.
Bugfix: Mappings using advanced mode list selectors should open in advanced mode.
Bugfix: Parallel batch runs don’t respect the isFullRun flag.
1.97
Date: November 11, 2021
Allow mappings to be configured per-mapping to ignore or persist null values. If ignored, an incoming null value will not overwrite an existing value.
Pop a warning in the Valence UI if the current user does not have the Valence User permission set assigned to them.