Releases: vlocityinc/vlocity_build
v1.7.7
Recent Major Changes
v1.7 - OmniScript and IntegrationProcedure
The OmniScript and IntegrationProcedure DataPacks have been modified to remove the Order and Level fields which previously controlled how the OmniScript Elements were ordered in the UI. Now the Elements__c Array in the OmniScript _DataPack.json file is ordered in the display order of the UI.
This change will affect any newly exported OmniScript and IntegrationProcedure, and all files in the newly exported DataPacks should be committed to version control.
This change can be applied to all OmniScripts and IntegrationProcedures immediately by running the refreshProject command.
All existing data is still compatible, and issues will only arise when an OmniScript or IntegrationProcedure exported with Vlocity Build 1.7+ is deployed with an earlier version of the Vlocity Build Tool.
Please ensure everyone on your project is using the same version of this build tool.
Recent Features
v1.7 - OmniScript and IntegrationProcedure
The OmniScript and IntegrationProcedure DataPacks have been modified to remove the Order and Level. This means that merging changes for these objects is now much easier.
v1.7 - SFDX
Authentication with Salesforce DX credentials is now possible. Use -sfdx.username to use a Salesforce DX Authorized Org for vlocity commands. Once you are passing this parameter you will not need a password or any other propertyfile information. The Salesforce DX Authorization from sfdx force:org:display -u <username> will handle all the information. Passing an alias will work as well.
Recent Minor Changes
1.7.6 - Add Key Deploy as better than manifest.
1.7.7 - Fix issue with Order of Deployment for RuleAssignments.
v1.7.6
Recent Major Changes
v1.7 - OmniScript and IntegrationProcedure
The OmniScript and IntegrationProcedure DataPacks have been modified to remove the Order and Level fields which previously controlled how the OmniScript Elements were ordered in the UI. Now the Elements__c Array in the OmniScript _DataPack.json file is ordered in the display order of the UI.
This change will affect any newly exported OmniScript and IntegrationProcedure, and all files in the newly exported DataPacks should be committed to version control.
This change can be applied to all OmniScripts and IntegrationProcedures immediately by running the refreshProject command.
All existing data is still compatible, and issues will only arise when an OmniScript or IntegrationProcedure exported with Vlocity Build 1.7+ is deployed with an earlier version of the Vlocity Build Tool.
Please ensure everyone on your project is using the same version of this build tool.
Recent Features
v1.7 - OmniScript and IntegrationProcedure
The OmniScript and IntegrationProcedure DataPacks have been modified to remove the Order and Level. This means that merging changes for these objects is now much easier.
v1.7 - SFDX
Authentication with Salesforce DX credentials is now possible. Use -sfdx.username to use a Salesforce DX Authorized Org for vlocity commands. Once you are passing this parameter you will not need a password or any other propertyfile information. The Salesforce DX Authorization from sfdx force:org:display -u <username> will handle all the information. Passing an alias will work as well.
Recent Minor Changes
Add Key Deploy as better than manifest.
v1.7.5
Recent Major Changes
v1.7 - OmniScript and IntegrationProcedure
The OmniScript and IntegrationProcedure DataPacks have been modified to remove the Order and Level fields which previously controlled how the OmniScript Elements were ordered in the UI. Now the Elements__c Array in the OmniScript _DataPack.json file is ordered in the display order of the UI.
This change will affect any newly exported OmniScript and IntegrationProcedure, and all files in the newly exported DataPacks should be committed to version control.
This change can be applied to all OmniScripts and IntegrationProcedures immediately by running the refreshProject command.
All existing data is still compatible, and issues will only arise when an OmniScript or IntegrationProcedure exported with Vlocity Build 1.7+ is deployed with an earlier version of the Vlocity Build Tool.
Please ensure everyone on your project is using the same version of this build tool.
Recent Features
v1.7 - OmniScript and IntegrationProcedure
The OmniScript and IntegrationProcedure DataPacks have been modified to remove the Order and Level. This means that merging changes for these objects is now much easier.
v1.7 - SFDX
Authentication with Salesforce DX credentials is now possible. Use -sfdx.username to use a Salesforce DX Authorized Org for vlocity commands. Once you are passing this parameter you will not need a password or any other propertyfile information. The Salesforce DX Authorization from sfdx force:org:display -u <username> will handle all the information. Passing an alias will work as well.
v1.6.3
v1.6.1
** Changes to Enterprise Product Catalog DataPacks **
The Product2 DataPack has been modified to include all Pricebook and PriceList Entries for the Product. This means that a Product can be migrated from one org to another along with its Pricing Information without migrating the other Products in the Pricebook and Price List.
Running packUpdateSettings and re-exporting the Product2, Pricebook and PriceList is necessary to migrate to the new format, however existing data should still be deployable with the new changes.
If you have any issues with these changes you can install the previous version of the tool with:
npm install --global https://github.com/vlocityinc/vlocity_build#v1.5.7All Changes
Move PriceListEntry__c from PriceList to Product2
Move PricebookEntry from Pricebook to Product2
Fix OmniScript Pagination Issue
Better ProductChildItem filtering.
Updates to clean data for ProductChildItem
Add Error Log
Fix Exit Code
Fix removing UrlLong
v1.6.0
** Changes to Enterprise Product Catalog DataPacks **
The Product2 DataPack has been modified to include all Pricebook and PriceList Entries for the Product. This means that a Product can be migrated from one org to another along with its Pricing Information without migrating the other Products in the Pricebook and Price List.
Running packUpdateSettings and re-exporting the Product2, Pricebook and PriceList is necessary to migrate to the new format, however existing data should still be deployable with the new changes.
If you have any issues with these changes you can install the previous version of the tool with:
npm install --global https://github.com/vlocityinc/vlocity_build#v1.5.7All Changes
Move PriceListEntry__c from PriceList to Product2
Move PricebookEntry from Pricebook to Product2
Fix OmniScript Pagination Issue
Better ProductChildItem filtering.
Updates to clean data for ProductChildItem
Add Error Log
Fix Exit Code
Fix removing UrlLong