Vlocity Government Package Links

Production Download

Sandbox Download

Production Download

Sandbox Download

Production Download

Sandbox Download

Production Download

Sandbox Download

Production Download

Sandbox Download

Production Download

Sandbox Download

Production Download

Sandbox Download

Production Download

Sandbox Download

Salesforce recommends the more secure OAuth 2.0 for DocuSign. We've introduced a custom implementation for you to switch from OAuth 1.0 to OAuth 2.0 authentication.

If you upgraded to 240.22.4 (which supports OAuth 2.0) from 240.11 and plan to start using OAuth 2.0 immediately, set the DocuSignAuth to OAuth 2.0.

If you continue to use OAuth 1.0 until March 2024, or are setting up DocuSign for the first time, you don't need to change the custom settings.

In OAuth 2.0, the DocuSign Send On Behalf Of (SOBO) functionality is supported only through Named Credential. To send or sign DocuSign on behalf of another user, create a Send On Behalf field in the User object and assign the Send on Behalf named credential from that field in the user’s page. See Setup Send on Behalf of Another User.

• To change to OAuth 2.0, open Setup.

• Go to Custom Code | Custom Settings.

• For General Settings, click Manage.

• Click New.

• Enter the name as DocuSignAuth. The name and value fields are case sensitive.

• Enter the value as OAuth 2.0.

• Save your changes.

See Upgrade to OAuth 2.0 Required to Manage DocuSign Integration.

Fixed issue: Files uploaded via Omniscript File element are uploaded but do not attach to the requested record.

Fixed issues:

• After upgrading to Summer '23, OmniScripts fail with the "Uncaught #<Object> throws" error when the Lightning Web Security is enabled.

• The child FlexCard list is not displayed, and child FlexCards can't be added.

Fixed issue: In an OmniScript, when a "set error" is added to a select element, selecting an element and then clearing the value results in array[0] instead of null in the datajson.

Salesforce recommends the more secure OAuth 2.0 for DocuSign. We've introduced a custom implementation for you to switch from OAuth 1.0 to OAuth 2.0 authentication.

If you upgraded to 242.16 (which supports OAuth 2.0) from 240.11 or 242.xx, and plan to start using OAuth 2.0 immediately, set the DocuSignAuth to OAuth 2.0.

If you continue to use OAuth 1.0 until March 2024, or are setting up DocuSign for the first time, you don't need to change the custom settings.

In OAuth 2.0, the DocuSign Send On Behalf Of (SOBO) functionality is supported only through Named Credential.

• To change to OAuth 2.0, open Setup.

• Go to Custom Code | Custom Settings.

• For General Settings, click Manage.

• Click New.

• Enter the name as DocuSignAuth. The name and value fields are case sensitive.

• Enter the value as OAuth2.0.

• Save your changes.

See Upgrade to OAuth 2.0 Required to Manage DocuSign Integration.

Fixed issues:

• VFActionFunctionController.actionFunctionResult has a new method: VFActionFunctionControllerApexClassCheck. If set to true, it perform apex class checks if user's profile has access permissions.

• The "Overwrite Target For All Null Inputs" option in DataRaptor now creates an empty JSON node for null values, instead of not creating the node at all.

• For DocuSign, you can select whether to use OAuth 1.0 or OAuth 2.0 after upgrading to 240.11 or any Spring 2023 package. But OAuth 1.0 is supported until March 2024 when you must switch to using OAuth 2.0.

Fixed issue: Starting in Spring '23, OmniScript displays an error with a selected value for Lookup elements in an Edit block with Enable Repeat checked and Clone Upon Repeating unchecked.

The OmniScript error message is "This page has an error. You might just need to refresh it. [Cannot use 'in' operator to search for 'jsonData' in undefined]."

Upgrade to OAuth 2.0 Required to Manage DocuSign Integration

Fixed issue: Bundling OmniOut resulted in warnings, including one that affects all elements with Window PostMessage enabled.

Added missing OmniOut dependencies that were introduced to OmniStudio.

PS v240.13.910.80.6 (Winter 2023)

910.80.6

Jan 26, 2023

Fixed issue: Custom labels aren't shown after deployment because the FlexCard local compiler doesn't compile them correctly.

PS v236.2.21.910.72.4

910.72.4

Jan 26, 2023

Fixed issue: Selecting a new child card or changing the existing child card resets the inputs and data node value.

PS 240.12.910.80.5 (Winter 2023)

910.80.5

Jan 19, 2023

Fixed issue: If text between % characters doesn't match a JSON node name, the text and surrounding % characters should be left alone. Instead, they're removed from the string.

PS 238.25.910.75.5 (Summer 2022)

910.75.5

Jan 19, 2023

Fixed issue: Value of Messaging component in OmniScript data JSON is incorrectly reported as null.

PS 240.11.910.80.4 (Winter 2023)

910.80.4

Jan 10, 2023

New feature: DocuSign OAuth 2.0 is supported.

Fixed issue: Deleting a DataRaptor version clears data in other versions, including the active version.

PS 240.9.910.80.2 (Winter 2023)

