Releases: vlocityinc/vlocity_build
v1.9.4
v1.9 - Auto Update Restricted Picklists, Support for Large Matrix and OmniScripts, Auto Re-Activate OmniScripts with Embedded Templates, Auto Retry, Stale References Check, Performance Enhancements
Auto Update Restricted Picklists
By default the Vlocity Build Tool will automatically add Restircted Picklist values to the fields that are being deployed to. This makes metadata changes across orgs for Vlocity Managed Package fields automatically propagate and eliminates errors due to this missing metadata. To turn off this feature add autoFixPicklists: false to your Job File. Does not work for Managed Global Value Sets - Like Vlocity's CurrencyCode field.
Support for Large Calculation Matrix and OmniScripts
Large Calculation Matrix which would take a long time to deploy and OmniScripts which could previously fail due to heap size issues, will now be deployed through Salesforce Bulk Uploads to eliminate potential issues.
Auto Re-Activate OmniScripts with Embedded Templates
When VlocityUITemplates that can be embedded in OmniScripts are deployed you now have the option of enabling a job that will reactivate all currently active OmniScripts post deploy. To enable this feature add reactivateOmniScriptsWhenEmbeddedTemplateFound: true. Note: This will run activate for all OmniScripts and for now requires that you are logged in via SFDX Authentication.
Fix Reusable OmniScripts embedded in multiple other OmniScripts from failing Activation
Previously if activating a Reusable OmniScript caused too many other OmniScripts to activate it would fail. Note: This requires that you are logged in via SFDX Authentication.
Auto Retry
Auto Retry will enable the Vlocity Build Tool to retry errors which may have been caused by incorrect deploy order or transient issues. Add autoRetryErrors: true to your Job File.
Stale References Check
Use the new command vlocity checkStaleObjects to ensure that all references in your project exist in either the org or locally. This is meant to ensure that you will see any missing reference errors before your deployment.
VlocityUITemplate SCSS Includes now Auto Export
When another VlocityUITemplate includes references to a SCSS Mixin or Variables VlocityUITemplate it will automatically be exported as a dependency.
Performance Enhancements
Elimination of a wasteful file writing process and more reliance on Node Async Processing will improve performance for larger projects.
Global Key Changes
AttributeCategory__c, CalculationMatrixVersion__c, CalculationMatrix__c, CalculationProcedureVersion__c, CalculationProcedure__c, DRBundle__c now use their unique field of Name or Code as the GlobalKey__c field.
Recent Minor Changes
v1.9.1 - Replace trimStart with trim as trimStart is only Node 10+.
v1.9.2 - Disable Bulk Upload of Matrix
v1.9.3 - Fix Bulk Upload of Matrix ending with "unhashed" rows
v1.9.4 - No code changes. Fix for missing file in executables.
v1.9.3
v1.9 - Auto Update Restricted Picklists, Support for Large Matrix and OmniScripts, Auto Re-Activate OmniScripts with Embedded Templates, Auto Retry, Stale References Check, Performance Enhancements
Auto Update Restricted Picklists
By default the Vlocity Build Tool will automatically add Restircted Picklist values to the fields that are being deployed to. This makes metadata changes across orgs for Vlocity Managed Package fields automatically propagate and eliminates errors due to this missing metadata. To turn off this feature add autoFixPicklists: false to your Job File. Does not work for Managed Global Value Sets - Like Vlocity's CurrencyCode field.
Support for Large Calculation Matrix and OmniScripts
Large Calculation Matrix which would take a long time to deploy and OmniScripts which could previously fail due to heap size issues, will now be deployed through Salesforce Bulk Uploads to eliminate potential issues.
Auto Re-Activate OmniScripts with Embedded Templates
When VlocityUITemplates that can be embedded in OmniScripts are deployed you now have the option of enabling a job that will reactivate all currently active OmniScripts post deploy. To enable this feature add reactivateOmniScriptsWhenEmbeddedTemplateFound: true. Note: This will run activate for all OmniScripts and for now requires that you are logged in via SFDX Authentication.
Fix Reusable OmniScripts embedded in multiple other OmniScripts from failing Activation
Previously if activating a Reusable OmniScript caused too many other OmniScripts to activate it would fail. Note: This requires that you are logged in via SFDX Authentication.
Auto Retry
Auto Retry will enable the Vlocity Build Tool to retry errors which may have been caused by incorrect deploy order or transient issues. Add autoRetryErrors: true to your Job File.
Stale References Check
Use the new command vlocity checkStaleObjects to ensure that all references in your project exist in either the org or locally. This is meant to ensure that you will see any missing reference errors before your deployment.
VlocityUITemplate SCSS Includes now Auto Export
When another VlocityUITemplate includes references to a SCSS Mixin or Variables VlocityUITemplate it will automatically be exported as a dependency.
Performance Enhancements
Elimination of a wasteful file writing process and more reliance on Node Async Processing will improve performance for larger projects.
Global Key Changes
AttributeCategory__c, CalculationMatrixVersion__c, CalculationMatrix__c, CalculationProcedureVersion__c, CalculationProcedure__c, DRBundle__c now use their unique field of Name or Code as the GlobalKey__c field.
Recent Minor Changes
v1.9.1 - Replace trimStart with trim as trimStart is only Node 10+.
v1.9.2 - Disable Bulk Upload of Matrix
v1.9.3 - Fix Bulk Upload of Matrix ending with "unhashed" rows
v1.9.2
v1.9 - Auto Update Restricted Picklists, Support for Large Matrix and OmniScripts, Auto Re-Activate OmniScripts with Embedded Templates, Auto Retry, Stale References Check, Performance Enhancements
Auto Update Restricted Picklists
By default the Vlocity Build Tool will automatically add Restircted Picklist values to the fields that are being deployed to. This makes metadata changes across orgs for Vlocity Managed Package fields automatically propagate and eliminates errors due to this missing metadata. To turn off this feature add autoFixPicklists: false to your Job File. Does not work for Managed Global Value Sets - Like Vlocity's CurrencyCode field.
Support for Large Calculation Matrix and OmniScripts
Large Calculation Matrix which would take a long time to deploy and OmniScripts which could previously fail due to heap size issues, will now be deployed through Salesforce Bulk Uploads to eliminate potential issues.
Auto Re-Activate OmniScripts with Embedded Templates
When VlocityUITemplates that can be embedded in OmniScripts are deployed you now have the option of enabling a job that will reactivate all currently active OmniScripts post deploy. To enable this feature add reactivateOmniScriptsWhenEmbeddedTemplateFound: true. Note: This will run activate for all OmniScripts and for now requires that you are logged in via SFDX Authentication.
Fix Reusable OmniScripts embedded in multiple other OmniScripts from failing Activation
Previously if activating a Reusable OmniScript caused too many other OmniScripts to activate it would fail. Note: This requires that you are logged in via SFDX Authentication.
Auto Retry
Auto Retry will enable the Vlocity Build Tool to retry errors which may have been caused by incorrect deploy order or transient issues. Add autoRetryErrors: true to your Job File.
Stale References Check
Use the new command vlocity checkStaleObjects to ensure that all references in your project exist in either the org or locally. This is meant to ensure that you will see any missing reference errors before your deployment.
VlocityUITemplate SCSS Includes now Auto Export
When another VlocityUITemplate includes references to a SCSS Mixin or Variables VlocityUITemplate it will automatically be exported as a dependency.
Performance Enhancements
Elimination of a wasteful file writing process and more reliance on Node Async Processing will improve performance for larger projects.
Global Key Changes
AttributeCategory__c, CalculationMatrixVersion__c, CalculationMatrix__c, CalculationProcedureVersion__c, CalculationProcedure__c, DRBundle__c now use their unique field of Name or Code as the GlobalKey__c field.
Recent Minor Changes
v1.9.1 - Replace trimStart with trim as trimStart is only Node 10+.
v1.9.2 - Disable Bulk Upload of Matrix
v1.9.1
v1.9 - Auto Update Restricted Picklists, Support for Large Matrix and OmniScripts, Auto Re-Activate OmniScripts with Embedded Templates, Auto Retry, Stale References Check, Performance Enhancements
Auto Update Restricted Picklists
By default the Vlocity Build Tool will automatically add Restircted Picklist values to the fields that are being deployed to. This makes metadata changes across orgs for Vlocity Managed Package fields automatically propagate and eliminates errors due to this missing metadata. To turn off this feature add autoFixPicklists: false to your Job File. Does not work for Managed Global Value Sets - Like Vlocity's CurrencyCode field.
Support for Large Calculation Matrix and OmniScripts
Large Calculation Matrix which would take a long time to deploy and OmniScripts which could previously fail due to heap size issues, will now be deployed through Salesforce Bulk Uploads to eliminate potential issues.
Auto Re-Activate OmniScripts with Embedded Templates
When VlocityUITemplates that can be embedded in OmniScripts are deployed you now have the option of enabling a job that will reactivate all currently active OmniScripts post deploy. To enable this feature add reactivateOmniScriptsWhenEmbeddedTemplateFound: true. Note: This will run activate for all OmniScripts and for now requires that you are logged in via SFDX Authentication.
Fix Reusable OmniScripts embedded in multiple other OmniScripts from failing Activation
Previously if activating a Reusable OmniScript caused too many other OmniScripts to activate it would fail. Note: This requires that you are logged in via SFDX Authentication.
Auto Retry
Auto Retry will enable the Vlocity Build Tool to retry errors which may have been caused by incorrect deploy order or transient issues. Add autoRetryErrors: true to your Job File.
Stale References Check
Use the new command vlocity checkStaleObjects to ensure that all references in your project exist in either the org or locally. This is meant to ensure that you will see any missing reference errors before your deployment.
VlocityUITemplate SCSS Includes now Auto Export
When another VlocityUITemplate includes references to a SCSS Mixin or Variables VlocityUITemplate it will automatically be exported as a dependency.
Performance Enhancements
Elimination of a wasteful file writing process and more reliance on Node Async Processing will improve performance for larger projects.
Global Key Changes
AttributeCategory__c, CalculationMatrixVersion__c, CalculationMatrix__c, CalculationProcedureVersion__c, CalculationProcedure__c, DRBundle__c now use their unique field of Name or Code as the GlobalKey__c field.
Recent Minor Changes
v1.9.1 - Replace trimStart with trim as trimStart is only Node 10+.
v1.9.0
v1.9 - Auto Update Restricted Picklists, Support for Large Matrix and OmniScripts, Auto Re-Activate OmniScripts with Embedded Templates, Auto Retry, Stale References Check, Performance Enhancements
Auto Update Restricted Picklists
By default the Vlocity Build Tool will automatically add Restircted Picklist values to the fields that are being deployed to. This makes metadata changes across orgs for Vlocity Managed Package fields automatically propagate and eliminates errors due to this missing metadata. To turn off this feature add autoFixPicklists: false to your Job File. Does not work for Managed Global Value Sets - Like Vlocity's CurrencyCode field.
Support for Large Calculation Matrix and OmniScripts
Large Calculation Matrix which would take a long time to deploy and OmniScripts which could previously fail due to heap size issues, will now be deployed through Salesforce Bulk Uploads to eliminate potential issues.
Auto Re-Activate OmniScripts with Embedded Templates
When VlocityUITemplates that can be embedded in OmniScripts are deployed you now have the option of enabling a job that will reactivate all currently active OmniScripts post deploy. To enable this feature add reactivateOmniScriptsWhenEmbeddedTemplateFound: true. Note: This will run activate for all OmniScripts and for now requires that you are logged in via SFDX Authentication.
Fix Reusable OmniScripts embedded in multiple other OmniScripts from failing Activation
Previously if activating a Reusable OmniScript caused too many other OmniScripts to activate it would fail. Note: This requires that you are logged in via SFDX Authentication.
Auto Retry
Auto Retry will enable the Vlocity Build Tool to retry errors which may have been caused by incorrect deploy order or transient issues. Add autoRetryErrors: true to your Job File.
Stale References Check
Use the new command vlocity checkStaleObjects to ensure that all references in your project exist in either the org or locally. This is meant to ensure that you will see any missing reference errors before your deployment.
VlocityUITemplate SCSS Includes now Auto Export
When another VlocityUITemplate includes references to a SCSS Mixin or Variables VlocityUITemplate it will automatically be exported as a dependency.
Performance Enhancements
Elimination of a wasteful file writing process and more reliance on Node Async Processing will improve performance for larger projects.
Global Key Changes
AttributeCategory__c, CalculationMatrixVersion__c, CalculationMatrix__c, CalculationProcedureVersion__c, CalculationProcedure__c, DRBundle__c now use their unique field of Name or Code as the GlobalKey__c field.
v1.8.11
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.6 - Fix exception on null error messages
v1.8.7 - Second Attempt to fix stalling on Deploy. Added some initial Incremental Deployment Mappings
v1.8.8 - Readme and cleanData.js small changes
v1.8.9 - Readme only changes
v1.8.10 - Fix gitCheck during Export causing no changes to be found and blocking command
v.18.11 - Fix exception when no gitCheck info found
v1.8.10
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.6 - Fix exception on null error messages
v1.8.7 - Second Attempt to fix stalling on Deploy. Added some initial Incremental Deployment Mappings
v1.8.8 - Readme and cleanData.js small changes
v1.8.9 - Readme only changes
v1.8.10 - Fix gitCheck during Export causing no changes to be found and blocking command
v1.8.8
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.6 - Fix exception on null error messages
v1.8.7 - Second Attempt to fix stalling on Deploy. Added some initial Incremental Deployment Mappings
v1.8.8 - Readme and cleanData.js small changes
v1.8.7
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.6 - Fix exception on null error messages
v1.8.7 - Second Attempt to fix stalling on Deploy. Added some initial Incremental Deployment Mappings
v1.8.6
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.6 - Fix exception on null error messages