Releases: vlocityinc/vlocity_build
v1.15.3
New in v1.15.0
Support for OmniStudio Standard Objects
- OmniScript
- DataRaptor
- FlexCards
- Integration Procedures
- Decision Matrix
- Expression Set
Initial Support for OmniScript / FlexCards Local Compilation
This is only supported for Package Versions Spring '22+.
To set up the local compile you will need to request a Username and Password for the private Vlocity NPM Repo. If you have previously used OmniOut then it is the same credentials.
If you do not have credentials Request an NPM repository access key from your Vlocity customer representative by filing a support case with the subject: "Request for Access Key to Vlocity's Private NPM Repository at https://repo.vlocity.com/repository/vlocity-public/ for using OmniOut / IDX CLI".
The easiest way to set it up is to add the credentials to an .npmrc file in the User's home directory of your machine.
//repo.vlocity.com/repository/vlocity-public/:username=USERNAME
//repo.vlocity.com/repository/vlocity-public/:_password="PASSWORD"
You can also add to your job file the following:
npmAuthKey: KEYIt will automatically use the correct compiler based on your managed package version.
Recent Minor Changes
v1.15.1 - Fix for "Could not find a match for URL" error where namespace became corrupt when ECONNRESET error in REST
v1.15.2 - Add Charge Measurement to Queries
v1.15.3 - Fix for OutputDataLong in MatrixVersion and changes for Git Based Deploy to work with OmniStudio Standard Data Model
v1.15.2
New in v1.15.0
Support for OmniStudio Standard Objects
- OmniScript
- DataRaptor
- FlexCards
- Integration Procedures
- Decision Matrix
- Expression Set
Initial Support for OmniScript / FlexCards Local Compilation
This is only supported for Package Versions Spring '22+.
To set up the local compile you will need to request a Username and Password for the private Vlocity NPM Repo. If you have previously used OmniOut then it is the same credentials.
If you do not have credentials Request an NPM repository access key from your Vlocity customer representative by filing a support case with the subject: "Request for Access Key to Vlocity's Private NPM Repository at https://repo.vlocity.com/repository/vlocity-public/ for using OmniOut / IDX CLI".
The easiest way to set it up is to add the credentials to an .npmrc file in the User's home directory of your machine.
//repo.vlocity.com/repository/vlocity-public/:username=USERNAME
//repo.vlocity.com/repository/vlocity-public/:_password="PASSWORD"
You can also add to your job file the following:
npmAuthKey: KEYIt will automatically use the correct compiler based on your managed package version.
Recent Minor Changes
v1.15.1 - Fix for "Could not find a match for URL" error where namespace became corrupt when ECONNRESET error in REST
v1.15.2 - Add Charge Measurement to Queries
v1.15.1
New in v1.15.0
Support for OmniStudio Standard Objects
- OmniScript
- DataRaptor
- FlexCards
- Integration Procedures
- Decision Matrix
- Expression Set
Initial Support for OmniScript / FlexCards Local Compilation
This is only supported for Package Versions Spring '22+.
To set up the local compile you will need to request a Username and Password for the private Vlocity NPM Repo. If you have previously used OmniOut then it is the same credentials.
If you do not have credentials Request an NPM repository access key from your Vlocity customer representative by filing a support case with the subject: "Request for Access Key to Vlocity's Private NPM Repository at https://repo.vlocity.com/repository/vlocity-public/ for using OmniOut / IDX CLI".
The easiest way to set it up is to add the credentials to an .npmrc file in the User's home directory of your machine.
//repo.vlocity.com/repository/vlocity-public/:username=USERNAME
//repo.vlocity.com/repository/vlocity-public/:_password="PASSWORD"
You can also add to your job file the following:
npmAuthKey: KEYIt will automatically use the correct compiler based on your managed package version.
Recent Minor Changes
v1.15.1 - Fix for "Could not find a match for URL" error where namespace became corrupt when ECONNRESET error in REST
v1.15.0
New in v1.15.0
Support for OmniStudio Standard Objects
- OmniScript
- DataRaptor
- FlexCards
- Integration Procedures
- Decision Matrix
- Expression Set
Initial Support for OmniScript / FlexCards Local Compilation
This is only supported for Package Versions Spring '22+.
To set up the local compile you will need to request a Username and Password for the private Vlocity NPM Repo. If you have previously used OmniOut then it is the same credentials.
If you do not have credentials Request an NPM repository access key from your Vlocity customer representative by filing a support case with the subject: "Request for Access Key to Vlocity's Private NPM Repository at https://repo.vlocity.com/repository/vlocity-public/ for using OmniOut / IDX CLI".
The easiest way to set it up is to add the credentials to an .npmrc file in the User's home directory of your machine.
//repo.vlocity.com/repository/vlocity-public/:username=USERNAME
//repo.vlocity.com/repository/vlocity-public/:_password="PASSWORD"
You can also add to your job file the following:
npmAuthKey: KEYIt will automatically use the correct compiler based on your managed package version.
v1.14.19
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.9 - Fix typo in VlocityTrackingGroup Query
v1.14.10 - Linux Support for Puppeteer path
v1.14.11 - New debugging info in LWC Activation
v1.14.12 - Fix for exceptions causing LWC Activation to not set deploy to failed and show error
v1.14.13 - Better Namespace Handling in OmniOut Export
v1.14.14 - Forward proxy to puppeteer when set in httpProxy
v1.14.15 - Only set proxy when explicitly set
v1.14.16 - Change httpProxy to puppeteerHttpProxy for puppeteer only
v1.14.17 - Fix for Managed Package Upgrade issue with concurrent transactions
v1.14.18 - Only allow deployment after previous parent success
v1.14.19 - Fix for not showing the correct error message on missing references
v1.14.18
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.9 - Fix typo in VlocityTrackingGroup Query
v1.14.10 - Linux Support for Puppeteer path
v1.14.11 - New debugging info in LWC Activation
v1.14.12 - Fix for exceptions causing LWC Activation to not set deploy to failed and show error
v1.14.13 - Better Namespace Handling in OmniOut Export
v1.14.14 - Forward proxy to puppeteer when set in httpProxy
v1.14.15 - Only set proxy when explicitly set
v1.14.16 - Change httpProxy to puppeteerHttpProxy for puppeteer only
v1.14.17 - Fix for Managed Package Upgrade issue with concurrent transactions
v1.14.18 - Only allow deployment after previous parent success
v1.14.17
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.9 - Fix typo in VlocityTrackingGroup Query
v1.14.10 - Linux Support for Puppeteer path
v1.14.11 - New debugging info in LWC Activation
v1.14.12 - Fix for exceptions causing LWC Activation to not set deploy to failed and show error
v1.14.13 - Better Namespace Handling in OmniOut Export
v1.14.14 - Forward proxy to puppeteer when set in httpProxy
v1.14.15 - Only set proxy when explicitly set
v1.14.16 - Change httpProxy to puppeteerHttpProxy for puppeteer only
v1.14.17 - Fix for Managed Package Upgrade issue with concurrent transactions
v1.14.16
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.9 - Fix typo in VlocityTrackingGroup Query
v1.14.10 - Linux Support for Puppeteer path
v1.14.11 - New debugging info in LWC Activation
v1.14.12 - Fix for exceptions causing LWC Activation to not set deploy to failed and show error
v1.14.13 - Better Namespace Handling in OmniOut Export
v1.14.14 - Forward proxy to puppeteer when set in httpProxy
v1.14.15 - Only set proxy when explicitly set
v1.14.14 - Change httpProxy to puppeteerHttpProxy for puppeteer only
v1.14.15
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.9 - Fix typo in VlocityTrackingGroup Query
v1.14.10 - Linux Support for Puppeteer path
v1.14.11 - New debugging info in LWC Activation
v1.14.12 - Fix for exceptions causing LWC Activation to not set deploy to failed and show error
v1.14.13 - Better Namespace Handling in OmniOut Export
v1.14.14 - Forward proxy to puppeteer when set in httpProxy
v1.14.15 - Only set proxy when explicitly set
v1.14.14
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.9 - Fix typo in VlocityTrackingGroup Query
v1.14.10 - Linux Support for Puppeteer path
v1.14.11 - New debugging info in LWC Activation
v1.14.12 - Fix for exceptions causing LWC Activation to not set deploy to failed and show error
v1.14.13 - Better Namespace Handling in OmniOut Export
v1.14.14 - Forward proxy to puppeteer when set in httpProxy