Releases: vlocityinc/vlocity_build
v1.8.5
v1.8 - Delta Deploys / Exports, Error Message Enhancements, Git Changes Based Deploys, and Auto Update Settings
Delta Deploys / Exports
Add deltaCheck: true to your job file to enable checking to see if there are changes to the the items you are about to deploy or export. This check will run much faster than the getDiffsAndDeploy check, but at this time 100% consistency is not gauranteed for all DataPack Types. The checks will error on the side of caution and run the deploy /export automatically for any DataPack Type that may have changes.
Error Message Enhancements
Error messages have been improved to give more instrution on how to fix issues. An example change is as follows:
Previous:
Error >> AttributeCategory/ATTRIBUTE_CATEGORY --- ATTRIBUTE_CATEGORY --- duplicate value found: <unknown> duplicates value on record with id: <unknown>
New:
Error >> AttributeCategory/ATTRIBUTE_CATEGORY -- DataPack >> ATTRIBUTE_CATEGORY -- Error Message -- duplicate field value found: 100 on the field: vlocity_cmt__DisplaySequence__c on record with id: a0K0b00000XabWUEAZ -- Change the vlocity_cmt__DisplaySequence__c field value of the vlocity_cmt__AttributeCategory__c on record with id: a0K0b00000XabWUEAZ in the target org to resolve the issue.
Git Changes Based Deploys
Add gitCheck: true to your job file to enable checking what the latest git hash was before deploying to the target org. With this setting only the DataPacks that have changed between the previous git hash and the latest git hash will be deployed to the org.
Auto Update Settings
Add autoUpdateSettings: true to your job file to enable checking that you have the latest DataPack settings before every export and deploy. This check is very fast and it is advised that this is enabled.
Recent Minor Changes
v1.8.1 - Fix wrong exitCode when using JSON.
v1.8.2 - Fix for endless loop when switching from regular to Headers Only.
v1.8.3 - Fix issue with endlessly stalled loop
v1.8.4 - Change Products to Headers Only Again
v1.8.5 - Fix exception when invalid query name sent
v1.8.4
v1.8 - Delta Deploys / Exports, Error Message Enhancements, Git Changes Based Deploys, and Auto Update Settings
Delta Deploys / Exports
Add deltaCheck: true to your job file to enable checking to see if there are changes to the the items you are about to deploy or export. This check will run much faster than the getDiffsAndDeploy check, but at this time 100% consistency is not gauranteed for all DataPack Types. The checks will error on the side of caution and run the deploy /export automatically for any DataPack Type that may have changes.
Error Message Enhancements
Error messages have been improved to give more instrution on how to fix issues. An example change is as follows:
Previous:
Error >> AttributeCategory/ATTRIBUTE_CATEGORY --- ATTRIBUTE_CATEGORY --- duplicate value found: <unknown> duplicates value on record with id: <unknown>
New:
Error >> AttributeCategory/ATTRIBUTE_CATEGORY -- DataPack >> ATTRIBUTE_CATEGORY -- Error Message -- duplicate field value found: 100 on the field: vlocity_cmt__DisplaySequence__c on record with id: a0K0b00000XabWUEAZ -- Change the vlocity_cmt__DisplaySequence__c field value of the vlocity_cmt__AttributeCategory__c on record with id: a0K0b00000XabWUEAZ in the target org to resolve the issue.
Git Changes Based Deploys
Add gitCheck: true to your job file to enable checking what the latest git hash was before deploying to the target org. With this setting only the DataPacks that have changed between the previous git hash and the latest git hash will be deployed to the org.
Auto Update Settings
Add autoUpdateSettings: true to your job file to enable checking that you have the latest DataPack settings before every export and deploy. This check is very fast and it is advised that this is enabled.
Recent Minor Changes
v1.8.1 - Fix wrong exitCode when using JSON.
v1.8.2 - Fix for endless loop when switching from regular to Headers Only.
v1.8.3 - Fix issue with endlessly stalled loop
v1.8.4 - Change Products to Headers Only Again
v1.8.3
v1.8 - Delta Deploys / Exports, Error Message Enhancements, Git Changes Based Deploys, and Auto Update Settings
Delta Deploys / Exports
Add deltaCheck: true to your job file to enable checking to see if there are changes to the the items you are about to deploy or export. This check will run much faster than the getDiffsAndDeploy check, but at this time 100% consistency is not gauranteed for all DataPack Types. The checks will error on the side of caution and run the deploy /export automatically for any DataPack Type that may have changes.
Error Message Enhancements
Error messages have been improved to give more instrution on how to fix issues. An example change is as follows:
Previous:
Error >> AttributeCategory/ATTRIBUTE_CATEGORY --- ATTRIBUTE_CATEGORY --- duplicate value found: <unknown> duplicates value on record with id: <unknown>
New:
Error >> AttributeCategory/ATTRIBUTE_CATEGORY -- DataPack >> ATTRIBUTE_CATEGORY -- Error Message -- duplicate field value found: 100 on the field: vlocity_cmt__DisplaySequence__c on record with id: a0K0b00000XabWUEAZ -- Change the vlocity_cmt__DisplaySequence__c field value of the vlocity_cmt__AttributeCategory__c on record with id: a0K0b00000XabWUEAZ in the target org to resolve the issue.
Git Changes Based Deploys
Add gitCheck: true to your job file to enable checking what the latest git hash was before deploying to the target org. With this setting only the DataPacks that have changed between the previous git hash and the latest git hash will be deployed to the org.
Auto Update Settings
Add autoUpdateSettings: true to your job file to enable checking that you have the latest DataPack settings before every export and deploy. This check is very fast and it is advised that this is enabled.
Recent Minor Changes
v1.8.1 - Fix wrong exitCode when using JSON.
v1.8.2 - Fix for endless loop when switching from regular to Headers Only.
v1.8.3 - Fix issue with endlessly stalled loop
v1.8.2
v1.8 - Delta Deploys / Exports, Error Message Enhancements, Git Changes Based Deploys, and Auto Update Settings
Delta Deploys / Exports
Add deltaCheck: true to your job file to enable checking to see if there are changes to the the items you are about to deploy or export. This check will run much faster than the getDiffsAndDeploy check, but at this time 100% consistency is not gauranteed for all DataPack Types. The checks will error on the side of caution and run the deploy /export automatically for any DataPack Type that may have changes.
Error Message Enhancements
Error messages have been improved to give more instrution on how to fix issues. An example change is as follows:
Previous:
Error >> AttributeCategory/ATTRIBUTE_CATEGORY --- ATTRIBUTE_CATEGORY --- duplicate value found: <unknown> duplicates value on record with id: <unknown>
New:
Error >> AttributeCategory/ATTRIBUTE_CATEGORY -- DataPack >> ATTRIBUTE_CATEGORY -- Error Message -- duplicate field value found: 100 on the field: vlocity_cmt__DisplaySequence__c on record with id: a0K0b00000XabWUEAZ -- Change the vlocity_cmt__DisplaySequence__c field value of the vlocity_cmt__AttributeCategory__c on record with id: a0K0b00000XabWUEAZ in the target org to resolve the issue.
Git Changes Based Deploys
Add gitCheck: true to your job file to enable checking what the latest git hash was before deploying to the target org. With this setting only the DataPacks that have changed between the previous git hash and the latest git hash will be deployed to the org.
Auto Update Settings
Add autoUpdateSettings: true to your job file to enable checking that you have the latest DataPack settings before every export and deploy. This check is very fast and it is advised that this is enabled.
Recent Minor Changes
v1.8.1 - Fix wrong exitCode when using JSON.
v1.8.2 - Fix for endless loop when switching from regular to Headers Only.
v1.8.1
v1.8 - Delta Deploys / Exports, Error Message Enhancements, Git Changes Based Deploys, and Auto Update Settings
Delta Deploys / Exports
Add deltaCheck: true to your job file to enable checking to see if there are changes to the the items you are about to deploy or export. This check will run much faster than the getDiffsAndDeploy check, but at this time 100% consistency is not gauranteed for all DataPack Types. The checks will error on the side of caution and run the deploy /export automatically for any DataPack Type that may have changes.
Error Message Enhancements
Error messages have been improved to give more instrution on how to fix issues. An example change is as follows:
Previous:
Error >> AttributeCategory/ATTRIBUTE_CATEGORY --- ATTRIBUTE_CATEGORY --- duplicate value found: <unknown> duplicates value on record with id: <unknown>
New:
Error >> AttributeCategory/ATTRIBUTE_CATEGORY -- DataPack >> ATTRIBUTE_CATEGORY -- Error Message -- duplicate field value found: 100 on the field: vlocity_cmt__DisplaySequence__c on record with id: a0K0b00000XabWUEAZ -- Change the vlocity_cmt__DisplaySequence__c field value of the vlocity_cmt__AttributeCategory__c on record with id: a0K0b00000XabWUEAZ in the target org to resolve the issue.
Git Changes Based Deploys
Add gitCheck: true to your job file to enable checking what the latest git hash was before deploying to the target org. With this setting only the DataPacks that have changed between the previous git hash and the latest git hash will be deployed to the org.
Auto Update Settings
Add autoUpdateSettings: true to your job file to enable checking that you have the latest DataPack settings before every export and deploy. This check is very fast and it is advised that this is enabled.
Recent Minor Changes
v1.8.1 - Fix wrong exitCode when using JSON.
v1.8.0
v1.8 - Delta Deploys / Exports, Error Message Enhancements, Git Changes Based Deploys, and Auto Update Settings
Delta Deploys / Exports
Add deltaCheck: true to your job file to enable checking to see if there are changes to the the items you are about to deploy or export. This check will run much faster than the getDiffsAndDeploy check, but at this time 100% consistency is not gauranteed for all DataPack Types. The checks will error on the side of caution and run the deploy /export automatically for any DataPack Type that may have changes.
Error Message Enhancements
Error messages have been improved to give more instrution on how to fix issues. An example change is as follows:
Previous:
Error >> AttributeCategory/ATTRIBUTE_CATEGORY --- ATTRIBUTE_CATEGORY --- duplicate value found: <unknown> duplicates value on record with id: <unknown>
New:
Error >> AttributeCategory/ATTRIBUTE_CATEGORY -- DataPack >> ATTRIBUTE_CATEGORY -- Error Message -- duplicate field value found: 100 on the field: vlocity_cmt__DisplaySequence__c on record with id: a0K0b00000XabWUEAZ -- Change the vlocity_cmt__DisplaySequence__c field value of the vlocity_cmt__AttributeCategory__c on record with id: a0K0b00000XabWUEAZ in the target org to resolve the issue.
Git Changes Based Deploys
Add gitCheck: true to your job file to enable checking what the latest git hash was before deploying to the target org. With this setting only the DataPacks that have changed between the previous git hash and the latest git hash will be deployed to the org.
Auto Update Settings
Add autoUpdateSettings: true to your job file to enable checking that you have the latest DataPack settings before every export and deploy. This check is very fast and it is advised that this is enabled.
v1.7.11
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.
1.7.8 - Fix DocumentTemplates to only export Active by default.
1.7.9 - Fix ContentVersion not saving correctly.
1.7.10 - Allow sending folder name as manifest key
1.7.11 - Fix for duplicating RuleAssignments on Deploy
v1.7.10
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.
1.7.8 - Fix DocumentTemplates to only export Active by default.
1.7.9 - Fix ContentVersion not saving correctly.
1.7.10 - Allow sending folder name as manifest key
v1.7.9
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.
1.7.8 - Fix DocumentTemplates to only export Active by default.
1.7.9 - Fix ContentVersion not saving correctly.
v1.7.8
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.
1.7.8 - Fix DocumentTemplates to only export Active by default.