910.80.2

Dec 8, 2022

Fixed issue: The Vlocity Build Tool doesn't compile FlexCard LWCs as expected because the namespace is incorrect and a dependency isn't installed.

PS 238.21.910.75.4 (Summer 2022)

910.75.4

Nov 23, 2022

Fixed issue: If text between % characters doesn't match a JSON node name, the text and surrounding % characters should be left alone but are removed from the string instead.

PS 240.5.910.80 (Winter 2023)

910.80

Nov 2, 2022

Fixed issues: The NVDA or JAWS screen reader and the DateTimePicker base LWC calendar GUI report different dates. Opening the FlexCard or OmniScript Designer when LWS is enabled may fail with the error Can't send message to Frame: DOMException: Failed to execute 'postMessage' on 'Window': #<Object> couldn't be cloned.

PS 240.0.910.79 (Winter 2023)

910.79

Oct 7, 2022

Includes OmniStudio for Vlocity Winter '23 updates.

PS 238.15.910.75.3 (Summer 2022)

910.75.3

Sep 29, 2022

Fixed issue: Upgrade prevents some OmniScripts from being activated due to LWC HTML file limits.

PS 238.12.910.75.2 (Summer 2022)

910.75.2

Sep 1, 2022

Fixed issues: Deactivating a reused child OmniScript on the Embedded OmniScript Page throws an Apex CPU Limit Error if the child has too many parents. Depending on whether useAppearanceObject is true or false, an OmniScript PDF Action generates a PDF file with field values that are either partially wrapped or invisible until clicked.

PS 236.2.13.910.72.3 (Spring 2022)

910.72.3

Sep 1, 2022

Fixed issue: Depending on whether useAppearanceObject is true or false, an OmniScript PDF Action generates a PDF file with field values that are either partially wrapped or invisible until clicked.

PS 236.2.6.910.72.2 Package (Spring 2022)

910.72.2

Jun 23, 2022

Fixed issue: When PDF files generated from Angular OmniScripts were opened in Adobe products, data in fillable fields was missing.

PS 238.1.910.75 Package (Summer 2022)

910.75

Jun 3, 2022

Includes OmniStudio for Vlocity Summer '22 updates.

PS 236.2.1.910.72.1 Package (Spring 2022)

910.72.1

Apr 25, 2022

Fixed issues: A custom LWC in a child OmniScript that called (this.omniNextStep()) advanced the parent OmniScript instead of the child. When an OmniScript step displayed a message about missing or invalid data, an unnecessary Sorry to interrupt pop-up appeared.

PS 236.2.910.72 Package (Spring 2022)

910.72

Apr 4, 2022

Fixed issues: Newport wasn't loaded in communities with no URL prefix. The lightning record page view and embedded OmniScript preview showed different numbers of FlexCards. FlexCards embedded in OmniScripts weren't responsive in lightning record pages. Repeatable Blocks didn't refresh with new data subsets. Rollback IP Changes was enabled by default.

PS 234.4.910.69.1 (Winter 2022)

910.69.1

Mar 17, 2022

Fixed issues: The lightning record page view and embedded OmniScript preview showed different numbers of FlexCards. FlexCards embedded in OmniScripts weren't responsive in lightning record pages. Edit Blocks didn't refresh with new data subsets. OmniScripts launched from the utility bar didn't load correctly.

PS 236.0.910.71 Package (Spring 2022)

910.71

Mar 1, 2022

New customers with Contract Lifecycle Management Document Generation licenses can enable server-side document generation without contacting Salesforce support.

PS 234.3.1.910.69 Package (Winter 2022)

910.69

Feb 14, 2022

Fixed issue: OmniScript Time elements weren't rendered. A missing oldDate variable in the timepicker LWC was responsible.

PS 234.3.910.68 Package (Winter 2022)

910.68

Feb 10, 2022

Fixed issues: Moving to the previous step in an Omniscript caused the Date/Time element to add an hour to the time field (a daylight savings time calculation in the daytimepicker LWC was responsible). In the prescreening OmniScript, checkboxes and text overlapped.

PS 234 Package (Winter 2022)

910.67

Oct 29, 2021

With the proper licenses, server-side document generation is available in Contract Lifecycle Management.

PS 232.0.910.66 Package (Summer 2021)

910.66

Jun 22, 2021

Server-side document generation is a pilot feature in Contract Lifecycle Management.

PS 230.0.910.63 Package (Spring 2021)

910.63

Mar 30, 2021

PS 108.0.2.910.56.2 Package (Spring 2020)

910.56.2

Mar 25, 2021

PS 109.0.910.61 Package (Winter 2021)

910.61

Oct 30, 2020

Trailing documents are supported on Accounts and many other objects, which allows Community and internal users to upload documents.

PS 108.0.1.910.56.1 Package (Spring 2020)

910.56

Sep 25, 2020

The Application Reference Number is generated for Guest Users and displays after you submit the application.

PS 108.0.910.56 Package (Spring 2020)

910.56

May 28, 2020

Contains fixes and enhancements including Lightning Web Components.