Releases: vlocityinc/vlocity_build
v1.14.8
v1.14 - OmniScript and Cards LWC Compile on Deploy
The Vlocity Build Tool will now automatically compile and deploy OmniScript and Cards LWCs after Activation through Puppeteer or Chrome installed on your local machine. To install puppeteer into a build machine or locally run:
npm install puppeteer -g
If your system has Chrome installed VBT will automatically start a headless chrome session, authenticate to the deployment org, and use a page in the Vlocity Managed Package to compile and deploy the OmniScript or Card.
To disable this feature add to your Job File:
ignoreLWCActivationOS: true
ignoreLWCActivationCards: true
Otherwise these are now on by default.
Added Support to Retrieve LWC OmniOut OmniScripts
vlocity -propertyfile <filepath> -job <filepath> runJavaScript -js lwcOmniOutRetrieve.js
Recent Minor Changes
v1.14.1 - Added LWC OmniOut Command
v1.14.2 - Re-add missing configuration.
v1.14.3 - Add order by to Pagination query
v1.14.4 - Additional Logging on Failures
v1.14.5 - Remove AttributeName from AttributeAssignment Filters
v1.14.6 - Fix FlexCards on failure exception
v1.14.7 - Fix for OS / Cards LWC Activation and JSON output for retry result
v1.14.8 - Add additional job file settings as available for passing in as part of the command.
v1.14.7
v1.14 - OmniScript and Cards LWC Compile on Deploy
The Vlocity Build Tool will now automatically compile and deploy OmniScript and Cards LWCs after Activation through Puppeteer or Chrome installed on your local machine. To install puppeteer into a build machine or locally run:
npm install puppeteer -g
If your system has Chrome installed VBT will automatically start a headless chrome session, authenticate to the deployment org, and use a page in the Vlocity Managed Package to compile and deploy the OmniScript or Card.
To disable this feature add to your Job File:
ignoreLWCActivationOS: true
ignoreLWCActivationCards: true
Otherwise these are now on by default.
Added Support to Retrieve LWC OmniOut OmniScripts
vlocity -propertyfile <filepath> -job <filepath> runJavaScript -js lwcOmniOutRetrieve.js
Recent Minor Changes
v1.14.1 - Added LWC OmniOut Command
v1.14.2 - Re-add missing configuration.
v1.14.3 - Add order by to Pagination query
v1.14.4 - Additional Logging on Failures
v1.14.5 - Remove AttributeName from AttributeAssignment Filters
v1.14.6 - Fix FlexCards on failure exception
v1.14.7 - Fix for OS / Cards LWC Activation and JSON output for retry result
v1.14.6
v1.14 - OmniScript and Cards LWC Compile on Deploy
The Vlocity Build Tool will now automatically compile and deploy OmniScript and Cards LWCs after Activation through Puppeteer or Chrome installed on your local machine. To install puppeteer into a build machine or locally run:
npm install puppeteer -g
If your system has Chrome installed VBT will automatically start a headless chrome session, authenticate to the deployment org, and use a page in the Vlocity Managed Package to compile and deploy the OmniScript or Card.
To disable this feature add to your Job File:
ignoreLWCActivationOS: true
ignoreLWCActivationCards: true
Otherwise these are now on by default.
Added Support to Retrieve LWC OmniOut OmniScripts
vlocity -propertyfile <filepath> -job <filepath> runJavaScript -js lwcOmniOutRetrieve.js
Recent Minor Changes
v1.14.1 - Added LWC OmniOut Command
v1.14.2 - Re-add missing configuration.
v1.14.3 - Add order by to Pagination query
v1.14.4 - Additional Logging on Failures
v1.14.5 - Remove AttributeName from AttributeAssignment Filters
v1.14.6 - Fix FlexCards on failure exception
v1.14.5
v1.14 - OmniScript and Cards LWC Compile on Deploy
The Vlocity Build Tool will now automatically compile and deploy OmniScript and Cards LWCs after Activation through Puppeteer or Chrome installed on your local machine. To install puppeteer into a build machine or locally run:
npm install puppeteer -g
If your system has Chrome installed VBT will automatically start a headless chrome session, authenticate to the deployment org, and use a page in the Vlocity Managed Package to compile and deploy the OmniScript or Card.
To disable this feature add to your Job File:
ignoreLWCActivationOS: true
ignoreLWCActivationCards: true
Otherwise these are now on by default.
Added Support to Retrieve LWC OmniOut OmniScripts
vlocity -propertyfile <filepath> -job <filepath> runJavaScript -js lwcOmniOutRetrieve.js
Recent Minor Changes
v1.14.1 - Added LWC OmniOut Command
v1.14.2 - Re-add missing configuration.
v1.14.3 - Add order by to Pagination query
v1.14.4 - Additional Logging on Failures
v1.14.5 - Remove AttributeName from AttributeAssignment Filters
v1.14.4
v1.14 - OmniScript and Cards LWC Compile on Deploy
The Vlocity Build Tool will now automatically compile and deploy OmniScript and Cards LWCs after Activation through Puppeteer or Chrome installed on your local machine. To install puppeteer into a build machine or locally run:
npm install puppeteer -g
If your system has Chrome installed VBT will automatically start a headless chrome session, authenticate to the deployment org, and use a page in the Vlocity Managed Package to compile and deploy the OmniScript or Card.
To disable this feature add to your Job File:
ignoreLWCActivationOS: true
ignoreLWCActivationCards: true
Otherwise these are now on by default.
Added Support to Retrieve LWC OmniOut OmniScripts
vlocity -propertyfile <filepath> -job <filepath> runJavaScript -js lwcOmniOutRetrieve.js
Recent Minor Changes
v1.14.1 - Added LWC OmniOut Command
v1.14.2 - Re-add missing configuration.
v1.14.3 - Add order by to Pagination query
v1.14.4 - Additional Logging on Failures
v1.14.3
v1.14 - OmniScript and Cards LWC Compile on Deploy
The Vlocity Build Tool will now automatically compile and deploy OmniScript and Cards LWCs after Activation through Puppeteer or Chrome installed on your local machine. To install puppeteer into a build machine or locally run:
npm install puppeteer -g
If your system has Chrome installed VBT will automatically start a headless chrome session, authenticate to the deployment org, and use a page in the Vlocity Managed Package to compile and deploy the OmniScript or Card.
To disable this feature add to your Job File:
ignoreLWCActivationOS: true
ignoreLWCActivationCards: true
Otherwise these are now on by default.
Added Support to Retrieve LWC OmniOut OmniScripts
vlocity -propertyfile <filepath> -job <filepath> runJavaScript -js lwcOmniOutRetrieve.js
Recent Minor Changes
v1.14.1 - Added LWC OmniOut Command
v1.14.2 - Re-add missing configuration.
v1.14.3 - Add order by to Pagination query
v1.14.2
v1.14 - OmniScript and Cards LWC Compile on Deploy
The Vlocity Build Tool will now automatically compile and deploy OmniScript and Cards LWCs after Activation through Puppeteer or Chrome installed on your local machine. To install puppeteer into a build machine or locally run:
npm install puppeteer -g
If your system has Chrome installed VBT will automatically start a headless chrome session, authenticate to the deployment org, and use a page in the Vlocity Managed Package to compile and deploy the OmniScript or Card.
To disable this feature add to your Job File:
ignoreLWCActivationOS: true
ignoreLWCActivationCards: true
Otherwise these are now on by default.
Added Support to Retrieve LWC OmniOut OmniScripts
vlocity -propertyfile <filepath> -job <filepath> runJavaScript -js lwcOmniOutRetrieve.js
Recent Minor Changes
v1.14.1 - Added LWC OmniOut Command
v1.14.2 - Re-add missing configuration.
v1.14.1
v1.14 - OmniScript and Cards LWC Compile on Deploy
The Vlocity Build Tool will now automatically compile and deploy OmniScript and Cards LWCs after Activation through Puppeteer or Chrome installed on your local machine. To install puppeteer into a build machine or locally run:
npm install puppeteer -g
If your system has Chrome installed VBT will automatically start a headless chrome session, authenticate to the deployment org, and use a page in the Vlocity Managed Package to compile and deploy the OmniScript or Card.
To disable this feature add to your Job File:
ignoreLWCActivationOS: true
ignoreLWCActivationCards: true
Otherwise these are now on by default.
Added Support to Retrieve LWC OmniOut OmniScripts
vlocity -propertyfile <filepath> -job <filepath> runJavaScript -js lwcOmniOutRetrieve.js
Recent Minor Changes
v1.14.1 - Added LWC OmniOut Command
v1.14.0
v1.14 - OmniScript and Cards LWC Compile on Deploy
The Vlocity Build Tool will now automatically compile and deploy OmniScript and Cards LWCs after Activation through Puppeteer or Chrome installed on your local machine. To install puppeteer into a build machine or locally run:
npm install puppeteer -g
If your system has Chrome installed VBT will automatically start a headless chrome session, authenticate to the deployment org, and use a page in the Vlocity Managed Package to compile and deploy the OmniScript or Card.
To disable this feature add to your Job File:
ignoreLWCActivationOS: true
ignoreLWCActivationCards: true
Otherwise these are now on by default.
v1.13.6
v1.13 - IDX Workbench Update - Process Profiler and Test Procedures
This update is primarily related to new features for IDX Workbench (formerly Vlocity DX). There were very few changes to VBT's core export or deployment capabilities.
Additional Documentation and release notes coming soon.
This update to VBT includes the following features and bug fixes:
- Support retrieving versions of calculation procedures using job file setting
separateCalculationProcedureVersions - New Test Procedure commands to run Vlocity Integration Procedure Tests as part of automation
- Fix Content Document Cleanup Issue
- Better account for Windows File Name Limits
Recent Minor Changes
v1.13.1 - Fix for Product Deployment with no Attribute Assignments throwing error
v1.13.2 - Fix for packBuildFile issue with DataPacks that reference other SObjects
v1.13.3 - When running packBuildFile the file will no longer be Pretty JSON
v1.13.4 - Add Matching Key for OrchestrationDependencyDefinition
v1.13.5 - Allow running packUpdateSettings when using sessionToken / authToken to authenticate
v1.13.6
- Fix for ApprovalProcess not getting listed in Salesforce Types
- Fix for Git commit not working for DataPack keys with spaces
- Add runAllTestProcedures target and add testKeys to CLI Arguments
- Fixes for OrchestrationScenario Merging
- Add pagination at 500 for Export of Attribute Assignments in Product2
- Remove AttributeAssignments and OverrideDefinitions being deployed in Pagination Scenarios
- Performance Enhancement for Product2 Export