Release Notes 22
ARM Release Notes 22.3
We would like to inform you about the End of Life (EOL) for ARM version 22.3. Per our support agreement, this version is now more than 365 days old and is no longer supported. As part of our ongoing commitment to providing the best possible experience for our users and maintaining the highest standards of security and performance, we have made the decision to discontinue support for ARM 22.3.
End of Life Date: April 1, 2024
What Does This Mean?
End of Support: As of April 1, 2024, we will no longer provide maintenance updates, bug fixes, or technical support for ARM 22.3. This includes both security and non-security updates.
Security Risks: Continuing to use ARM 22.3 after the end of support date may expose your system to potential security vulnerabilities, as we will no longer release security patches.
Upgrade Recommendations: We strongly recommend migrating to a supported version of ARM to ensure continued reliability, security, and performance. Our team is available to assist you with this transition process and provide guidance on your upgrade.
Accessing Resources: While official support for ARM 22.3 will no longer be available, you can still access existing resources such as documentation, knowledge base articles, and the Knowledge Hub for reference purposes.
Action Required:
To mitigate any potential risks associated with the EOL of 22.3, we urge you to take proactive steps towards upgrade immediately. Our customer success and support team are here to assist you every step of the way. Please reach out to your CSM to plan this work.
We understand that this transition may present challenges, and we sincerely apologize for any inconvenience it may cause. However, we believe that focusing our efforts on our latest offerings will ultimately benefit you with enhanced features, improved performance, and better security.
Thank you for your understanding and continued support.
December 2022 - Version 22.3 - New Features, Enhancements, Improvements and Changelogs
Date of release: 18 December 2022 Article last updated: 31 July 2023
New Features
1. Retention Policy
You can now define a data Retention Policy and choose how much data should be stored for how long. ARM will now be considerably quicker by eliminating outdated data. Clearing out old and useless data from the database and moving it to the archives keeps the application from underperforming and improves speed across all modules.
A weekly clean-up will ensure that the application runs smoothly. The default data retention period is set as 12 months which will be implemented with the release of ARM version 22.3. Admins can specify the duration of data retention in the history tables from the My Account section and change the retention period from 12 months to 6 months or 3 months. Read more →
2. Search, Group, and Filter CI Job List
Finding a CI Job has never been easier. Instead of scrolling through endless pages, you can search for a job or a group by simply typing the name in the new dropdown lists. You can further narrow the search results by combining these two options to look for a particular job within a group.
Additionally, the filter feature provides further options to narrow the search results by source type, date range, and more. Read more →
3. Ability to Abort a Vlocity Deployment
We just included new functionality to the ARM 22.3 version that allows users to terminate an ongoing Vlocity deployment process or abort it if get stuck. The Deployment History screen contains the Abort option, which allows you to terminate the deployment process.
Enhancements
1. Release Label Revamp
The revamp of the Release Label page is the feature of version 22.3 that stands out the most. This enhancement is actually a collection of multiple smaller enhancements, each of which is briefly discussed in this section.
While creating a release label, you can choose the specific period for which you want to retrieve the commit history instead of loading the entire commit history, which could take a really long time.
You can also create a release label while simultaneously creating a package simply by selecting a conveniently located checkbox on the same screen.
The selected revisions are also displayed on the same screen and updated dynamically as you select/unselect revisions.
Release labels are color-coded on the Release Label Summary screen for easier identification, and the search now provides leaner results.
2. Additional Metadata Support in Search and Substitute
Additional metadata types are now compatible with the Search and Substitute rule, allowing the application to use them for Deployments and Commits.
Until now, the Search and Substitute functionality only had the ability to select a metadata type and then perform the search for substrings across all members in that type. But now, you can select specific metadata members in a type and substitute values for that member(s).
This enhancement is also helpful when users want to add object permissions only to the production and not to the lower sandboxes.
It is also beneficial to have this feature so that the rules can be created and used in CI Jobs to do the replacements automatically, depending on the deployment settings in the CI Job. Read more →
3. Additional details in the Users Export List
Export List is a comprehensive list of all registered users with an organization. This list can be downloaded from the Users module. It includes details like the users' name, email, and title; and information about user accounts created, modified, deactivated, and deleted.
With the recent release, the Export List will include a few additional details related to the last login to ensure security and compliance. Details like the location, login type, IP address, coordinates, and the browser used.
The access level of users is not mentioned in the export list for security reasons, i.e., if any users are Admin or Super Admin, this will not be specified. The company can share this list, if required, with people both inside and outside their organization without jeopardizing the confidentiality of the access granted to the users. Read more →
4. Dataloader Clone process
In addition to providing a new name, Dataloader users can now specify a different Salesforce org as a source or destination for the operation while cloning an existing job. This helps the users to reuse the same job configuration with a different Salesforce org without going through the entire process again.
For the Extract operation, users have the option to edit the query corresponding to the new org selected. For Insert/Update/Upsert/Delete operations, users have the option to upload a different .CSV file instead of the original one. Validation is done to verify whether the object is available in the new org and also if the user edits the query for the cloned process. Read more →
Improvements
The
/syncbranchcommits
service is no longer supported. The users will no longer require Auto-sync functionality to create a release label. This simplifies the function's use and gets rid of unnecessary steps.For improved user experience, the metadata.zip file upload option has been added to the New Deployment page itself. When uploading large files, this is extremely useful.
The password policy is reduced from 13 previously used passwords not being allowed to 5 previously used passwords. This gives users more options while resetting their passwords after the three months period or if they forget their password.
Improvements have been made to VC Repo flow as well as to Salesforce Org flow. You can now run scans on a repo or an org to be tagged to the same project and run comparisons so that you have traceability across the scans. The comparison feature allows for every delta scanned to be compared with the baseline. Scans are run on the source, and the results are available in the Reports module. Users can trace the jobs run using the unique identifier. Click HERE to see a few points to note about these improvements.
Super Admin and the user currently logged in are disabled for ALL actions. They cannot be added, deleted, suspended, activated, deactivated, edited, or their roles delegated to other users. Super Admin is displayed at the top of the users' list for easy identification.
The Users module now displays the last login date and time of the users instead of the phone number, and the first and last names appear under the single Name column for better monitoring and tracking.
Super Admin can now enter the desired thread pool count while registering an ARM agent.
Customers can now request for Pendo and Full Story to be enabled or disabled for their instance. Simple toggle buttons to do this are added under the Product Analytics section on the Super User Accounts page. Only Super Admin will have access to this section.
In DataLoader,
The number of records that are going to be impacted by the specific operation (Extract, Insert, Update, Upsert, or Delete) is displayed as a message before the operation begins and also on the Summary screen as Records.
Filters have been added to differentiate between the mapped and unmapped fields when auto-map is selected.
Success and error count of records is displayed while the job is still in progress. Click HERE to read more about these improvements for each of the operations.
Changelogs
28 February 2024
(ARM v. 22.3.55)
Version Control
Merges are not being fetched when trying to create a release label for Vlocity components.
22.3
Code Fix
Use Case
Version Control
Unable to Commit the Action Overrides in Service Appointment Object
22.3
Code Fix
Use Case
28 January 2024
(ARM v. 22.3.54)
Deployment
Vlocity Deployment issue
QA Passed
22.3, 23.1
Code Fix
Use Case
Version Control
Not fetching merges when trying to create a release label for Vlocity components
QA Passed
22.3
Code Fix
Use Case
21 January 2024
(ARM v. 22.3.53)
Dataloader Pro
Issue while deploying promotions from QAT to PRD the rule set criteria is compressing the value while deploying it to RD
QA Passed
22.3 23.1
Code Fix
Use Case
Dataloader Pro
Issue on Feature Deployments
QA Passed
22.3 23.1
Code Fix
Use Case
14 January 2024
(ARM v. 22.3.52)
MODULE
SUMMARY
FIXVERSION
RESOLUTION
CAUSE
Admin
After baselining the branch, it did not pull all metadata for development.
22.3
Code Fix
Use Case
Deployments
Deployment status failed when deploying Vlocity components
22.3 23.1
Code Fix
Use Case
10 December 2023
(ARM 22.3.51)
nCino
User is unable to do nCino Feature Deployments * Requires documentation
23.1, 22.3
Code Fix
Use Case
Admin
Getting ‘null parameters’ error when clicking on save in the user’s section.
23.1, 22.3
Code Fix
Use Case
3 December 2023
(ARM v. 22.3.50)
Admin
Issue adding user mapping
22.3, 23.1
Code Fix
Use Case
Admin
nCino View Object Failing
NA
No Code Fix - Added Loggers
Data
Deployments
Org sync not completing
NA
No Code Fix - Added Loggers
Data
Dataloader
Corrected a spelling mistake in ARM steps.
23.1, 22.3
Code Fix
Use Case
Dataloader
Corrected data seeding error preventing upsert
23.1, 22.3
Code Fix
Use Case
nCino
On-premise testing: CI Job with template option failed due to "data and metadata retrieval failed” error
23.1, 22.3
Code Fix
Use Case
26 November 2023
(ARM v. 22.3.49)
CI Jobs
Post activities, particular job status showing as FAILED in ARM even job execution completed with succeed
22.3
Code Fix
Use Case
Admin
Getting empty Configuration under "Configure Default SCA Baseline Branches"
22.3
Code Fix
Use Case
Admin
Able to view empty role under permissions
22.3
Code Fix
Use Case
19 November 2023
(ARM v. 22.3.48)
Deployments
In sub-user, unable to get the branch in Salesforce Org Mappings section in SF Org Management screen if Admin user given only admin module permission.
22.3
Code Fix
Use Case
Deployments
Deployment tab - Redeploy/Promote issue
22.3, 23.1
Added Loggers
Data
nCino
Unable to create Feature Migration Template on Debt Schedule object
22.3, 23.1
Code Fix
Use Case
All Modules
Invalid Email ID
22.3, 23.1
Code Fix
Use Case
15 November 2023
Deployments
Page unresponsive in new deployment for "previous deployment" as source type
22.3
Code Fix
Use Case
12 November 2023
(ARM v. 22.3.47)
nCino
User is unable to create Feature Migration Template on Debt Schedule object.
22.3, 23.1
Code Fix
Use Case
5 November 2023
(ARM v. 22.3.46)
All Modules
New User Creation
22.3
Code Fix
Change Request
Environment Provisioning
View environment provisioning templates
22.3 & 23.1
Code Fix
Enhancement
Admin
Branching baseline is not picking all components from production
22.3 & 23.1
Code Fix
Use Case
Deployments
Help with destructive change
22.3 & 23.1
Code Fix
Use Case
Version Control
Merge request is failing due to validation credentials
22.3 & 23.1
Code Fix
Use Case
CI Jobs, Deployments
Issues with a release – related to Feature Flag not automatically set: STANDARD_VALUE_SET_DELTA
22.3 & 23.1
Code Fix
Data
Version Control
Approval button is not visible after successful merge validation
22.3 & 23.1
Code Fix
Data
27 October 2023
(ARM v. 22.3.45)
This was a maintenance release. The following items were enhanced, fixed, or added:
Loggers were added to Reports and Dashboard modules in versions 22.3 and 23.1 due to a data error in which users were unable to fetch a Salesforce code coverage report.
An enhancement was made by a code fix applied to the Environment Provisioning module in version 22.3 to enable users to view Environment Provisioning templates.
An enhancement was made by a code fix applied to the Deployments and Org Synchronization modules in versions 22.3 and 23.1 enabling users to change deploy text for validations.
A code fix was applied to the nCino module of versions 22.3 and 23.1 due to a use-case scenario during dataset creation with saving only user info in Json that is relevant to current dataset.
A code fix was applied to the Version Control module of versions 22.3 and 23.1 due to a use-case error with an AR merge failing.
A code fix was applied to the Version Control module of versions 22.3 and 23.1 due to a use-case error in which the incorrect removal of Custom Application type in package.xml on EZ-Commit via AR occurred.
A code fix was applied to the Version Control module of versions 22.3 and 23.1 in which two external pull request issues were occurring.
25 October 2023
This was a maintenance release. The following items were enhanced, fixed, or added by code fixes resulting from use-case scenarios:
A Code Fix was applied to the Deployments module due to the Deployment initiated using Org Synchronization failing caused by a use case with a fix applied to versions 22.3 and 23.1.
A Code Fix was applied to the Version control module due to a Validation Error requiring Feature Flag: VALIDATE_DEPLOY_PICK_FILECHANGES_FROM_DIFF caused by a use case with a fix applied to versions 22.3 and 23.1.
A Code Fix was applied to the Reports module due to the Weekly Code/ Test Coverage Report taking a long time caused by a use case with a fix applied to versions 22.3 and 23.1.
22 October 2023
(ARM v. 22.3.44)
This is a maintenance release. The following items were enhanced, fixed, or added.
Implemented an enhancement to version 22.3 identified as part of a use-case issue affecting the Deployments and Org Synchronization modules requiring changing deploy text for validations.
Implemented a code fix to versions 22.3 and 23.1 affecting the CI Jobs module due to a use-case issue to SFDX/CI jobs with package version installation key.
Performed a code fix to versions 22.3 and 23.1 affecting the Version Control module for a use-case issue related to custom label translation file.
Applied a code fix to versions 22.3 and 23.1 related to the Deployments module for a use-case error with previous deployment label 'add members' option not working.
Added loggers to version 22.3 affecting the Version Control module due to a use-case error with user roles missing.
Added loggers to version 22.3 affecting the CI Jobs module resulting from a use-case with automated package generation CI job AR server exception error.
Implemented a flow center change to versions 22.3 and 23.1 for the Dataloader module due to a use-case error with the download button not working.
18 October 2023
This interim release consisted of the following:
Performed a code fix to versions 22.3 and 23.1 affecting the Version Control module for a use-case issue with a custom label translation file.
15 October 2023
(ARM v22.3.43)
AutoRABIT provided the API 59.0 changes as part of its weekly fixes on both 22.3 and 23.1. This is available only for ARM modules, not for Dataloader or nCino. For DL and nCino, API 59.0 changes will be available next week as part of the Wednesday fixes deployment.
This is a maintenance release. The following items were enhanced, fixed, or added.
Instituted an enhancement via code fix to versions 22.3 and 23.1 affecting all ARM modules, applying Salesforce v.59 upgrade for Winter 2024.
Performed a code fix to versions 22.3 and 23.1 relating to a use-case error affecting the CI Jobs module concerning a package directory issue.
Applied a code fix to versions 22.3 and 23.1 due to a use-case scenario pertaining to the Environmental Provisioning module with users not able to generate a migration template using the migrate custom setting data module.
Issued a code fix to versions 22.3 and 23.1 for a use-case error in the Version Control module with a custom label translation file.
Performed a code fix to versions 22.3 and 23.1 relating to a use-case error affecting the Deployments module concerning bugs in deployment with multi-packages and static resource.
Applied a code fix to version 22.3 resulting from a use-case error affecting Dataloader returning an 'invalid cross reference id' error for ProcessInput and ProcessingInputCondition objects.
Performed a code fix to version 23.1 relating to a use-case error to the Version Control module with users unable to perform new pull request commit due to commit template permission.
Performed a code fix to versions 22.3 and 23.1 relating to a use-case error affecting the Version Control module, in which users were unable to create/append a revision to an existing label for a sub-user.
Implemented a code fix to version 22.3 relating to a use-case error in the Version Control module in which the user was getting empty error pop-ups under the ALM management screen for a sub-user, not displaying the ALM items.
Initiated a code fix to versions 22.3 and 23.1 relating to a use-case error affecting the nCino module for a 'no modifications status' displayed for a version control BR job.
11 October 2023
Performed a code fix to versions 22.3 and 23.1 related to a use case scenario affecting the Version Control module related to ALM tickets being bugged after using the ALM sync refresh.
8 October 2023
(ARM v22.3.42)
This is a maintenance release. The following items were enhanced, fixed, or added.
Performed a code fix to versions 22.3 and 23.1 for a use-case error affecting the Admin module relating to code coverage issues.
Applied a code fix to versions 22.3 and 23.1 related to a use-case error in the Deployments module concerning a flow component missed in the deployment.
Implemented a code fix to versions 22.3 and 23.1 for a use-case error related to a specific customer’s fields for redeployment.
Applied a code fix to the nCino module in versions 22.3 and 23.1 pertaining to [arm-qan] no modification status displayed for version control BR job.
Added loggers to versions 22.3 and 23.1 to correct a use-case error in the Deployments module pertaining to a deployment bug occurring with multi packages and static resources.
1 October 2023
(ARM v22.3.41)
This is a maintenance release. The following items were enhanced, fixed, or added.
A code fix was applied to the version control module in releases 22.3 and 23.1 due to a use-case error with a user being unable to create a new commit.
A code fix was performed for release versions 22.3 and 23.1 to the Deployments module for a use-case error resulting in a buggy deployment with multi packages and the static resources being bugged as well.
A code fix was applied to the version control module in releases 22.3 and 23.1 concerning a use-case error for an EZ-Commit, where the user was unable to view the 'deleted components' tab for the commit template when unchecking the 'skip mappings' checkbox.
A code fix was implemented to versions 22.3 and 23.1 to correct an error with the Deployments module due to a deployment initiated using Org Synchronization failing.
A code fix was applied to releases 22.3 and 23.1 due to a use-case error in which the registration date of the repository was not correct in the version control repository (created date in AutoRABIT).
A code fix was performed to versions 22.3 and 23.1 due to a data error in the version control module preventing ALM working items from loading.
A code fix was initiated to versions 22.3 and 23.1 due to a data error affecting the reports module, in which a user was getting an error message when executing a static code analysis (CodeScan) report.
A code fix was applied to version 22.3 in the version control module pertaining to a use-case error with changes not getting fetched via autodraft after reverting a commit.
A code fix was implemented in versions 22.3 and 23.1 to the version control module related to a use-case error wherein the baseline job has modified the Salesforce folder structure in GitHub.
A code fix was integrated to the version control module in version 22.3 after a data error caused by a feature template migration issue. The feature flag is MERGE_SKIP_AUTORESOLVE_CONFIGURATION_FILES.
A code fix to version 22.3 was implemented affecting all modules from a data error when setting up SFDX deployment.
A code fix was applied to the version control module in version 22.3 resulting from a use-case error with an ARM commit comment label error.
A code fix was implemented to the nCino module for versions 22.3 and 23.1 for a data error in which the records count was not being updated in the object sidebar for the version control baseline revision job.
24 September 2023
(ARM v22.3.40) This is a maintenance release. The following items were enhanced, fixed, or added:
A code fix was implemented due to a use-case error to the Version Control module regarding an issue with merging destructive changes.
A code fix was applied to the Deployment module due to a data error concerning an Org difference pulling changes from the managed packages.
A code fix was applied due to a use-case error relating to the Deployments module with a user unable to deploy components via Org Sync.
A code fix was applied pertaining to the CI Jobs module relating to a use-case error in which the CI Job has two different package directories and changes fall under one package when an analysis is completed on CodeScan
Performed a code fix relating to a use-case error in on the Deployments module in which a deployment bug with multi packags and static resource was bugged.
17 September 2023
(ARM v22.3.39) This is a maintenance release. The following items were enhanced, fixed, or added.
A code fix was implemented to the Deployment module related to a use-case error encountered when deploying Vlocity components from a Git branch.
A code fix was implemented related to the CI Jobs module to institute best practices following a user session.
A code fix was implemented to the Version Control module related to a use-case error pertaining to [integration_EZ-commit]. User was getting a "no package .xml found to retrieve the members" through package manifest when selecting 'all users or the respective SF org user.'
10 September 2023
(ARM v22.3.38)
This is a maintenance release. The following items were enhanced, fixed, or added:
As part of this fix deployment, one of the feature flags, 'RUN_PACKAGE_JOB_ENTIRE_BRANCH_78757,' has been provided. Enabling this feature flag only applies to one specific customer.
Implemented a code fix associated with the version control module for a use-case error in which ALM working items were not loading.
Implemented a code fix for a use-case error pertaining to the version control module for an approval email notification error.
As a result of a use-case error relating to a feature template migration issue, a new feature flag has been provided, 'MERGE_CONFLICTS_AUTORESOLVE_CONFIGFILES_USINGSOURCE,' which must be enabled for one specific customer only: More details are provided in the ticket itself.
Implemented a code fix related to a use-case error where the AutoRABIT deployment initiated using Org Synchronization fails. This error pertains to the Version Control module.
Implemented a code fix related to the CI Jobs module related to setting up SFDX deployment, with the Feature Flag:
RUN_PACKAGE_JOB_ENTIRE_BRANCH_78757
Regarding one ticket, 'Setting up SFDX Deployment': Only for the 'Create and Install an Unlocked/Managed Package Version from a Version Control Branch' CI, type in the CI Job configuration. When selecting the 'Trigger build on commit' option, we have hidden the 'Process commit revision received via hook only' sub-option. This change will be incorporated into our documentation. Further details are available in the ticket itself.
Implemented a code fix related to the nCino module error:
LLC_BI__Schedule_Section__c migration issue#1
Implemented a code fix related to an internal ticket in ARM, in which the user was not able to migrate related data using the Dataloader test environment setup module.
Implemented a code fix related to the Deployment module for an EBR Manual Asyncid XML Copy Automation error.
3 September 2023
(ARM v22.3.37)
This is a maintenance release. The following items were enhanced, fixed, or added:
Implemented a code fix associated with the version control module related to a use-case scenario in which a review artifact was not working.
Implemented a code fix to the nCino module resulting from a user product suggestion to the deployment history filter.
Implemented a code fix to the nCino module related to an instance in which the org name was not displayed for the destination org value field.
27 August 2023
(ARM v22.3.36)
This is a maintenance release. The following items were enhanced, fixed, or added:
Error: "Merging from Devint branch to Developer branch (Back merge) is getting Auto Rejected": Code fix to Version Control module on user merging from Devint branch to Developer branch (Back merge) getting Auto Rejected.
Implemented a UI change to include the “Ignore Warnings” option in both the prevalidation commit and merge flows. This requires a documentation change. See ticket for more details.
Error: “[Client] getting frequent page unresponsive errors in ARM": Introduced a UI change to support Salesforce orgs and the previous label deployment type in the deployment module.
Performed a code fix affecting the Deployments module related to a use-case error with the client getting frequent page unresponsive errors in ARM. This also requires an update in our documentation. Further information is in the ticket.
Error: “Branching baseline is not picking all components from production": Based on the customer-confirmed downtime window, it was necessary to enable the "METADATA_API_TO_DX_CONVERSION" feature flag for this fix deployment.
Performed a code fix concerning the Admin module due to an error with a branching baseline not picking all components from production with feature flag error: ‘METADATA_API_TO_DX_CONVERSION’.
Error in CodeScan Plugin pop-up window where the user was unable to type text in Org key drop-down selection field, which required a code fix to the Admin module. (Internal ticket)
Performed a code fix related to a use-case error during Vlocity deployments showing "NoOrgFoung" after activation of LWC components. Fix applied to the CI Jobs and Deployment modules.
Code fix applied to SFDX module for the user receiving an error message showing login failed. Also related to CI Jobs, scratch org creation was being struck in progress and not able to be deleted.
Applied a code fix for the Version Control module related to a user being unable to select the ALM side, getting a JAVA error.
Initiated a code fix to the Deployments module related to an error during an EZ deployment from a single revision with profiles and comp-specific changes pulling all comps.
Executed a code fix to the Deployments module on a use-case error affecting an AR deployment initiated using Org Synchronization failing.
Applied a code fix related to the following use-case error: [Cijobs-DXModulePckagecreation] facing the "["An unexpected error occurred while preparing endpoint: null. Please contact Salesforce Support and provide the following error code: 795089467-5806 (-1215335089)"].
Initiated a code fix to the nCino module for a client use-case error concerning spread template issues.
Performed a code fix for a customer use-case scenario regarding an error related to an nCino CI job deployment issue.
20 August 2023
(ARM v22.3.35) This is a maintenance release. The following items were fixed and/or added:
Performed a code fix impacting the Deployments and CI Jobs modules related to use cases in which selected test classes for production were not running and users were having code coverage issues.
Performed a code fix for the Admin module related to a specific user having difficulty with PWD policy.
Performed a code fix to the CI Jobs and Deployment modules relating to users unable to deploy changes to production orgs due to a CI Jobs coding issue.
Performed a code fix to the CI Jobs module related to an error message as login failed.
Performed a code fix on the CI Jobs module pertaining to Vlocity SFI components not compiling LWC on destination orgs when deploying via CI Jobs.
Performed a code fix related to the CI Jobs module for CI Job not starting according to schedule.
Performed a code fix related to the CI Jobs module to resolve an error related to setting up SFDX deployment and CI Job configuration.
Performed a code fix to the nCino module for an error in which the screen template failed with a malformed query exception.
13 August 2023
(ARM v22.3.34)
This is a maintenance release. The following items were fixed and/or added:
Performed a code fix pertaining to all modules relating to an SFDX to SF CLI Hotfix.
Performed a code fix relating to version control, CI jobs, and deployment modules initiated via change request due to ALM working items not loading, resolved by enabling the customer domain name.
Performed a code fix for a data error with feature flag name, ‘Disable_Merge_Rename_Detection’ after a merge was failing and took hours to complete.
Performed a code fix for the version control, CI jobs, and deployment modules pertaining to a data error, validation failing for the LWC component despite no error message being displayed in the logs.
Performed a code fix related to a use-case error in the version control module pertaining to a commit showing a “no modification” error.
Performed a code fix related to a use-case error affecting the version control, CI jobs, and deployment modules caused by an error merging a commit from the dev environment to the INT environment.
Performed a code fix to the version control module resulting from a use-case error where the commit was incorrectly showing “no modification”.
Performed a code fix related to a data error pertaining to the version control module, when Jira integration stories redeploy post sandbox refresh.
Performed a code fix for a use-case error in the deployment module related to filter-based retrievals not working when applying the ‘created by,’ ‘modified by,’ ‘created date,’ and ‘modified date’ filters.
Performed a code fix related to a performance issue in the nCino module pertaining to Spread Template issues.
Fixed an error in the deployment module when ‘Run Specified Tests’ is selected from the Apex Test Level dropdown.
Rather than a code fix, a customer-specific utility was provided to address SSO login issues in the admin module. This particular utility only works in versions 22.3.9 or lower for one individual customer.
06 August 2023
(ARM v22.3.33) This is a maintenance release. The following items were fixed and/or added:
Fixed an error under reports where code coverage emails were missing information.
Fixed an error related to a second deployment starting in the middle of a deployment.
Fixed an error in version control module related to not being able to commit or Repush changes in the Training Branch.
Fixed an error in version control module related to a feature flag: USE_PATCH_LOGIC_IN_EZCOMMIT for Code overwritten (feature not enabled by default).
Fixed an error for CI Job module where ALM-enabled failed due to Unparsable date error.
Fixed an error concerning multiple CI Jobs failing due to data error.
Fixed an error related to the Deployment, CI Jobs, and Version Control modules occurring when merging a commit from dev environment to INT environment.
Fixed an error related to deployments getting frequent page unresponsive errors in ARM.
Fixed an error under the Admin module relating to being unable to select the revision number while creating the Tag.
Fixed an error for Create and Install Package CI job deployment failing if having multiple package directories on the branch.
Fixed an error under the Admin module, My Account >> Merge Settings: Not visible Border for "Notify All Criteria Overwrites To" field.
Fixed an error under the Admin module, which enabled Domain names to be visible in the inspect mode.
Fixed an error in the nCino module related to [ARM-QAN] attachments’ deployment Failed with Bulk API.
Fixed an error in the nCino module related to a Pricebook entry.
Fixed an error related to the nCino module with scheduled Job not showing up in UI after completion due to Deploy Status Not Updated.
Fixed an error related to the nCino module with a CI Job Edit not populating with scheduled time details.
30 July 2023
(ARM v22.3.32) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue with duplicate not working on EZ-merge requests related to version control.
Fixed EZ deployments from a single revision with profiles comp-specific changes pulling all comps during deployments.
Fixed an error related to CI Jobs not running the pipeline.
Fixed situations with both version control prevalidation commit and merge where static code analysis processes are stuck in an In-progress state when VNC is not started.
Helped generate the reports for CI/CD pipelines for nCino reports.
Performed Jira integration story’s redeploy post-sandbox refresh in version control.
Fixed a specified metadata type is unsupported: [processflowmigration] error in CI Jobs.
Set up the SFDX Deployment in CI Jobs.
Fixed an error with a CI Job not identifying changes.
Fixed an error related to BHG with CI Job webhooks failing to trigger.
Performed nCino AR template updates.
23 July 2023
(ARM v22.3.31) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue with a merge use case of handling deleted files in both source and target branches by using git rm command.
Fixed an issue where screen redirects to login page on clicking on User activation email.
Fixed an issue where Commit stuck in InProgress.
Fixed an issue where we receive “JAXB marshall/unmarshall exception” while getting directed to CI results screen.
Fixed an issue where Release labels are taking 30 minutes or more to be available for repository in Version control.
Fixed an issue where Merges are taking a long time to complete in version control.
Fixed an issue where components selected on review component pages were being repeated in the next category in Version Control.
Fixed an issue where same name should be reflected instead of Commit showing a different name in Bitbucket in Version Control.
Fixed an issue where JIRA ALM Filter mappings not working in My profile & Version Control.
Fixed an issue where the Login rate exceeded error on the Salesforce Integration user.
Fixed an issue where Backup to Version Control is not backing up Matching Rules in Salesforce in CI jobs.
Fixed an issue where the shared server with common DB creates another customer weekly report in another server.
Fixed an issue where Custom field property didn’t deploy in CI Jobs and Deployment.
Fixed an issue where Diff report is not generated in New Deployment Module.
Fixed an issue where Unsupported metadata template execution is failing in Sandbox Refresh in Environment Provisioning module.
Enhanced DataLoader uber jar upgrade to 58.0.3.
Fixed an issue where we are facing Record Configuration Time Out in nCino.
Enhanced UI in Post Deployment activities result page in CI Job – nCino.
Enhanced the View details page not being visible unless post-deployment activities are completed – nCino.
18 June 2023
(ARM v22.3.26) This is a maintenance release. The following items were fixed and/or added:
Enhanced ARM by allowing PAT Authentication for Jira.
Fixed an issue where user ran an Org Synchronization history job and tried to access the Diff report to see the metadata difference, but the page kept loading indefinitely without the required diff.
Upgraded Provar to version 2.10.1.
Fixed an issue where the Approval option wasn't functional for L1 Approvers, and the Org Admin couldn't bypass the approval gate on EZ-Merge.
Fixed an issue with nCino where user created a Feature deployment task, but the jobs were stuck the queue.
Introduced a new feature in DataLoader called Hard Delete which can be used to delete the data completely and permanently instead of sending it to the Recycle Bin of the org.
Fixed an issue where CI Job build history was not displaying the results and throwing a blank page instead.
Fixed a UI bug where Abort option for CI job was displaying even after the build was successful.
Fixed an issue where duplicate ALM Commit entries were Displaying while performing ALM Commit with Vlocity repository.
Fixed an issue where the CI edit configuration screen was taking longer to load than expected before throwing
Page Unresponsive
alert.Fixed an issue with DataLoader Pro where user created a new job and applied filter, but the source and destination orgs are taken from history page.
Fixed an issue with DataLoader where Insert operation bulk API selection was resulting in console error message
serializeToString
.Fixed an issue where Vlocity metadata components were getting expanded on the Finish page.
11 June 2023
(ARM v22.3.25) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where deployment failed with the error message
File cannot be loaded
.Fixed an issue where the SharingCriteriaRule component was not deployed to Production even though the user had selected it (#73824).
Fixed an issue where the SharingReasons component was ignored when the deployment/validation was done using Commit Label as source, but the same component was processed using Single Revision deployment or CI Job deployment (#72073).
Fixed an issue where user was trying to create an connect an Active Directory but it kept failing (#73582).
Fixed a UI bug where Deployment Failed line was displayed twice in the logs for failed deployments (internal ticket).
Fixed an issue where admin was unable to release a user from a team (internal ticket).
Fixed an issue where Null Values were displayed on the ALM Labels screen as well as the ALM Details tab on the respective ALM Commit Label Details screen (internal ticket).
Fixed an issue where selected files for DX Commits were not displayed in the File Changes tab, and after the commit it was showing as No Modifications (internal ticket).
04 June 2023
(ARM v22.3.24) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where a CI job failed to pick the external commit revision which was added to an ALM Label as part of Smart Commits sync (#71444).
Fixed an issue where Class Coverage Report generated was empty for one of the Salesforce orgs, and it was intermittent. The same behavior was observed for RunSpecified and RunLocal test levels (#71367).
Fixed an issue where deploying test classes from manual deployment was throwing an out of memory error (#71872).
Fixed an issue where BackUp to Version Control CI Job was failing due to too many retrieval error messages even though the Bulk API option was enabled (#72181).
Fixed an issue where while performing any commit, Pull Request enabled CI Job was triggering as expected; but its Build and Deployment status was not added in the Comments in Bitbucket (#72811).
Fixed an issue where EZ-Commits were stuck with In-progress status for a few hours before failing. But the commit revisions were generated at the repository level and updated in ARM database (#72817).
Fixed an issue where the Git author was overridden by ARM (#71393).
Fixed an issue with DataLoader where user was unable to create an Update job because the functionality prompoted user to select the Required field within the Mapping Fields (#73515).
Fixed an issue with DataLoader where user was getting a script error in the console while editing an existing old job (internal ticket).
Fixed an issue where Destructive commit for DX was not working as expected for Documents, Reports, and Dashboards types (internal ticket).
Fixed an issue where the Layout file was not displayed in the Review Artifact screen after resolving the layout duplicates (internal ticket).
Fixed an issue where 4 CI jobs were running parallelly even though the parallel process limit was 1 on the external agent (internal ticket).
28 May 2023
(ARM v22.3.23) This is a maintenance release. The following items were fixed and/or added:
Fixed a compliance issue with Apache Commons by removing the text dependency (#71947).
Fixed an issue where CI Jobs were failing due to empty JSON file(s) in the remote repository, and throwing the following error:
Failed to initiate deployment. Unexpected end of JSON input
(#72217).Improved the UI by removing the Validate Deployment option if Vlocity is selected, and hiding the whole Board Type option if Vlocity is not enabled (#70993).
Fixed an issue where user was performing CI jobs for Validate and Deploy for a successful commit, but only validation was performed but not the deployment (#72751).
Fixed an issue where CI job deployment was failing because the build was picking duplicate Layout values (#71214).
Fixed an issue where Branching Baseline was not picking all the components from production (#70720).
Fixed an issue with nCino where CI jobs that used a Deployment from Version Control were failing when the build was triggered (#71914).
Improved the New Merge screen by adding Layouts text in the Skip Flow /Profile/ Perm.Set Access-Setting Duplicity Check option (internal ticket).
Fixed a UI bug where SF Org Test Connection notification message was displayed on an unrelated module (internal ticket).
Removed the option to sign up for a 30-day Salesforce trial while registering a DevHub as the trial offer is no longer applicable (internal ticket).
21 May 2023
(ARM v22.3.22) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where wrong timezone region was displaying for users (#71553).
Fixed an issue where the EZ-Commits report file displayed the file count but not the components count (#71538).
Fixed an issue where clone build jobs were taking between 10 and 25 minutes, which is much longer than expected (#70227).
Fixed an issue where CI job to generate Code Coverage Report was not reflected in the org or in the e-mail notification (#72042).
Fixed an issue where merge status is displayed as completed but no revision is generated, and the merge is not available in the UAT branch (#71266).
Enhanced DataLoader by adding the ability to field mapping through the lookup fields (#58480).
Fixed an issue with DataLoader where while running an Extract job on the PUBLISHER object, the job was failing with the following error
Publisher: column id is not supported in ORDER BY clause
(#71303).Enhanced the nCino filter criteria by adding the ability to search and filter labels using the whole or partial name (#71826).
Enhanced ARM by using known vulnerable components through the DataTables 1.10.12 plugin for advanced data table functionalities such as sorting, filtering, pagination, and more. This allows users to easily display and manipulate large sets of data on their web pages in a user-friendly manner (internal ticket).
Fixed an issue with Prevalidation Merge where users were unable to deploy the ApexClass Tests related to ApexClasses and Apex Triggers (internal ticket).
Fixed a UI bug where the date column in the EZ-Commit Weekly report was displaying incorrect values (internal ticket).
14 May 2023
(ARM v22.3.21) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where user was having trouble while deploying LighteningMessageChannel components (#70787).
Fixed an issue where Destructive Changes wasn't working as expected while performing an Entire Branch merge (#68882).
Enhanced the ALM management feature by adding an option to sync Smart Commits (#58904).
Fixed an issue with CI Jobs Destructive Sharing Rule was not deploying to the Salesforce org (#71183).
Fixed an issue where user could not disable the Smart Commits-Sync option for a repository branch in the VC repos section (#70854).
Improved the New Merge screen by removing the Validate Deployment option from the UI if Vlocity is selected (#70993).
Enhanced the Credentials module by adding SSH Cetificate option for Git Authentication (#67725).
Improved Release label creation by requiring at least two revisions to be selected (internal ticket).
Fixed an issue where Classic SF Org URL with a slash at the end of the URL redirects to the
400
error page, and for a Lightning SF Org URL without a slash gives anOAuth Authentication Failed
error message (internal ticket).Fixed an issue with nCino where user was getting a
NullPointerException
on Saving Permissions using Bulk Assignment (internal ticket).Fixed an issue with CI Jobs where all the scheduled timings were not displayed in the Preview & Save page (internal ticket).
Fixed an issue with Dataloader where user was able to upload a 900 MB file despite the limit being 100 MB, causing the process to hang (internal ticket).
Fixed an issue with Dataloader where sever crashed after user performed an Extract operation from an SF org which had Account Object with 2 million records (internal ticket).
07 May 2023
(ARM v22.3.20) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where user was getting a validation deployment error while performing release label deployment (#70400).
Fixed an issue where Branching Baseline was taking longer than expected (#67814).
Fixed an issue where using the AutoDraft functionality in EZ-Commit was resulting in a malformed exception in the UI (#70458).
Fixed an issue where Branching baseline was not picking all components from production (#70720).
Fixed an issue where prevalidation merge failed with empty metadata package even though there were changes in File Diff (#32256).
Fixed an issue where entire ARM application was down temporarily (#70658).
Fixed an issue where Merge was auto-rejected due to an empty package because the metadata folder path not being specified under branch settings (#69788).
Fixed an issue where user was using the Bulk Assignment feature to assign Sandbox permissions on the Permissions page but encountered the following error:
Java.lang.NullPointerException
(#70868).Fixed an issue where users weren't receiving SCA reports by email even though the reports were running (#70751).
Fixed an issue where while performing new EZ-Commit, user edited one line using review artifact option but Diff did not capture the same (#70270).
Fixed an issue where if CI Jobs were added in a queue with Scheduled jobs, then not all jobs were displayed in the queue (internal ticket).
Fixed an issue where existing revision file related delta still existed in agent even after uploading to rabitserver (internal ticket).
Fixed an issue where release label creation was failing when user tried to create package manifest and aborted and refreshed the label for DX repo (internal ticket).
Fixed an issue where Super admin user was getting a blank popup screen while trying to click on the Register Agent button from the Pool Mgmt screen (internal ticket).
30 April 2023
(ARM v22.3.19) This is a maintenance release. The following items were fixed and/or added:
Enhanced the Version Control module by adding SSH Certificate for Git authentication while creating user credentials (#67725).
Fixed an issue where CI Job was picking changes one build but not for the other, and the logs weren't capturing this (#69164).
Fixed an issue where Ignore missing visibility settings function was not working as expected and Record type visibility on the profile was not getting deployed using CI Job (#67654).
Fixed an issue where user merged a new component using a single revision merge but the merge missed to perform a CodeScan analysis (#70391).
Fixed an issue where user was unable to commit the destructive Email Template files as part of commit in SFDX format and getting auto failure (#70351).
Fixed a UI issue where OK button to reject an EZ-Merge was not working (#70041).
Fixed an issue where a field was available in the package but still Validation was throwing error that the field was missing (#69831).
Fixed an issue with DataLoader where multiple jobs were not processing parallelly when user loaded a large number of jobs to the queue (#62559).
Fixed an issue with nCino where user created more than 100 jobs with sub-user but was still getting the following error:
No jobs exist to load
(#69831).Fixed an issue where Release Label artifact was not displaying metadata types in the Destructive changes tab for DX repos, but was working as expected for non-DX repos (internal ticket).
Fixed an issue where new jobs are getting added to the queue but not getting triggered, and later throwing
NullPointer Exception
(internal ticket).Fixed an issue where Rollback button was not enabled for the first job if that job is came from a queued list (internal ticket).
Fixed an issue where ALM CI Job and Release artifact execution was happening at the same time, and the CI Job build was failing (internal ticket).
Fixed an issue where an empty pop-up was displayed when user tried to edit the existing CI jobs label for Sub-User (internal ticket).
Fixed an issue where if Validate only CI job came from the queue, then direct deployment was executing for that job instead of validate deployment (internal ticket).
Fixed an issue where duplicates revisions were being added to the list while creating the release label when user unselected and reselected the same revisions. (internal ticket).
Fixed an issue where Vlocity revisions were not displaying while user was trying to edit a release label (internal ticket).
Enhanced the Release Label creation page by adding options to the Vlocity label type which were only available for Salesforce revisions before (internal ticket).
23 April 2023
(ARM v22.3.18) This is a maintenance release. The following items were fixed and/or added:
Enhanced the VC Repos page by introducing a feature that allows users to sync external smart commits (#58904).
Updated the UI on the External pull request creation page to reflect the Source and Target fields clearly so users can trace which one is the source and destination branches (#69772).
Fixed an issue where duplicate entries were created in different lines during the Merge process and user wasn't able to remove the duplicate field without clearing the layout tag as well (#68012).
Fixed an issue where the baseline branch is not displayed during Static Code Analysis job creation if the branch name contains spaces in the Reports module (#69614).
Enhanced deployment in ARM by providing a new option Rollback on error in merge pre-validation. This checkbox allows users to choose if deployment should proceed with remaining components in case of errors (#47794).
Fixed an issue with nCino where CI job filter changes on templates were not taking effect after saving (#66956).
Fixed an issue where user created a baseline revision job with the Automation Sanity repo and triggered the build but it failed without any error (internal ticket).
Fixed an issue where user could not fetch the ApexClass Tests related to ApexTriggers upon selecting Run Tests Based On Changes as an option (internal ticket).
Fixed an issue where error
405
in the build and deployment logs didn't display further details in the UI log (internal ticket).Fixed a UI bug where dropdown selection in Reports > CodeCoverage Reports was not working after refreshing the page (internal ticket).
Fixed an issue where Release Label artifact was not displaying metadata types in the Destructive changes tab for DX repos, but was working as expected for non-DX repos (internal ticket).
Fixed an issue where user was unable to revert the commit if a previously reverted commit was deleted while in Conflict state (internal ticket).
16 April 2023
(ARM v22.3.17) This is a maintenance release. The following items were fixed and/or added:
Enhanced the SCA report options by removing the 10,000 limit for exporting issues using CodeScan (#48644).
Fixed an issue where user was unable to use the Redeploy/Promote option after ten iterations of an existing Deployment label (#69084).
Fixed an issue where user was trying to commit System Permissions which were enabled in Salesforce org, but while performing EZ-Commit, file Diff is not getting generated and the system permissions are not getting committed (#67826).
Fixed an issue where ALM label merge option was not working in EZ-Merge feature. This happened only when the ALM Label contained
/
in it (#67818).Fixed an issue where EZ-Merge was failing with
NullPointerException
(#67502).Fixed a recurring issue of ARM overwriting the Salesforce Org - Default Apex Test Class Configuration by adding a checkbox
Do you want us to update the test classes?
(#65565).Fixed an issue where Revert commits were failing without any error messages (#68771).
Fixed an issue where user created a Release label with multiple commit revisions, each with dependency components, but the revisions were not displaying in the right order in UI (#68939).
Fixed a UI bug where when user unchecked Validate deployment option in EZ-Merge, the Run destructive changes checkbox was hidden (#68750).
Fixed an issue where when user had files in conflicted state, selecting the ALL checkbox was not working and user had to click on each file to resolve conflicts (#65680).
Fixed an issue where the NPM repository Access Key wasn't saving after clicking Save, causing the Local Compilation to fail (internal ticket).
Fixed an issue where comments lines were not executed in Metadata when there were spaces in the comment line in merge flow (internal ticket).
Fixed an issue where an empty popup screen is displayed while resolving conflicts in case of malformed file (internal ticket).
Fixed an issue where improper validation message is displayed after clicking on Resolve Duplicates without selecting any files to resolve (internal ticket).
Fixed an issue where SSO user's org was not deleted from the Security-Context XML (internal ticket).
Fixed an issue where the API Token status was marked as Never Accessed, despite the API being in use already (internal ticket).
09 April 2023
(ARM v22.3.16) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where Salesforce components were showing under the Apex Test Success tab in the Deployment module, which is not expected behavior (#67537).
Enhanced the Branching Baseline feature by allowing admin to define default baseline branches, making it easier for developers to choose the default branch for each project (#63571).
Fixed an issue where user was unable to register a branch even though Test Connection was successful (#67023).
Fixed an issue where ARM wasn't fetching the ApexClass Tests related to ApexTriggers upon selecting Run Tests Based On Changes option (#67503).
Fixed an issue where triggered CI jobs were taking too long to build, and also slowing down ARM altogether (#66846).
Fixed an issue where if the file name contained spaces, Commit Validation via VS Code plugin was unable to detect the file (#63518).
Fixed an issue where Search & Substitute was not updating the value for a custom label in the SF org (#66809).
Fixed an issue where there was a discrepancy between the changes captured in the ARM Diff and the repos in BitBucket (#60596).
Fixed an issue where the SF org URL is not displaying the updated one under Profile (#67718).
Fixed an issue with nCino where CI job filter changes on templates are not reflecting after saving (#66956).
Fixed an issue with Dataloader Pro where user tried to migrate Account Object Data with Attachments Object, but the logs verify that there is a Null Pointer Exception. (internal ticket).
Improved nCino by adding additional loggers for Branching baseline for user to view the status in the UI (internal ticket).
Fixed an issue where user was unable to filter while trying to select a job which had spaces in the job name (internal ticket).
02 April 2023
(ARM v22.3.15) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where Custom Metadata type access changes were not detected in version control Diff. There was no diff generated even there were changes in metadata access (#59458).
Fixed an issue where user performed a CI job deployment that had 8 destructive change items in the merge PR, but ARM is displaying only 2 destructive changes (#66587).
Fixed an issue where Git backup job was failing due to unsupported metadata (#66536).
Fixed an issue where scheduled CI jobs were getting queued or not getting triggered as per schedule (#57749).
Fixed an issue where Quick action was not picked for destructive changes (#65058).
Fixed an issue where while running the scan from ARM for the version control branches are failing because .java files were present in the current repository (#63234).
Fixed an issue where user using non-SFDX repo with Custom API enabled failed to pick the changes in the CI job (#64497).
Fixed an issue where Release label displayed commit revisions older than 30 days even when the No. of days filter was set as 30 (#63845).
Fixed an issue where a user had trouble creating artifact for a release label (#65557).
Fixed an issue where there are Vlocity components in Merge Validation, and the validation deployment should bypass and process the merge; instead it is Auto-rejecting as criteria were not met (#65625).
Fixed an issue with Dataloader where a job completes with No records status whenever attachment and content version are selected as child objects in the parent cccount object (#66655).
Fixed an issue with nCino where CI job build status is displayed as Completed for a failed job (#64479).
Fixed an issue with nCino where attachements to
nFORMS__Form_Template__c
failed to get deployed (#65242).Fixed an issue where user was unable to initiate static code analysis on a Salesforce Org (#51559).
Fixed an issue with New EZ- Commit where while using Custom YAML file the page was taking much longer to load than usual (#65742).
Fixed an issue where Merge was happening on incorrect files (#64485).
Fixed an issue where for DX repo, Custom field destructive Deployment was failing with the error
Package generation without a valid package directory cannot be processed
(internal ticket).Fixed an issue from the VS Code where Static Code Analysis report was not getting executed on the selected files and report generated (internal ticket).
Fixed an issue where Release Label creation with SVN Repo was not successful, and throwing the following errors (internal ticket):
Supplied AttributeValue is empty, must contain exactly one of the supported datatypes (Service: AmazonDynamoDBv2; Status Code: 400; Error Code: ValidationException; Request ID: a59c77cb-67ad-4a58-80b4-364feb5a4d6c; Proxy: null)
No Version Control Mappings found for Repo: {} and Branch: {}. Please update it in My Profile
Fixed an issue where Merge was not Auto-rejected after UI logs displayed
Mock deployment is failed, so auto rejecting the merge
(internal ticket).Fixed an issue where Revision in Vlocity release label was not getting selected after you clicked save (internal ticket).
Fixed an issue with nCino where user was getting an exception while creating a CI job, and user was selecting the same VC Repo/Branch for multiple times (internal ticket).
26 March 2023
(ARM v22.3.14) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where Quick action was not picked for destructive changes (#65058).
Fixed an issue where WebStoreTemplates object was not available for deployment (#65854).
Fixed an issue where Merge Request XML file was conflicting with an error
No conflict data found for this block
(#65164).Fixed an issue where Release label failed while creating the artifact (#64491).
Fixed an issue where Prevalidation EZ-Commit shows that Diff does not exist even when there are changes. If user tries multiple times, then Diff is displayed sometimes (#64612).
Fixed an issue where user was unable to merge the code from one branch to another branch. (#65570).
Fixed an issue where Ignore Missing Visibility settings not working on EZ-Merge validation (#65162).
Fixed an issue where user was loading multiple DataLoader jobs but it was not processing parallelly (#62559).
Fixed a UI bug in nCino where the header in template details section was missing in Feature Deployment (internal ticket).
Fixed an issue with nCino where Deployment Logs were not displayed when the CI Job failed (internal ticket).
19 March 2023
(ARM v22.3.13) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where CI job deployments were failing with the error,
Error 405 Only POST allowed
(#64228).Fixed an issue where multiple deployment requests were being generated while performing Org Sync if the user selected all components instead of a few (#51288).
Fixed an issue where Rollback API threw a 200 response but the Rollback immediately failed in the ARM UI (#65146).
Fixed an issue where SCA report Failed to run using the Codescan Plugin with the following Salesforce error
384187622-16951 (-673032061)
(#61676).Fixed an issue where after upgrading to ARM version 22.3 user was unable to approve EZ-Commits that were pending approval in the 22.2 (#64094).
Fixed an issue where user was trying to resolve a conflict in EZ-Merge but was getting a message on the UI that there are no conflicts (#64185).
Fixed an issue where Branching Baseline job does not delete files in static resources sub directories even though the user has selected the Delete existing metadata and commit new changes option (#64150).
Fixed an issue where user was unable to retrieve MutingPermissionSet using the SFDX repository (#64141).
Fixed an issue where the Release Label failed while creating the artifact (#64491).
Fixed an issue where Sharing Rule Set metadata type was found in the Deployment module but not in the Version Control module (#65060).
Fixed an issue where the user performed a merge and approved both level 1 and level 2 reviews but was unable to approve the merge (#65091).
Fixed an issue where errors were occuring while performing Delete Org (internal ticket).
Fixed an issue where for Build only job source from VC with DX repo, if Master Details Object Change is included in the build, we're getting No Modifications even if changes exist (internal ticket).
12 March 2023
(ARM v22.3.12) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where Static Code Anaysis was failing due to missing property tag in Apex PMD rules file, but the UI log wasn't displaying this error (#63554).
Fixed an issue where when there was no results generated, the report displayed an error that there are zero metrics instead of displaying the results as zero in all the places when there is no change (#63272).
Fixed an issue where user was unable to deploy a CI job with the RelationshipGraphDefinition components (#64145).
Fixed an issue where Validate deployment was displayed as failed in UI and the database, but was successful as per the logs (#63868).
Fixed an issue with Review Artifact where similar custom fields from different objects were not populating correctly and switching to other fields (#63676).
Fixed an issue where multiple fields of the respective custom objects were getting selected parallelly while performing edit or save or exit operations on the Review Artifact screen (internal ticket).
Enhanced ARM by adding an option for multiple ARM instances to share a single database cluster (internal ticket).
05 March 2023
(ARM v22.3.11) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where ARM was displaying incorrect installation settings and package version information in the deployment log while installing the package version from a CI job (#63544).
Fixed an issue where user chose Exclude Metadata Type for a particular metadata type during a CI Job, but it was still deployed (#62966).
Fixed an issue where user was unable to perform Destructive Commit with PermissionSetGroups metadata type (#63172).
Fixed an issue where users weren't receiving emails after setting up Mail Settings (#55070).
Fixed an issue where there was a discrepancy between EZ-Commit and Commit templates while retrieving Email Template metadata members (#61696).
Fixed an issue where Merge Labels were taking much longer than expected (#62625).
Fixed an issue where user tried to commit the changes without validation and UI displayed an error
Another commit is in progress
(#61930).Fixed a UI bug where there was a discrepancy in the timestamp displayed for a commit in the Commits History page (#61672).
Fixed an issue where Merge was not auto-rejected when validation criteria was not met (#62287).
Enhanced nCino by allowing users to deploy nCino CI build to multiple target sandboxes (#41763).
Fixed a UI bug where incorrect notification was displayed in certain components pages when template was created using one org and was used by another org (internal ticket).
Fixed an issue where Baseline Managed Package Changes option was not displayed on the UI when navigating from Package xml to select manually (internal ticket).
Fixed an issue where there was a discrepancy between the Attachments Records Success/Failure Count and the Retrieved Count when BULK API was enabled for Deployment (internal ticket).
26 February 2023
(ARM v22.3.10) This is a maintenance release. The following items were fixed and/or added:
Fixed a UI bug in Profile Manager where User Permissions differences are shown in the report but not in the UI (#61672).
Enhanced the Release Label creation by increasing the range of retrievable commit history (#61714).
Fixed an issue where user was unable to use Release Labels to perform Deployment, and it failed while trying to Create Artifact (#59429).
Fixed an issue where Release Artifact execution was failing when rabit home did not exist with an external agent (internal ticket).
Fixed a UI bug on the Profile screen where the expand option for the My Projects and My Roles sections was not working (internal ticket).
Fixed an issue where triggering Data Retention for Audit Tables was throwing the following error:
Unable to execute HTTP request: Read timed out
(internal ticket).Fixed an issue where extra characters are seen in the Fetch Commit History results while creating a Release Label with Vlocity label type (internal ticket).
Fixed an issue where user was unable to delete Apex test class on the SF Org Management page (internal ticket).
Enhanced nCino by introducing New Spreads Schedule tile in the Feature Creation screen (internal ticket).
Fixed an issue where if the fields did not load for Applied Mappings during deployment, no error was thrown by the application (internal ticket).
19 February 2023
(ARM v22.3.9) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where user was deploying single revision deployment with only report folder but sub-reports were also getting fetched, and the deployment was failing due to field dependency error (#61403).
Fixed an issue where after deployment with single revision merge, user permission appears to be removed in target org but in the Salesforce target org the user permission is not removed, and an incorrect layout is displayed in UI (#60531).
Fixed an issue where user performed a pre-validation commit and each process like file diff, validate deploy happened thrice as per the logs (#61079).
Fixed an issue where user was unable to select master branch as the parent branch while creating a new branch in EZ-Commit (#56188).
Fixed an issue where user was customer trying to register a Salesforce Org with Custom URL but it was failing with an error (#62192).
Fixed an issue where user user uploaded a YAML file to retrieve the Vlocity components but ALL metadata types were retrieved and displayed (#61181).
Fixed an issue where the same merge could be approved and rejected by different users simultaneously (#60859).
Fixed an issue where branch creation was faileing for sub-users in the EZ-Commit screen for Non-DX Repo (internal ticket).
Fixed an issue where Null Pointer was seen in Create Branch in EZ-Commit flow (internal ticket).
Fixed an issue where all credentials were listed twice in the Credentials dropdown in Create Branch in EZ-Commit flow (internal ticket).
Fixed an issue where branch creation was failing for sub-users in VC repos when the credential scope was private while Admin credentials were fetched (internal ticket).
Fixed an issue where user was unable to delete the Apex Test class under the SF org Apex default config (internal ticket).
Fixed an issue where the Add manually checkbox under Apex class config was selected by default (internal ticket).
Fixed an issue with nCino where user created a feature Deployment for Credit memo template with attachments, but Attachments Objects Data was not fetched, and the deployment failed with the following error:
Data file not fetched for object: Attachment
(internal ticket).Fixed an issue with nCino where Standard Features were not loaded in the Feature Management page (internal ticket).
12 February 2023
(ARM v22.3.8) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where user was unable to download success/failure reports in Single Dataloader (#61551).
Fixed an issue where when multiple CI Jobs are triggered, jobs are moved into the queue as expected, but new jobs are not starting automatically getting processed once the existing jobs is cleared from the CI Job results page (#59082).
Fixed an issue where Dependency order defined in json file was being changed on every commit but it was not supposed to (#57731).
Fixed an issue where Create Artifact was not working as expected while using Release Label (#61607).
Fixed an issue where user was performing an EZ-Commit with Review Artifact option and download the .zip file to make some changes, but was unable to upload it afterwards (#61751).
Fixed an issue where meta.xml file was not deleted from the repository after committing the destructive changes (#61736).
Fixed an issue where File Diff was empty in case of modified Uploaded via Review Artifact in PV Commit Flow (internal ticket).
Fixed an issue where Review Artifact Tree was not responding after uploading the modified file in Commit Flow (internal ticket).
Fixed an issue where User Permissions and Ip Ranges are completly removed from the branch after commiting the Permission Sets and Profiles (internal ticket).
Fixed an issue where Super Admin was getting an error while trying to activate newly signed up users (internal ticket).
05 February 2023
(ARM v22.3.7) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where SFDX module creation log shows that deployment is successful but the module creation had failed (#57318).
Fixed an issue with Backup from Org CI Jobs where PermissionSet User Permissions were being deleted (#59674).
Fixed an issue where Org to Org Deployment for Profiles including Deploy Profile Access Settings for selected components only was not working as expected (#60559).
Fixed an issue where Post Destruct fields were also added to Pre Destruct despite the user setting it to post (#61162).
Fixed an issue where user set the Max depth value as '0' under Vlocity Configuration Settings but it was retrieving all level dependancy components (#57501).
Fixed an issue with DataLoader where the Credit Memo Template migration was not deploying after user upgraded their instance (#57676).
Fixed an issue where user selected Custom Metadata members (records), but EZ-Commit was failing to generate File Diff with
Null
error (#59709).Fixed an issue where Merge was taking longer than usual, and then failing with
Null Exception
(#60757).Fixed an issue where EZ-Commits and EZ-Merges were taking much longer than usual (#58098).
29 January 2023
(ARM v22.3.6) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where the deployment was failing with the following error when user was deploying Permissionset with a user-permission Manage Public Documents:
Permission Manage Public Documents depends on permission(s): Create Document, Delete Document, Edit Document, Read Document
(#60597).Fixed an issue where CI jobs were failing intermittently with the following error:
Getting access token failed from refresh tokenHTTP/1.1 400 Bad Request
(#59050).Fixed an issue where Reports deployment validation failed in EZ-Merge but was successful in EZ-Commit and Deployment modules (#57714).
Fixed an issue where user performed a merge and sent it for approval, but it was not available under the Commit history tab (#53759).
Fixed an issue where user initiated the prevalidation commit by enabling the destructive type but the deployment failed with an error
null
at Diff (#59919).Fixed an issue where Validate Deploy failed in QuickMerge and displayed the following message:
This folder unique name already exists for this folder type or has been previously used. Please choose a different name
(internal ticket).Fixed an issue where CI job wasn't considering the metadata changes, so the destructive changes were not being prepared or displayed on the build. (internal ticket).
22 January 2022
(ARM v22.3.5) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where user changed the permissions to list view from visible to all users to visible only for me while using the previous commit label, it is added under the Deleted tab (#59359).
Fixed an issue where commit was running for longer and remained in-progress and validation check log is also in progress (#59199).
Fixed an issue where commits with SFDX metadata structure are failing in metadata retrieval stage (#58888).
Fixed an issue where user couldn't create a managed package with the selected ancestor (#59044).
Fixed an issue where CI Job was occasionally failing with the error
BUILD FAILED
(#57647).Fixed an issue where CI job was taking the last modified user name if trigger through API instated of taking API token user (#55438).
Salesforce API version 57 (Beta support) is upgraded. The label is modified throughout ARM application including DataLoader and nCino (internal ticket).
Fixed an issue where nCino CI job was stuck in Build Success status for more than a week (#59040).
Fixed an issue where user was trying to deploy RBC (nCino Screens) and the deployment was failing for some of the objects, but there were no error messages shown on the UI (#58044).
Fixed an issue where user was using SSH credential in AutoRABIT but it was throwing the following error:
Invalid Private Key
(#59244).Fixed an issue where user has created a Commit label but it was not available while trying to perform an EZ-Merge (#55176).
Fixed an issue where user was not getting file Diff to commit the previously validated commit label and getting an error in the Diff (#59114).
Fixed an issue where user could not create an xml package for deployment because artifact creation and package manifest preparation were failing with an
invalid credentials
error (#59402).Fixed an issue where user was trying to perform single revision merge but validation deployment was failing with the following error
Metadata package is empty
(#59028).Fixed an issue where when there are special characters in Layout metadata then the user was not able to add it manually in Skip Members section (#58998).
Fixed an issue where user wanted to choose commit revision in a release label based on its comment but if the comment was not in text, it was not completely visible in the UI (#59014).
Fixed a UI bug where an incorrect validation message was seen while adding Skip Members manually (internal ticket).
Fixed an issue where the selected tab checkbox in the metadata components page in the EZ-Commit was not functioning as expected (internal ticket).
Fixed an issue where the EZ-Commit validation screen was displaying incorrect notification when name of the template was empty (internal ticket).
15 January 2022
(ARM v22.3.4) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where Merge validation failed to process when there was a Flow metadata (#58309).
Fixed an issue with user received 6 notifications for a failed CI Job instead of 1 (#58436).
Fixed an issue where user was trying to register branches to AutoRABIT through GitHub, but was getting the following error:
Lower Region
(#58888).Fixed a recurring issue where Commits and Merges were slowing down at a particular step, and EZ-Merge was failing with an error at commit phase (#51268).
Fixed an issue where while performing destructive changes in EZ-Commit, it was creating package.xml in root path folder in SFDX structure (#57868).
Fixed a UI bug on CI List and CI Results pages where when pagination was changed, the first 25 records were repeated (internal ticket).
Fixed an UI bug where the LastUsedDate column was not displayed in the Branch Table (internal ticket).
8 January 2022
(ARM v22.3.3) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where Admin was able to see the Teams field under ALM Integration but the same field was unavailable for sub-users (#55153).
Fixed an issue where Environment provisioning processes were failing to update when user was trying to change the email deliverability access level from No access to All email (#55208).
Fixed a build bug where CI Job Build was failing during package preparation step 5 failing while commiting DecisionMatrixDefinition and throwing an error (#58376).
Fixed an issue with Branching Baseline where the developers were migrating the changes from dev branch to INT, but Diff was showing 100% addition which is incorrect (#58478).
Fixed an issue where generating Diff for a Commit Label was taking much longer than expected (#55220).
Fixed an issue where Code coverage job was running 4 hours earlier than scheduled every time services were restarted (#54837).
Fixed an issue where SFDX scratch org was failing during data deployment but without any errors on UI, and the logs did not capture the failure either (#54837).
Fixed an issue where CheckMarx is executed successfully, but when trying to open the file user is the following error popup:
Result file not exists
(internal ticket).Fixed an issue where ActionCall and Decision Nodes were not shown in the Duplicate Resolving screen (internal ticket).
1 January 2022
(ARM v22.3.2) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where user was unable to create Environment Provisioning templates for multiple component types (#57898).
Fixed an issue where user was creating an EZ-Commit, mapping the ALM Project (VersionOne) but received the following error:
JSONObject["Assets"] is not a string
(#57238).Fixed an issue where AutoRABIT SSH credentials were failing with an error
Auth failed
while trying to connect with AWS CodeCommit (#53694).Fixed an issue where EZ-Commit Diff was taking approximately 4 hours while Refactoring CustomField, which is much longer than expected (#56650).
Fixed an issue where ExternalCredential metadata type was not getting excluded even when user added it in the excluded lists in CI Configuration (internal ticket).
Fixed an issue where after triggering Branching baseline, standard value set metadata type was getting displayed under the deleted components through Autodraft for Non-DX repo (internal ticket).
Fixed an issue where Destructive Components are not seen in case of PV-DX-Destructive Merge for Report metadata type. Instead, it displaying a message:
Package is empty
(internal ticket).Fixed an issue where Deployment was failing with certain Permission set metadatatypes that were not selected (internal ticket).
25 December 2022
(ARM v22.3.1) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where Provar jobs were failing due to incorrect files being copied from customer repository branch to Provar project directory (#56662).
Fixed an issue where user triggered a CI Job but it deployed with many more components than expected (#46983).
Fixed an issue where user was performing a single Merge with only two approval process, but while selecting SCA, process is auto rejected (#55671).
Fixed an issue where SFI components were not getting fetched in Commit and Deployment module (#55139).
Fixed an issue where non-admin users were unable to select Branch Type while trying to create a new branch from New EZ-Commit Branch (#57732).
Fixed an issue where CI jobs are failing intermittently with the following error:
Getting access token failed from refresh tokenHTTP/1.1 400 Bad Request
(#57371).Fixed an issue where user was trying to deploy only the Documents from the branch to Org, but deployment failed and Asynch ID is not generating (#57263).
Fixed an issue where user was trying to deploy login hours. First they merged it to target branch, then once CI job triggers login hours are not getting deployed to target org (#57359).
Fixed multiple issues where user was having trouble creating new package version from previous ancestor version (#55707).
Fixed an issue where Merge is failing with the following error:
failed to push some refs to 'https://github.com/salesforce-align/SFDX.git'
(#55939).Fixed an issue where the Standard Field Account.name is displayed in the deleted components list (#57396).
Fixed an issue where the prevalidation commit failed at delta stage (#55763).
Fixed an issue where user was unable to create commit label for the same repository second time, and branches were not displayed (internal ticket).
18 December 2022
(ARM v22.3.0) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue with DataLoader Pro where jobs executed in the last 6 months were not showing in the database process table and in the Reports module (#53980).
Fixed an issue with Deploy SFDX Source With ALM Mapping where CI job with ALM Mapping was not working as expected for Team which is not default (#55995).
Fixed an issue where Profile Diff is working as expected for Selective Deployment, but not while using the same profile in the profile manager (#52868).
Fixed an issue where Provar jobs were failing due to incorrect files being copied from customer repository branch to Provar project directory (#56662).
Fixed an issue where user triggered a CI Job but it deployed with many more components than expected (#46983).
Fixed an issue where user was creating an EZ-Commit, mapping the ALM Project (VersionOne) but received the following error:
JSONObject["Assets"] is not a string
(#57238).
ARM Release Notes 22.2
Date of release: 9 October 2022 Article last updated: 15 May 2023
New Features
1. Teams/Slack Notifications
Mail Settings module in the Admin section is relabeled as Notifications. Through this module, you can choose to send notifications about specific events triggered in ARM to specific groups or channels within your organization through Teams or Slack. For whichever messaging app you use, you can configure a webhook connection for each of the groups or channels, and then integrate them with ARM. You can customize and select which group(s) to notify when events like build failure, build success, deployment failure, merge reports, etc. are triggered.
2. Salesforce Scanner plugin
In addition to the existing static code analysis tools, ARM now provides the ability to choose the Salesforce Scanner CLI plugin.
Most static code analysis tools specialize in one language or a set of languages. Many applications (including typical Salesforce packages), however, contain an assortment of components created using different languages. A single static analyzer is insufficient to address all aspects of such applications, and managing multiple static analyzer tools could prove unfeasible.
This is where the Salesforce CLI Scanner plugin shines. This plugin aggregates the results of static analyzers that are most relevant to Salesforce developers while providing a unified experience.
With the Salesforce CLI Scanner plugin, you can look forward to a:
Single installation process
A single set of commands to interact with multiple rule engines
A unified set of rules that are checked by their respective rule engines
Unified rule violation report that includes all issues identified by the engines.
3. AutoRABIT for nCino
We’ve added the ability to view and review datasets corresponding to each version of the nCino feature template before using it for deployment. Prior to this release, the capability was available only for the latest version of the template.
Enhancements
1. ApexPMD Upgrade to 6.49 version
With this release, PMD has been upgraded to version 6.49. If you have not uploaded a rules file, ARM will use the default Apex PMD rules file. However, you can add new rules to the default ruleset.
Click HERE to view the list of currently deprecated rules available on GitHub.
2. Auto-approve on validation success
We have moved one step closer to automating the flow by adding an option to choose if an EZ-Commit or an EZ-Merge should be approved automatically if the SCA validation is successful. Combined with the existing option to auto-commit on approval, this leads to a true CI/CD experience.
3. HashiCorp Vault Integration
While adding HashiCorp credentials to ARM, you can now choose the AWS Authentication method so that the Vault Token will be generated automatically whenever the existing token expires. Now the user will not have to update the token manually from the application when it expires.
4. SFDX CLI Upgrade
The SFDX CLI has been upgraded to the latest stable 7.169 version.
Key characteristics to look for:
Support for the quick deploy functionality for SFDX jobs.
Use CLI commands to generate the package manifest and rollbacks.
5. Salesforce Winter (API 56.0) Support
To keep our product up to date with the most recent Salesforce updates, AutoRABIT supports the most recent API 56.0 version in this release. The most recent API version is intended for customizing the metadata model and developing tools to manage it.
6. Merge to multiple branches
With this release, you can choose to merge from one source branch to multiple destination branches upon successful deployment.
7. OAuth for Jira
In addition to the Standard access type, users can now set up SSO as authentication for Jira using the OAuth access type while registering an ALM. You can also switch between Standard and OAuth access types for already registered ALMs.
Improvements
Users with Admin access can now turn off the Jira comments and notifications created by AR. This ensures a cleaner workspace. These comments and notifications are very development centric, so the end users who use Jira cannot make sense of our technical comments from AR, and this may create confusion for them.
Changelogs
28 May 2023
(ARM v22.2.28) This is a maintenance release. The following items were fixed and/or added:
Fixed a compliance issue with Apache Commons by removing the text dependency (#71947).
Fixed an issue where CI Jobs were failing due to empty JSON file(s) in the remote repository, and throwing the following error:
Failed to initiate deployment. Unexpected end of JSON input
(#72217).Improved the UI by removing the Validate Deployment option if Vlocity is selected, and hiding the whole Board Type option if Vlocity is not enabled (#70993).
Fixed an issue where user was performing CI jobs for Validate and Deploy for a successful commit, but only validation was performed but not the deployment (#72751).
Fixed an issue where CI job deployment was failing because the build was picking duplicate Layout values (#71214).
Fixed an issue where Branching Baseline was not picking all the components from production (#70720).
Fixed an issue with nCino where CI jobs that used a Deployment from Version Control were failing when the build was triggered (#71914).
Improved the New Merge screen by adding Layouts text in the Skip Flow /Profile/ Perm.Set Access-Setting Duplicity Check option (internal ticket).
Fixed a UI bug where SF Org Test Connection notification message was displayed on an unrelated module (internal ticket).
Removed the option to sign up for a 30-day Salesforce trial while registering a DevHub as the trial offer is no longer applicable (internal ticket).
21 May 2023
(ARM v22.2.27) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where wrong timezone region was displaying for users (#71553).
Fixed an issue where the EZ-Commits report file displayed the file count but not the components count (#71538).
Fixed an issue where clone build jobs were taking between 10 and 25 minutes, which is much longer than expected (#70227).
Fixed an issue where CI job to generate Code Coverage Report was not reflected in the org or in the e-mail notification (#72042).
Fixed an issue where merge status is displayed as completed but no revision is generated, and the merge is not available in the UAT branch (#71266).
Enhanced DataLoader by adding the ability to field mapping through the lookup fields (#58480).
Fixed an issue with DataLoader where while running an Extract job on the PUBLISHER object, the job was failing with the following error
Publisher: column id is not supported in ORDER BY clause
(#71303).Enhanced the nCino filter criteria by adding the ability to search and filter labels using the whole or partial name (#71826).
Enhanced ARM by using known vulnerable components through the DataTables 1.10.12 plugin for advanced data table functionalities such as sorting, filtering, pagination, and more. This allows users to easily display and manipulate large sets of data on their web pages in a user-friendly manner (internal ticket).
Fixed an issue with Prevalidation Merge where users were unable to deploy the ApexClass Tests related to ApexClasses and Apex Triggers (internal ticket).
Fixed a UI bug where the date column in the EZ-Commit Weekly report was displaying incorrect values (internal ticket).
14 May 2023
(ARM v22.2.26) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where user was having trouble while deploying LighteningMessageChannel components (#70787).
Fixed an issue where Destructive Changes wasn't working as expected while performing an Entire Branch merge (#68882).
Enhanced the ALM management feature by adding an option to sync Smart Commits (#58904).
Fixed an issue with CI Jobs Destructive Sharing Rule was not deploying to the Salesforce org (#71183).
Fixed an issue where user could not disable the Smart Commits-Sync option for a repository branch in the VC repos section (#70854).
Improved the New Merge screen by removing the Validate Deployment option from the UI if Vlocity is selected (#70993).
Enhanced the Credentials module by adding SSH Cetificate option for Git Authentication (#67725).
Improved Release label creation by requiring at least two revisions to be selected (internal ticket).
Fixed an issue where Classic SF Org URL with a slash at the end of the URL redirects to the
400
error page, and for a Lightning SF Org URL without a slash gives anOAuth Authentication Failed
error message (internal ticket).Fixed an issue with nCino where user was getting a
NullPointerException
on Saving Permissions using Bulk Assignment (internal ticket).Fixed an issue with CI Jobs where all the scheduled timings were not displayed in the Preview & Save page (internal ticket).
Fixed an issue with Dataloader where user was able to upload a 900 MB file despite the limit being 100 MB, causing the process to hang (internal ticket).
Fixed an issue with Dataloader where sever crashed after user performed an Extract operation from an SF org which had Account Object with 2 million records (internal ticket).
07 May 2023
(ARM v22.2.25) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where user was getting a validation deployment error while performing release label deployment (#70400).
Fixed an issue where Branching Baseline was taking longer than expected (#67814).
Fixed an issue where using the AutoDraft functionality in EZ-Commit was resulting in a malformed exception in the UI (#70458).
Fixed an issue where Branching baseline was not picking all components from production (#70720).
Fixed an issue where prevalidation merge failed with empty metadata package even though there were changes in File Diff (#32256).
Fixed an issue where entire ARM application was down temporarily (#70658).
Fixed an issue where Merge was auto-rejected due to an empty package because the metadata folder path not being specified under branch settings (#69788).
Fixed an issue where user was using the Bulk Assignment feature to assign Sandbox permissions on the Permissions page but encountered the following error:
Java.lang.NullPointerException
(#70868).Fixed an issue where users weren't receiving SCA reports by email even though the reports were running (#70751).
Fixed an issue where while performing new EZ-Commit, user edited one line using review artifact option but Diff did not capture the same (#70270).
Fixed an issue where if CI Jobs were added in a queue with Scheduled jobs, then not all jobs were displayed in the queue (internal ticket).
Fixed an issue where existing revision file related delta still existed in agent even after uploading to rabitserver (internal ticket).
Fixed an issue where release label creation was failing when user tried to create package manifest and aborted and refreshed the label for DX repo (internal ticket).
Fixed an issue where Super admin user was getting a blank popup screen while trying to click on the Register Agent button from the Pool Mgmt screen (internal ticket).
09 April 2023
(ARM v22.2.23) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where Salesforce components were showing under the Apex Test Success tab in the Deployment module, which is not expected behavior (#67537).
Enhanced the Branching Baseline feature by allowing admin to define default baseline branches, making it easier for developers to choose the default branch for each project (#63571).
Fixed an issue where user was unable to register a branch even though Test Connection was successful (#67023).
Fixed an issue where ARM wasn't fetching the ApexClass Tests related to ApexTriggers upon selecting Run Tests Based On Changes option (#67503).
Fixed an issue where triggered CI jobs were taking too long to build, and also slowing down ARM altogether (#66846).
Fixed an issue where if the file name contained spaces, Commit Validation via VS Code plugin was unable to detect the file (#63518).
Fixed an issue where Search & Substitute was not updating the value for a custom label in the SF org (#66809).
Fixed an issue where there was a discrepancy between the changes captured in the ARM Diff and the repos in BitBucket (#60596).
Fixed an issue where the SF org URL is not displaying the updated one under Profile (#67718).
Fixed an issue with nCino where CI job filter changes on templates are not reflecting after saving (#66956).
Fixed an issue with Dataloader Pro where user tried to migrate Account Object Data with Attachments Object, but the logs verify that there is a Null Pointer Exception. (internal ticket).
Improved nCino by adding additional loggers for Branching baseline for user to view the status in the UI (internal ticket).
Fixed an issue where user was unable to filter while trying to select a job which had spaces in the job name (internal ticket).
19 March 2023
(ARM v22.2.22) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where CI job deployments were failing with the error,
Error 405 Only POST allowed
(#64228).Fixed an issue where multiple deployment requests were being generated while performing Org Sync if the user selected all components instead of a few (#51288).
Fixed an issue where Rollback API threw a 200 response but the Rollback immediately failed in the ARM UI (#65146).
Fixed an issue where SCA report Failed to run using the Codescan Plugin with the following Salesforce error
384187622-16951 (-673032061)
(#61676).Fixed an issue where after upgrading to ARM version 22.3 user was unable to approve EZ-Commits that were pending approval in the 22.2 (#64094).
Fixed an issue where user was trying to resolve a conflict in EZ-Merge but was getting a message on the UI that there are no conflicts (#64185).
Fixed an issue where Branching Baseline job does not delete files in static resources sub directories even though the user has selected the Delete existing metadata and commit new changes option (#64150).
Fixed an issue where user was unable to retrieve MutingPermissionSet using the SFDX repository (#64141).
Fixed an issue where the Release Label failed while creating the artifact (#64491).
Fixed an issue where Sharing Rule Set metadata type was found in the Deployment module but not in the Version Control module (#65060).
Fixed an issue where the user performed a merge and approved both level 1 and level 2 reviews but was unable to approve the merge (#65091).
Fixed an issue where errors were occuring while performing Delete Org (internal ticket).
Fixed an issue where for Build only job source from VC with DX repo, if Master Details Object Change is included in the build, we're getting No Modifications even if changes exist (internal ticket).
12 March 2023
(ARM v22.2.21) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where Static Code Anaysis was failing due to missing property tag in Apex PMD rules file, but the UI log wasn't displaying this error (#63554).
Fixed an issue where when there was no results generated, the report displayed an error that there are zero metrics instead of displaying the results as zero in all the places when there is no change (#63272).
Fixed an issue where user was unable to deploy a CI job with the RelationshipGraphDefinition components (#64145).
Fixed an issue where Validate deployment was displayed as failed in UI and the database, but was successful as per the logs (#63868).
Fixed an issue with Review Artifact where similar custom fields from different objects were not populating correctly and switching to other fields (#63676).
Fixed an issue where multiple fields of the respective custom objects were getting selected parallelly while performing edit or save or exit operations on the Review Artifact screen (internal ticket).
Enhanced ARM by adding an option for multiple ARM instances to share a single database cluster (internal ticket).
05 March 2023
(ARM v22.2.20) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where ARM was displaying incorrect installation settings and package version information in the deployment log while installing the package version from a CI job (#63544).
Fixed an issue where user chose Exclude Metadata Type for a particular metadata type during a CI Job, but it was still deployed (#62966).
Fixed an issue where user was unable to perform Destructive Commit with PermissionSetGroups metadata type (#63172).
Fixed an issue where users weren't receiving emails after setting up Mail Settings (#55070).
Fixed an issue where there was a discrepancy between EZ-Commit and Commit templates while retrieving Email Template metadata members (#61696).
Fixed an issue where Merge Labels were taking much longer than expected (#62625).
Fixed an issue where user tried to commit the changes without validation and UI displayed an error
Another commit is in progress
(#61930).Fixed a UI bug where there was a discrepancy in the timestamp displayed for a commit in the Commits History page (#61672).
Fixed an issue where Merge was not auto-rejected when validation criteria was not met (#62287).
Enhanced nCino by allowing users to deploy nCino CI build to multiple target sandboxes (#41763).
Fixed a UI bug where incorrect notification was displayed in certain components pages when template was created using one org and was used by another org (internal ticket).
Fixed an issue where Baseline Managed Package Changes option was not displayed on the UI when navigating from Package xml to select manually (internal ticket).
Fixed an issue where there was a discrepancy between the Attachments Records Success/Failure Count and the Retrieved Count when BULK API was enabled for Deployment (internal ticket).
26 February 2023
(ARM v22.2.19) This is a maintenance release. The following items were fixed and/or added:
Fixed a UI bug in Profile Manager where User Permissions differences are shown in the report but not in the UI (#61672).
Enhanced the Release Label creation by increasing the range of retrievable commit history (#61714).
Fixed an issue where user was unable to use Release Labels to perform Deployment, and it failed while trying to Create Artifact (#59429).
Fixed an issue where Release Artifact execution was failing when rabit home did not exist with an external agent (internal ticket).
Fixed a UI bug on the Profile screen where the expand option for the My Projects and My Roles sections was not working (internal ticket).
Fixed an issue where triggering Data Retention for Audit Tables was throwing the following error:
Unable to execute HTTP request: Read timed out
(internal ticket).Fixed an issue where extra characters are seen in the Fetch Commit History results while creating a Release Label with Vlocity label type (internal ticket).
Fixed an issue where user was unable to delete Apex test class on the SF Org Management page (internal ticket).
Enhanced nCino by introducing New Spreads Schedule tile in the Feature Creation screen (internal ticket).
Fixed an issue where if the fields did not load for Applied Mappings during deployment, no error was thrown by the application (internal ticket).
19 February 2023
(ARM v22.2.18) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where user was deploying single revision deployment with only report folder but sub-reports were also getting fetched, and the deployment was failing due to field dependency error (#61403).
Fixed an issue where after deployment with single revision merge, user permission appears to be removed in target org but in the Salesforce target org the user permission is not removed, and an incorrect layout is displayed in UI (#60531).
Fixed an issue where user performed a pre-validation commit and each process like file diff, validate deploy happened thrice as per the logs (#61079).
Fixed an issue where user was unable to select master branch as the parent branch while creating a new branch in EZ-Commit (#56188).
Fixed an issue where user was customer trying to register a Salesforce Org with Custom URL but it was failing with an error (#62192).
Fixed an issue where user user uploaded a YAML file to retrieve the Vlocity components but ALL metadata types were retrieved and displayed (#61181).
Fixed an issue where the same merge could be approved and rejected by different users simultaneously (#60859).
Fixed an issue where branch creation was faileing for sub-users in the EZ-Commit screen for Non-DX Repo (internal ticket).
Fixed an issue where Null Pointer was seen in Create Branch in EZ-Commit flow (internal ticket).
Fixed an issue where all credentials were listed twice in the Credentials dropdown in Create Branch in EZ-Commit flow (internal ticket).
Fixed an issue where branch creation was failing for sub-users in VC repos when the credential scope was private while Admin credentials were fetched (internal ticket).
Fixed an issue where user was unable to delete the Apex Test class under the SF org Apex default config (internal ticket).
Fixed an issue where the Add manually checkbox under Apex class config was selected by default (internal ticket).
Fixed an issue with nCino where user created a feature Deployment for Credit memo template with attachments, but Attachments Objects Data was not fetched, and the deployment failed with the following error:
Data file not fetched for object: Attachment
(internal ticket).Fixed an issue with nCino where Standard Features were not loaded in the Feature Management page (internal ticket).
12 February 2023
(ARM v22.2.17) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where user was unable to download success/failure reports in Single Dataloader (#61551).
Fixed an issue where when multiple CI Jobs are triggered, jobs are moved into the queue as expected, but new jobs are not starting automatically getting processed once the existing jobs is cleared from the CI Job results page (#59082).
Fixed an issue where Dependency order defined in json file was being changed on every commit but it was not supposed to (#57731).
Fixed an issue where Create Artifact was not working as expected while using Release Label (#61607).
Fixed an issue where user was performing an EZ-Commit with Review Artifact option and download the .zip file to make some changes, but was unable to upload it afterwards (#61751).
Fixed an issue where meta.xml file was not deleted from the repository after committing the destructive changes (#61736).
Fixed an issue where File Diff was empty in case of modified Uploaded via Review Artifact in PV Commit Flow (internal ticket).
Fixed an issue where Review Artifact Tree was not responding after uploading the modified file in Commit Flow (internal ticket).
Fixed an issue where User Permissions and Ip Ranges are completly removed from the branch after commiting the Permission Sets and Profiles (internal ticket).
Fixed an issue where Super Admin was getting an error while trying to activate newly signed up users (internal ticket).
05 February 2023
(ARM v22.2.16) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where SFDX module creation log shows that deployment is successful but the module creation had failed (#57318).
Fixed an issue with Backup from Org CI Jobs where PermissionSet User Permissions were being deleted (#59674).
Fixed an issue where Org to Org Deployment for Profiles including Deploy Profile Access Settings for selected components only was not working as expected (#60559).
Fixed an issue where Post Destruct fields were also added to Pre Destruct despite the user setting it to post (#61162).
Fixed an issue where user set the Max depth value as '0' under Vlocity Configuration Settings but it was retrieving all level dependancy components (#57501).
Fixed an issue with DataLoader where the Credit Memo Template migration was not deploying after user upgraded their instance (#57676).
Fixed an issue where user selected Custom Metadata members (records), but EZ-Commit was failing to generate File Diff with
Null
error (#59709).Fixed an issue where Merge was taking longer than usual, and then failing with
Null Exception
(#60757).Fixed an issue where EZ-Commits and EZ-Merges were taking much longer than usual (#58098).
29 January 2023
(ARM v22.2.15) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where the deployment was failing with the following error when user was deploying Permissionset with a user-permission Manage Public Documents:
Permission Manage Public Documents depends on permission(s): Create Document, Delete Document, Edit Document, Read Document
(#60597).Fixed an issue where CI jobs were failing intermittently with the following error:
Getting access token failed from refresh tokenHTTP/1.1 400 Bad Request
(#59050).Fixed an issue where Reports deployment validation failed in EZ-Merge but was successful in EZ-Commit and Deployment modules (#57714).
Fixed an issue where user performed a merge and sent it for approval, but it was not available under the Commit history tab (#53759).
Fixed an issue where user initiated the prevalidation commit by enabling the destructive type but the deployment failed with an error
null
at Diff (#59919).Fixed an issue where Validate Deploy failed in QuickMerge and displayed the following message:
This folder unique name already exists for this folder type or has been previously used. Please choose a different name
(internal ticket).Fixed an issue where CI job wasn't considering the metadata changes, so the destructive changes were not being prepared or displayed on the build. (internal ticket).
22 January 2022
(ARM v22.2.14) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where user changed the permissions to list view from visible to all users to visible only for me while using the previous commit label, it is added under the Deleted tab (#59359).
Fixed an issue where commit was running for longer and remained in-progress and validation check log is also in progress (#59199).
Fixed an issue where commits with SFDX metadata structure are failing in metadata retrieval stage (#58888).
Fixed an issue where user couldn't create a managed package with the selected ancestor (#59044).
Fixed an issue where CI Job was occasionally failing with the error
BUILD FAILED
(#57647).Fixed an issue where CI job was taking the last modified user name if trigger through API instated of taking API token user (#55438).
Salesforce API version 57 (Beta support) is upgraded. The label is modified throughout ARM application including DataLoader and nCino (internal ticket).
Fixed an issue where nCino CI job was stuck in Build Success status for more than a week (#59040).
Fixed an issue where user was trying to deploy RBC (nCino Screens) and the deployment was failing for some of the objects, but there were no error messages shown on the UI (#58044).
Fixed an issue where user was using SSH credential in AutoRABIT but it was throwing the following error:
Invalid Private Key
(#59244).Fixed an issue where user has created a Commit label but it was not available while trying to perform an EZ-Merge (#55176).
Fixed an issue where user was not getting file Diff to commit the previously validated commit label and getting an error in the Diff (#59114).
Fixed an issue where user could not create an xml package for deployment because artifact creation and package manifest preparation were failing with an
invalid credentials
error (#59402).Fixed an issue where user was trying to perform single revision merge but validation deployment was failing with the following error
Metadata package is empty
(#59028).Fixed an issue where when there are special characters in Layout metadata then the user was not able to add it manually in Skip Members section (#58998).
Fixed an issue where user wanted to choose commit revision in a release label based on its comment but if the comment was not in text, it was not completely visible in the UI (#59014).
Fixed a UI bug where an incorrect validation message was seen while adding Skip Members manually (internal ticket).
Fixed an issue where the selected tab checkbox in the metadata components page in the EZ-Commit was not functioning as expected (internal ticket).
Fixed an issue where the EZ-Commit validation screen was displaying incorrect notification when name of the template was empty (internal ticket).
15 January 2022
(ARM v22.2.13) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where Merge validation failed to process when there was a Flow metadata (#58309).
Fixed an issue with user received 6 notifications for a failed CI Job instead of 1 (#58436).
Fixed an issue where user was trying to register branches to AutoRABIT through GitHub, but was getting the following error:
Lower Region
(#58888).Fixed a recurring issue where Commits and Merges were slowing down at a particular step, and EZ-Merge was failing with an error at commit phase (#51268).
Fixed an issue where while performing destructive changes in EZ-Commit, it was creating package.xml in root path folder in SFDX structure (#57868).
Fixed a UI bug on CI List and CI Results pages where when pagination was changed, the first 25 records were repeated (internal ticket).
Fixed an UI bug where the LastUsedDate column was not displayed in the Branch Table (internal ticket).
8 January 2022
(ARM v22.2.12) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where Admin was able to see the Teams field under ALM Integration but the same field was unavailable for sub-users (#55153).
Fixed an issue where Environment provisioning processes were failing to update when user was trying to change the email deliverability access level from No access to All email (#55208).
Fixed a build bug where CI Job Build was failing during package preparation step 5 failing while commiting DecisionMatrixDefinition and throwing an error (#58376).
Fixed an issue with Branching Baseline where the developers were migrating the changes from dev branch to INT, but Diff was showing 100% addition which is incorrect (#58478).
Fixed an issue where generating Diff for a Commit Label was taking much longer than expected (#55220).
Fixed an issue where Code coverage job was running 4 hours earlier than scheduled every time services were restarted (#54837).
Fixed a UI bug where scrollbar and pagination were not visible on the Org Sync History page (internal ticket).
01 January 2022
(ARM v22.2.11) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where Deployment was failing with no changes in the package (internal ticket).
Fixed an issue where user was unable to create Environment Provisioning templates for multiple component types (#57898).
Fixed an issue where user was creating an EZ-Commit, mapping the ALM Project (VersionOne) but received the following error:
JSONObject["Assets"] is not a string
(#57238).Fixed an issue where AutoRABIT SSH credentials were failing with an error
Auth failed
while trying to connect with AWS CodeCommit (#53694).Fixed an issue where EZ-Commit Diff was taking approximately 4 hours while Refactoring CustomField, which is much longer than expected (#56650).
Fixed an issue where ExternalCredential metadata type was not getting excluded even when user added it in the excluded lists in CI Configuration (internal ticket).
Fixed an issue where after triggering Branching baseline, standard value set metadata type was getting displayed under the deleted components through Autodraft for Non-DX repo (internal ticket).
Fixed an issue where Destructive Components are not seen in case of PV-DX-Destructive Merge for Report metadata type. Instead, it displaying a message:
Package is empty
(internal ticket).
25 December 2022
(ARM v22.2.10) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where Provar jobs were failing due to incorrect files being copied from customer repository branch to Provar project directory (#56662).
Fixed an issue where user triggered a CI Job but it deployed with many more components than expected (#46983).
Fixed an issue where user was performing a single Merge with only two approval process, but while selecting SCA, process is auto rejected (#55671).
Fixed an issue where SFI components were not getting fetched in Commit and Deployment module (#55139).
Fixed an issue where non-admin users were unable to select Branch Type while trying to create a new branch from New EZ-Commit Branch (#57732).
Fixed an issue where CI jobs are failing intermittently with the following error:
Getting access token failed from refresh tokenHTTP/1.1 400 Bad Request
(#57371).Fixed an issue where user was trying to deploy only the Documents from the branch to Org, but deployment failed and Asynch ID is not generating (#57263).
Fixed an issue where user was trying to deploy login hours. First they merged it to target branch, then once CI job triggers login hours are not getting deployed to target org (#57359).
Fixed multiple issues where user was having trouble creating new package version from previous ancestor version (#55707).
Fixed an issue where Merge is failing with the following error:
failed to push some refs to 'https://github.com/salesforce-align/SFDX.git'
(#55939).Fixed an issue where the Standard Field Account.name is displayed in the deleted components list (#57396).
Fixed an issue where the prevalidation commit failed at delta stage (#55763).
Fixed an issue where user was unable to create commit label for the same repository second time, and branches were not displayed (internal ticket).
18 December 2022
(ARM v22.2.9) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue with DataLoader Pro where jobs executed in the last 6 months were not showing in the database process table and in the Reports module (#53980).
Fixed an issue with Deploy SFDX Source With ALM Mapping where CI job with ALM Mapping was not working as expected for Team which is not default (#55995).
Fixed an issue where Profile Diff is working as expected for Selective Deployment, but not while using the same profile in the profile manager (#52868).
Fixed an issue where Provar jobs were failing due to incorrect files being copied from customer repository branch to Provar project directory (#56662).
Fixed an issue where user triggered a CI Job but it deployed with many more components than expected (#46983).
Fixed an issue where user was creating an EZ-Commit, mapping the ALM Project (VersionOne) but received the following error:
JSONObject["Assets"] is not a string
(#57238).
11 December 2022
(ARM v22.2.8) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where SFI components were not getting fetched in Commit and Deployment module (#55139).
Fixed an issue where multiple metadata types where not able to retrieve (#56668).
Fixed an issue where Commit Label is not Auto rejected when the validation criteria is not met (#55670).
Fixed an issue where user performed a merge and sent it for approval, but it was not available under the Commit history tab (#53759).
Enhanced the Conflict Resolution Log by adding additional loggers like strategy chosen to resolve the conflict and which user did the resolution (#47559).
Fixed an issue where Commits added from non-nCino Repositories were not cleared from the Workspace causing the Commit to either not be visible in the UI or it is added to the queue but not deployed to the Destination Org (internal ticket).
Fixed an issue where user was creating the feature template for some of the nCino objects but it was taking too long to retrieve the objects from Source Org (#53915).
Enhanced nCino to:
Modify notification messages for null checks on request parameters (internal ticket).
Display only nCino revisions for Version Control in nCino feature deployment (internal ticket).
04 December 2022
(ARM v22.2.7) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where Flexi pages were not picked up in a CI Job even after the commit with same set of metadata was excluded by user (#54518).
Fixed an issue where Abort function to stop Provar jobs was not working as expected (#55511).
Fixed an issue where production backup CI Job was not picking all the changes, and when user modified the job configuration and retriggered the job, the application was throwing the following error
java.lang.NullPointerException: null
(#55213).Fixed an issue where all Slack Notifications were selected by default and user was unable to unselect all at once (#55817).
Fixed an issue where SFI components were not being fetched both in Commit and Deployment modules (#55139).
Fixed an issue with DataLoader Pro where user selected a field as External ID in a job and saved it, but the saved entry was lost and user was unable to map it (#55011).
Fixed an issue where Deployment validation in Prevalidation Commit fails because profile validation automatically picks User Permissions even though Remove User Permissions option is selected (#54941).
Fixed an issue where user was performing a single Merge with only two approval process, but while selecting SCA, process is auto rejected (#55671).
Fixed an issue where Commit Label is not Auto rejected when the validation criteria is not met (#55670).
Fixed an issue where Release Label Merge was failing and throwing the following error:
fatal: bad revision
(#55000).Fixed an issue with EZ-Commit where user was unable to upload a Custom YAML file (#55826).
Fixed an issue where the Vlocity Component option under Fetch Changes is not populating for sub-users with roles that have all permissions and access (#54962).
Fixed an issue where Commits added from non-nCino Repositories were not cleared from the Workspace causing the Commit to either not be visible in the UI or it is added to the queue but not deployed to the Destination Org (internal ticket).
Fixed an issue where user was performing a merge operation and validating the package on the target org but the validation was failing with multiple errors (#55541).
27 November 2022
(ARM v22.2.6) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where user was trying to migrate Products, Pricebooks, and its entries but the Deploy was failing for Pricebook and throwing the following error:
INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY: insufficient access rights on cross-reference id:--
(#55263).Fixed an issue with nCino where user was trying to create a custom feature template including product objects as well as product line but the deployment was failing with the following error:
Required fields are missing: [LLC_BI_Product_Line_c]
(#51209).Fixed an issue with nCino where CI Job was stuck in Build Success status (#53605).
Fixed an issue where CI Job build was failing with a NullPointerException (#55204).
Fixed an issue where the Repository Branch was unavailable to select to run the Merge process after selecting On successful deployment option (#55537).
Fixed an issue where Admin was able to see the Teams field under ALM Integration but the same field was unavailable for sub-users (#55153).
Fixed an issue where user was getting a NullPointerException when trying to resolve a Merge conflict (#55137).
Fixed an issue with nCino where the UTF-8 Encoding Flag was not displayed in the pop-up during Re-Deployments (internal ticket).
Fixed an issue where during an EZ-Commit, complete information about some of the members of WaveDataflow metadata type was not retreived from the Salesforce Org (#49753).
Fixed an issue where Quick Merge was throwing the following error after clicking Validate & Merge:
Please Select Valid revision
(#53932 ).Fixed an issue with EZ-Commit where Autodraft feature was taking too long and eventually failing when user was trying to retrieve components (#48257).
Fixed an issue where user was able to create a Delegated Group but was unable to add a Delegated Admin user to the group using Environment Provisioning (#55266).
20 November 2022
(ARM v22.2.5) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where user was performing Prevalidation Commit but commits in the repository have different components than the ones shown in Diff before the commit (#52307).
Fixed an issue with Install an Unlocked or Managed Package from a Version Control Branch where CI job getting an exception and the build status was showing as successful but the Scratch Org was not being created (#50702).
Fixed an issue where CI Job shows that the ALM status has been updated successfully but on Azure ALM it is not updated (#54669).
Fixed an issue where Test Automation CI Jobs were failing due to InitializeDriver & quit methods (#45878).
Fixed a bug where user was able to access certain branches in the Deployment module to which he did not have access under Profile Settings (#54879).
Fixed an issue with CI Jobs where the build failed with Checkout conflict for an .svg file (#54172).
Fixed an issue with nCino where Record Classification and Classification Objects were missing in the template (internal ticket).
Fixed an issue with nCino where user was creating a CI Job and observed that
Use UTF-8 file encoding for the file read and write operations
flag was displayed at the bottom below the Commit Details section (internal ticket).Fixed an issue with nCino where the UTF-8 Encoding Flag was not displayed in the pop-up during Re-Deployments (internal ticket).
Fixed an issue where during an EZ-Commit, complete information about some of the members of WaveDataflow metadata type was not retreived from the Salesforce Org (#49753).
Fixed an issue where Quick Merge was throwing the following error after clicking Validate & Merge:
Please Select Valid revision
(#53932 ).Fixed an issue with EZ-Commit where Autodraft feature was taking too long and eventually failing when user was trying to retrieve components (#48257).
Fixed an issue where user was unable to add another branch to Azure in the ALM MGMT Repository mappings (#55133).
Fixed an issue where the Destructive commit Diff was including more components than selected (#54795).
Fixed an issue where a merge got stuck for a long time and the Commit ID was reflected in BitBucket but unavailable to select for release label deployment (#52964).
13 November 2022
(ARM v22.2.4) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where the user was trying to create an Extract process in DataLoader but after validating the query the application was throwing an error:
not supported; requires @DynamoDBTyped or @DynamoDBTypeConverted
(#54648).Fixed an issue with CI Jobs where External Credential metadata was not identified during Deployment (#53939).
Fixed an issue with DX CI Jobs where user is not getting details of faulty commit revisions in the notification (#54063).
Fixed an issue with Profile Manager where the deployment is not showing any progress in the logger detail in front end. It was updated only after completion of the deployment job at backend (#53706).
Enhanced the Conflict Resolution Log by adding additional loggers like strategy chosen to resolve the conflict and which user did the resolution (#47559).
Fixed a bug where Merge Commit validation was not considering special characters like %,#, etc. as a value and throwing the following error:
Merge comment should not contain an empty space
(#54512).Fixed an issue where ARM was slowing at different phases in the EZ-Commit module (#50503).
Fixed an issue where Git check response was not delivered for validation CI Job even though user has added the comment for a Pull request in the remote repository (#53036).
06 November 2022
(ARM v22.2.3) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue with DX CI Job where user selected Do Not Include Skip Members but the respective mapper reports were not skipped (internal ticket).
Fixed an issue where the Deployment module page was loading very slowly and then throwing an error:
Page Unresponsive
(#53675).Fixed the following issues in CI and Reports modules (internal ticket):
Build With NULL ERROR (issue exists both with Proxy and without Proxy)
SF Org Code coverage Execution is failing (issue exists both with Proxy and without Proxy)
Jenkins Build is updated with FAILED status even after it is successfully completed (issue exists only without Proxy)
Checkmarx text is not displaying the Proxy Configuration note (Only With Proxy)
Fixed an issue with QA Environments where user was unable to create and delete the SFDX module because of the Apache config CACHE settings (internal ticket).
Fixed an issue with the Deployment module where user initiated a Deployment without selecting the Do not Include Skip Members option, but this option was auto-enabled and skipped the member at the time of deployment (#53747).
Fixed an issue with Modularization where user creating a module and selected the Ignore installed components check box but the installed components were not ignored causing the deployment to fail (#53703).
Fixed an issue with AccelQ Test Automation where test case fails but the error details pop-up is not showing the details of the error that caused the failure (#54224).
Fixed an issue where user is setting up the Apex PMD rules as Priority 1 & Priority 2 in the CI Job but the SCA Report is showing the Priority 3, P4 & P5 which wasn't selected (#54017).
Fixed an issue where the Git check response was not delivered for a validation CI Job (#53036).
Fixed an issue where the Deleted Report metadata components were not found in the EZ-Commit (#53119).
Fixed an issue where user was trying to perform a Quick Merge but was getting an Undefined error for all labels (internal ticket).
30 October 2022
(ARM v22.2.2) This is a maintenance release. The following items were fixed and/or added:
Fixed a UI bug on the CI Jobs page for Install an Unlocked or Managed Package from a Version Control Branch type where old Dev Hubdropdown list was displayed in the Deploy section (internal ticket).
Fixed an issue with AccelQ where running a test execution was successful even before the jobs were completed in AccelQ, but the status was always showing as Not Run instead of Success or Failure even if the jobs have been successfully completed (#50181).
Fixed a Page Unresponsive issue while creating a new Release Label by adding a feature to list limited results on each page (#48563).
Fixed an issue where user created a Release Label, performed a Merge operation, committed changes to the target branch, and created two revisions in the Github branch. But ARM was throwing an error while applying merge stage and only on the revision generated (#51364).
Fixed an issue where EZ-Commit initiation was stuck with the error:
Unable to fetch Salesforce Org users. Reason: Invalid login: invalid user name or password or security token or api version or user locked out
(#52550).Fixed an issue where Page Size value on the Edit Release Label screen is defaulting to the previous value instead of the set value (internal ticket).
Fixed a UI bug where OK Button in Automation is not visible in the Create Release Label pop-up when opened in 100% zoom (internal ticket).
23 October 2022
(ARM v22.2.1) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where CI Job was successful but was including components from GIT revisions from old deleted branches (#46983).
Fixed an issue where user was performing a production deployment using CI job for an object, but it failed with the following error:
Cannot set sharingModel to ControlledByParent on a CustomObject without a MasterDetail relationship field
(#48626).Fixed an issue where CI Job was getting an exception, Build status was showing as successful, but Scratch Org not getting created (#50702).
Fixed an issue where Managed Package was picking the wrong ancestor by adding a feature to manually select the preferred ancestor while creating a package version (#48311).
Fixed an issue where user was adding URLs to the Proxy Configuration Settings but the URL List was not reflecting the same (internal ticket).
Fixed an issue where Custom Template Creation failed and the Logs did not record the reason for failure (#52147).
Fixed an issue where the Created By value was not visible in Dataloader, Dataloader Pro DL Config, and the TestEnv History page (internal ticket).
Fixed an issue where the Comment Box was not accepting more than 100 characters while rejecting a Commit, but was working as expected while approving a commit (#51384).
Fixed an issue where user set Commit validation Criteria to Auto reject after 7 days but the older Pre-validation commits are not auto rejected after 7 days (#49874).
Fixed an issue where user cannot add Skip members manually and it is failing due to special characters being included (#53139).
16 October 2022
(ARM v22.2.0) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where skipped members were present in many components but only Report Metadata was failing during Deployment (#51040).
Fixed an issue where CI Job was getting stuck in In Progress status but the log showed that the deployment was successful (#51140).
Fixed an issue where GitHub login credentials were not working when user triggered a CI Job for the second time (#50630).
Fixed an issue where CI Job has failed in the Salesforce org, but still stuck in In Progress status in ARM (#50435).
Fixed an issue where user raised a Pull request on a branch and was getting a webhook response, but CI Job build was not triggered (#51592).
Fixed a UI bug where Add to dashboard button was unavailable for widgets (#52333).
Fixed an issue where a new database file is created and overwritten with an existing database file whenever the server was restarted (internal ticket).
Fixed an issue where user was trying to resolve conflicts on Merge Request Labels created more than 7 days ago, but application was throwing an error:
undefined
(internal ticket).Fixed an issue where Custom Email Template was not working for Email notifications (#47484).
Fixed an issue where user was testing SSH Connection but the application was throwing an error:
invalid privateKey
(#50940).Fixed an issue with nCino where UI Log was not generated for failed CI Jobs (#50442).
Fixed an issue where New EZ-Merge was throwing an error (#46754).
Fixed an issue where Audit Logs were not generating via Postman Services (#50221).
Fixed an issue where Commits were getting stuck and throwing the following error:
No credential have been found with Name:git
, but was not reflecting in the UI log (#51713).Fixed an issue with Workspace Settings where unused workspaces were not being cleared despite selecting Clear all workspaces which are not used in last 7 days (#50164).
Fixed an issue where user was performing a Prevalidation EZ-Commit and found that some Layout Assignments were deleted though those layouts were not part of the commit (#50945).
Fixed an issue with nCino where migration was failing due to errors with Standard Screen and UI Templates (#50432).
ARM Release Notes 22.1
Date of release: 20 March 2022 Article last updated: 23 October 2022
New features
1. Squash and merge
We have added the Squash and Merge feature in this release. Sometimes, when merging a long list of changes from a development branch into the master, it's helpful to squash those commits into one change for ease of review and declutter the repo's commit history. AutoRABIT offers an option to squash all commits in a merge request into one commit after the merge is approved and completed.

2. SFDX- Import packages
Packages
The users could previously build a new package (unlocked or managed) and update the package's version in Salesforce DX. With this release, you may now import packages and update the version of packages created outside of AutoRABIT.

Dev Hub management
With this update, users will see all of the packages in their dev hub in the record view. You may expand each package to show the package's versions in order and package data such as version name, version number, ancestor version, ancestor dependencies, etc.

3. Step-based rollback
The option to list the API-supported and unsupported API components is added to the CI job/deployment rollback. If such components may be deployed to the target environment but do not have API support to delete them, ARM will display them individually as unsupported API types. Take, for example, RecordType.
The RecordType component may be deployed to the target environment, but it cannot be removed; instead, we need to connect to the target Salesforce environment to deactivate the component.

Enhancements
1. Checkmarx upgrade to v9.4.1
Checkmarx has been updated to version 9.4.1. Earlier, Checkmarx used a username/password-based authentication method. Now, the user will be able to use token-based authentication with the Checkmarx upgrade.
2. Export all users
The Export All Users feature allows the org admins to export a CSV file of all the users currently in their account. We now have added the following fields to the existing CSV file:
CreatedDate
CreatedByName
DeativatedDate
LastLoginDate
DeactivatedByName
LastModifiedDate
LastModifiedByName.
3. Pull request support for Azure cloud repositories
We have extended the support of having the pull request support in the CI Job for the Azure repository. This feature was previously available for Github cloud/Enterprise and Bitbucket cloud/Enterprise; however, we've added support for Azure cloud repositories (DX and non-DX repositories) with this release.
4. Merge/commit approval eligibility
If you want to make sure one or more people approve every commit or merge, you can enforce this workflow by using merge/commit approvals. These approvals allow you to set the number of necessary approvals to approve every commit/ merge in a project.
The org admins' eligibility level has been enhanced with the ARM 22.1 version. If you're an administrator, you will have the privilege to approve self-merge even if the criteria to self-approve a merge is set to FALSE. This permission will be denied to all members of your team except the org admin. To put it another way, no criteria can restrict an org administrator from approving any EZ-commit/ EZ-Merge.

5. CodeScan additional metadata support
We have enhanced the scope for analysis of what CodeScan does by adding support for additional metadata and rules. For our ARM users who want to incorporate the SCA tool into their subscriptions, CodeScan would be their first choice as it now supports more robust integrations.
Below is the list of CodeScan supported metadata types:
Apex Triggers
Apex Classes
Aura Definition Bundles
Lightning Component Bundles (LWC)
Visualforce Pages
Custom Object
Settings
Flows
Workflows
Profiles
Sharing Rules
Sharing Criteria Rules
Sharing Owner Rules
Sharing Territory Rules
Permission Sets
6. SFDX CLI update
The SFDX CLI has been upgraded to the latest stable 7.134 version.
Key characteristics to look for:
Single deployment request for constructive and destructive changes
Quick deploy and rollbacks work for both constructive and destructive changes
Package preparation has been improved.
Improvements
The jquery-UI version has been upgraded to v1.13.0 to fix security issues. Upgrading to the most recent version of jquery makes our application more secure and potentially faster in script execution and loading.
Minor performance, bug fixes, and security improvements can also be observed in the ARM portal.
Changelogs
21 May 2023
(ARM v22.1.48) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where wrong timezone region was displaying for users (#71553).
Fixed an issue where the EZ-Commits report file displayed the file count but not the components count (#71538).
Fixed an issue where clone build jobs were taking between 10 and 25 minutes, which is much longer than expected (#70227).
Fixed an issue where CI job to generate Code Coverage Report was not reflected in the org or in the e-mail notification (#72042).
Fixed an issue where merge status is displayed as completed but no revision is generated, and the merge is not available in the UAT branch (#71266).
Enhanced DataLoader by adding the ability to field mapping through the lookup fields (#58480).
Fixed an issue with DataLoader where while running an Extract job on the PUBLISHER object, the job was failing with the following error
Publisher: column id is not supported in ORDER BY clause
(#71303).Enhanced the nCino filter criteria by adding the ability to search and filter labels using the whole or partial name (#71826).
Enhanced ARM by using known vulnerable components through the DataTables 1.10.12 plugin for advanced data table functionalities such as sorting, filtering, pagination, and more. This allows users to easily display and manipulate large sets of data on their web pages in a user-friendly manner (internal ticket).
Fixed an issue with Prevalidation Merge where users were unable to deploy the ApexClass Tests related to ApexClasses and Apex Triggers (internal ticket).
Fixed a UI bug where the date column in the EZ-Commit Weekly report was displaying incorrect values (internal ticket).
09 April 2023
(ARM v22.1.46) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where Salesforce components were showing under the Apex Test Success tab in the Deployment module, which is not expected behavior (#67537).
Enhanced the Branching Baseline feature by allowing admin to define default baseline branches, making it easier for developers to choose the default branch for each project (#63571).
Fixed an issue where user was unable to register a branch even though Test Connection was successful (#67023).
Fixed an issue where ARM wasn't fetching the ApexClass Tests related to ApexTriggers upon selecting Run Tests Based On Changes option (#67503).
Fixed an issue where triggered CI jobs were taking too long to build, and also slowing down ARM altogether (#66846).
Fixed an issue where if the file name contained spaces, Commit Validation via VS Code plugin was unable to detect the file (#63518).
Fixed an issue where Search & Substitute was not updating the value for a custom label in the SF org (#66809).
Fixed an issue where there was a discrepancy between the changes captured in the ARM Diff and the repos in BitBucket (#60596).
Fixed an issue where the SF org URL is not displaying the updated one under Profile (#67718).
Fixed an issue with nCino where CI job filter changes on templates are not reflecting after saving (#66956).
Fixed an issue with Dataloader Pro where user tried to migrate Account Object Data with Attachments Object, but the logs verify that there is a Null Pointer Exception. (internal ticket).
Improved nCino by adding additional loggers for Branching baseline for user to view the status in the UI (internal ticket).
Fixed an issue where user was unable to filter while trying to select a job which had spaces in the job name (internal ticket).
25 December 2022
(ARM v22.1.38) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where Provar jobs were failing due to incorrect files being copied from customer repository branch to Provar project directory (#56662).
Fixed an issue where user triggered a CI Job but it deployed with many more components than expected (#46983).
Fixed an issue where user was performing a single Merge with only two approval process, but while selecting SCA, process is auto rejected (#55671).
Fixed an issue where SFI components were not getting fetched in Commit and Deployment module (#55139).
Fixed an issue where non-admin users were unable to select Branch Type while trying to create a new branch from New EZ-Commit Branch (#57732).
Fixed an issue where CI jobs are failing intermittently with the following error:
Getting access token failed from refresh tokenHTTP/1.1 400 Bad Request
(#57371).Fixed an issue where user was trying to deploy only the Documents from the branch to Org, but deployment failed and Asynch ID is not generating (#57263).
Fixed an issue where user was trying to deploy login hours. First they merged it to target branch, then once CI job triggers login hours are not getting deployed to target org (#57359).
Fixed multiple issues where user was having trouble creating new package version from previous ancestor version (#55707).
Fixed an issue where Merge is failing with the following error:
failed to push some refs to 'https://github.com/salesforce-align/SFDX.git'
(#55939).Fixed an issue where the Standard Field Account.name is displayed in the deleted components list (#57396).
Fixed an issue where the prevalidation commit failed at delta stage (#55763).
Fixed an issue where user was unable to create commit label for the same repository second time, and branches were not displayed (internal ticket).
11 December 2022
(ARM v22.1.37) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where SFI components were not getting fetched in Commit and Deployment module (#55139).
Fixed an issue where multiple metadata types where not able to retrieve (#56668).
Fixed an issue where Commit Label is not Auto rejected when the validation criteria is not met (#55670).
Fixed an issue where user performed a merge and sent it for approval, but it was not available under the Commit history tab (#53759).
Enhanced the Conflict Resolution Log by adding additional loggers like strategy chosen to resolve the conflict and which user did the resolution (#47559).
Fixed an issue where Commits added from non-nCino Repositories were not cleared from the Workspace causing the Commit to either not be visible in the UI or it is added to the queue but not deployed to the Destination Org (internal ticket).
Fixed an issue where user was creating the feature template for some of the nCino objects but it was taking too long to retrieve the objects from Source Org (#53915).
Enhanced nCino to:
Modify notification messages for null checks on request parameters (internal ticket).
Display only nCino revisions for Version Control in nCino feature deployment (internal ticket).
04 December 2022
(ARM v22.1.36) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where Flexi pages were not picked up in a CI Job even after the commit with same set of metadata was excluded by user (#54518).
Fixed an issue where Abort function to stop Provar jobs was not working as expected (#55511).
Fixed an issue where production backup CI Job was not picking all the changes, and when user modified the job configuration and retriggered the job, the application was throwing the following error
java.lang.NullPointerException: null
(#55213).Fixed an issue where all Slack Notifications were selected by default and user was unable to unselect all at once (#55817).
Fixed an issue where SFI components were not being fetched both in Commit and Deployment modules (#55139).
Fixed an issue with DataLoader Pro where user selected a field as External ID in a job and saved it, but the saved entry was lost and user was unable to map it (#55011).
Fixed an issue where Deployment validation in Prevalidation Commit fails because profile validation automatically picks User Permissions even though Remove User Permissions option is selected (#54941).
Fixed an issue where user was performing a single Merge with only two approval process, but while selecting SCA, process is auto rejected (#55671).
Fixed an issue where Commit Label is not Auto rejected when the validation criteria is not met (#55670).
Fixed an issue where Release Label Merge was failing and throwing the following error:
fatal: bad revision
(#55000).Fixed an issue with EZ-Commit where user was unable to upload a Custom YAML file (#55826).
Fixed an issue where the Vlocity Component option under Fetch Changes is not populating for sub-users with roles that have all permissions and access (#54962).
Fixed an issue where Commits added from non-nCino Repositories were not cleared from the Workspace causing the Commit to either not be visible in the UI or it is added to the queue but not deployed to the Destination Org (internal ticket).
Fixed an issue where user was performing a merge operation and validating the package on the target org but the validation was failing with multiple errors (#55541).
27 November 2022
(ARM v22.1.35) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where user was trying to migrate Products, Pricebooks, and its entries but the Deploy was failing for Pricebook and throwing the following error:
INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY: insufficient access rights on cross-reference id:--
(#55263).Fixed an issue with nCino where user was trying to create a custom feature template including product objects as well as product line but the deployment was failing with the following error:
Required fields are missing: [LLC_BI_Product_Line_c]
(#51209).Fixed an issue with nCino where CI Job was stuck in Build Success status (#53605).
Fixed an issue where CI Job build was failing with a NullPointerException (#55204).
Fixed an issue where the Repository Branch was unavailable to select to run the Merge process after selecting On successful deployment option (#55537).
Fixed an issue where Admin was able to see the Teams field under ALM Integration but the same field was unavailable for sub-users (#55153).
Fixed an issue where user was getting a NullPointerException when trying to resolve a Merge conflict (#55137).
Fixed an issue with nCino where the UTF-8 Encoding Flag was not displayed in the pop-up during Re-Deployments (internal ticket).
Fixed an issue where during an EZ-Commit, complete information about some of the members of WaveDataflow metadata type was not retreived from the Salesforce Org (#49753).
Fixed an issue where Quick Merge was throwing the following error after clicking Validate & Merge:
Please Select Valid revision
(#53932 ).Fixed an issue with EZ-Commit where Autodraft feature was taking too long and eventually failing when user was trying to retrieve components (#48257).
Fixed an issue where user was able to create a Delegated Group but was unable to add a Delegated Admin user to the group using Environment Provisioning (#55266).
20 November 2022
(ARM v22.1.34) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where user was performing Prevalidation Commit but commits in the repository have different components than the ones shown in Diff before the commit (#52307).
Fixed an issue with Install an Unlocked or Managed Package from a Version Control Branch where CI job getting an exception and the build status was showing as successful but the Scratch Org was not being created (#50702).
Fixed an issue where CI Job shows that the ALM status has been updated successfully but on Azure ALM it is not updated (#54669).
Fixed an issue where Test Automation CI Jobs were failing due to InitializeDriver & quit methods (#45878).
Fixed a bug where user was able to access certain branches in the Deployment module to which he did not have access under Profile Settings (#54879).
Fixed an issue with CI Jobs where the build failed with Checkout conflict for an .svg file (#54172).
Fixed an issue with nCino where Record Classification and Classification Objects were missing in the template (internal ticket).
Fixed an issue with nCino where user was creating a CI Job and observed that
Use UTF-8 file encoding for the file read and write operations
flag was displayed at the bottom below the Commit Details section (internal ticket).Fixed an issue with nCino where the UTF-8 Encoding Flag was not displayed in the pop-up during Re-Deployments (internal ticket).
Fixed an issue where during an EZ-Commit, complete information about some of the members of WaveDataflow metadata type was not retreived from the Salesforce Org (#49753).
Fixed an issue where Quick Merge was throwing the following error after clicking Validate & Merge:
Please Select Valid revision
(#53932 ).Fixed an issue with EZ-Commit where Autodraft feature was taking too long and eventually failing when user was trying to retrieve components (#48257).
Fixed an issue where user was unable to add another branch to Azure in the ALM MGMT Repository mappings (#55133).
Fixed an issue where the Destructive commit Diff was including more components than selected (#54795).
Fixed an issue where a merge got stuck for a long time and the Commit ID was reflected in BitBucket but unavailable to select for release label deployment (#52964).
13 November 2022
(ARM v22.1.33) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where the user was trying to create an Extract process in DataLoader but after validating the query the application was throwing an error:
not supported; requires @DynamoDBTyped or @DynamoDBTypeConverted
(#54648).Fixed an issue with CI Jobs where External Credential metadata was not identified during Deployment (#53939).
Fixed an issue with DX CI Jobs where user is not getting details of faulty commit revisions in the notification (#54063).
Fixed an issue with Profile Manager where the deployment is not showing any progress in the logger detail in front end. It was updated only after completion of the deployment job at backend (#53706).
Enhanced the Conflict Resolution Log by adding additional loggers like strategy chosen to resolve the conflict and which user did the resolution (#47559).
Fixed a bug where Merge Commit validation was not considering special characters like %,#, etc. as a value and throwing the following error:
Merge comment should not contain an empty space
(#54512).Fixed an issue where ARM was slowing at different phases in the EZ-Commit module (#50503).
Fixed an issue where Git check response was not delivered for validation CI Job even though user has added the comment for a Pull request in the remote repository (#53036).
06 November 2022
(ARM v22.1.32) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue with DX CI Job where user selected Do Not Include Skip Members but the respective mapper reports were not skipped (internal ticket).
Fixed an issue where the Deployment module page was loading very slowly and then thrwing an error:
Page Unresponsive
(#53675).Fixed the following issues in CI and Reports modules (internal ticket):
Build With NULL ERROR (issue exists both with Proxy and without Proxy)
SF Org Code coverage Execution is failing (issue exists both with Proxy and without Proxy)
Jenkins Build is updated with FAILED status even after it is successfully completed (issue exists only without Proxy)
Checkmarx text is not displaying the Proxy Configuration note (Only With Proxy)
Fixed an issue with QA Environments where user was unable to create and delete the SFDX module because of the Apache config CACHE settings (internal ticket).
Fixed an issue with the Deployment module where user initiated a Deployment without selecting the Do not Include Skip Members option, but this option was auto-enabled and skipped the member at the time of deployment (#53747).
Fixed an issue with Modularization where user creating a module and selected the Ignore installed components check box but the installed components were not ignored causing the deployment to fail (#53703).
Fixed an issue with AccelQ Test Automation where test case fails but the error details pop-up is not showing the details of the error that caused the failure (#54224).
Fixed an issue where user is setting up the Apex PMD rules as Priority 1 & Priority 2 in the CI Job but the SCA Report is showing the Priority 3, P4 & P5 which wasn't selected (#54017).
Fixed an issue where the Git check response was not delivered for a validation CI Job (#53036).
Fixed an issue where the Deleted Report metadata components were not found in the EZ-Commit (#53119).
Fixed an issue where user was trying to perform a Quick Merge but was getting an Undefined error for all labels (internal ticket).
30 October 2022
(ARM v22.1.31) This is a maintenance release. The following items were fixed and/or added:
Fixed a UI bug on the CI Jobs page for Install an Unlocked or Managed Package from a Version Control Branch type where old Dev Hubdropdown list was displayed in the Deploy section (internal ticket).
Fixed an issue with AccelQ where running a test execution was successful even before the jobs were completed in AccelQ, but the status was always showing as Not Run instead of Success or Failure even if the jobs have been successfully completed (#50181).
Fixed a Page Unresponsive issue while creating a new Release Label by adding a feature to list limited results on each page (#48563).
Fixed an issue where user created a Release Label, performed a Merge operation, committed changes to the target branch, and created two revisions in the Github branch. But ARM was throwing an error while applying merge stage and only on the revision generated (#51364).
Fixed an issue where EZ-Commit initiation was stuck with the error:
Unable to fetch Salesforce Org users. Reason: Invalid login: invalid user name or password or security token or api version or user locked out
(#52550).Fixed an issue where Page Size value on the Edit Release Label screen is defaulting to the previous value instead of the set value (internal ticket).
Fixed a UI bug where OK Button in Automation is not visible in the Create Release Label pop-up when opened in 100% zoom (internal ticket).
23 October 2022
(ARM v22.1.30) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where CI Job was successful but was including components from GIT revisions from old deleted branches (#46983).
Fixed an issue where user was performing a production deployment using CI job for an object, but it failed with the following error:
Cannot set sharingModel to ControlledByParent on a CustomObject without a MasterDetail relationship field
(#48626).Fixed an issue where CI Job was getting an exception, Build status was showing as successful, but Scratch Org not getting created (#50702).
Fixed an issue where Managed Package was picking the wrong ancestor by adding a feature to manually select the preferred ancestor while creating a package version (#48311).
Fixed an issue where user was adding URLs to the Proxy Configuration Settings but the URL List was not reflecting the same (internal ticket).
Fixed an issue where Custom Template Creation failed and the Logs did not record the reason for failure (#52147).
Fixed an issue where the Created By value was not visible in Dataloader, Dataloader Pro DL Config, and the TestEnv History page (internal ticket).
Fixed an issue where the Comment Box was not accepting more than 100 characters while rejecting a Commit, but was working as expected while approving a commit (#51384).
Fixed an issue where user set Commit validation Criteria to Auto reject after 7 days but the older Pre-validation commits are not auto rejected after 7 days (#49874).
Fixed an issue where user cannot add Skip members manually and it is failing due to special characters being included (#53139).
16 October 2022
(ARM v22.1.29) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where skipped members were present in many components but only Report Metadata was failing during Deployment (#51040).
Fixed an issue where CI Job was getting stuck in In Progress status but the log showed that the deployment was successful (#51140).
Fixed an issue where GitHub login credentials were not working when user triggered a CI Job for the second time (#50630).
Fixed an issue where CI Job has failed in the Salesforce org, but still stuck in In Progress status in ARM (#50435).
Fixed an issue where user raised a Pull request on a branch and was getting a webhook response, but CI Job build was not triggered (#51592).
Fixed a UI bug where Add to dashboard button was unavailable for widgets (#52333).
Fixed an issue where a new database file is created and overwritten with an existing database file whenever the server was restarted (internal ticket).
Fixed an issue where user was trying to resolve conflicts on Merge Request Labels created more than 7 days ago, but application was throwing an error:
undefined
(internal ticket).Fixed an issue where Custom Email Template was not working for Email notifications (#47484).
Fixed an issue where user was testing SSH Connection but the application was throwing an error:
invalid privateKey
(#50940).Fixed an issue with nCino where UI Log was not generated for failed CI Jobs (#50442).
Fixed an issue where New EZ-Merge was throwing an error (#46754).
Fixed an issue where Audit Logs were not generating via Postman Services (#50221).
Fixed an issue where Commits were getting stuck and throwing the following error:
No credential have been found with Name:git
, but was not reflecting in the UI log (#51713).Fixed an issue with Workspace Settings where unused workspaces were not being cleared despite selecting Clear all workspaces which are not used in last 7 days (#50164).
Fixed an issue where user was performing a Prevalidation EZ-Commit and found that some Layout Assignments were deleted though those layouts were not part of the commit (#50945).
Fixed an issue with nCino where migration was failing due to errors with Standard Screen and UI Templates (#50432).
09 October 2022
(ARM v22.1.28) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue with nCino where user was getting errors with Standard Screen and UI Templates (#50432).
Fixed an issue where user noticed discrepancy in the Conflict Resolution Log (#47559).
02 October 2022
(ARM v22.1.27) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where email notification wasn't sent for some of the CI Jobs (#48028).
Fixed an issue where the Custom label and remote site setting URLs were not getting updated by ARM through Environmental Provisioning (#49612).
Fixed an issue with Vlocity where selecting one component from a GIT repository was causing all the components from the category to get selected (#49806).
Fixed an issue with ALM Mgmt. where item status was not retrieved properly for Merge Request, but was working as expected for EZ-Merge (#50628).
Fixed a UI bug where Release Labels were showing duplicate Time Stamps (#51205).
Fixed an issue where old Commit Labels were not getting auto-rejected after 7 days as the user had configured under Commit Validation Criteria (#49874).
Fixed an issue where user was getting an error pop-up on the Permissions and the SF ORG MGMNT pages, and the SF org and VC repo mappings were lost in the profile section of a role (#49108).
26 September 2022
(ARM v22.1.26) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where Provar test job was throwing an error while in queue (#49797).
Fixed an issue where scheduled auto-sync of external commits was not working (internal ticket).
Fixed an issue with the New EZ-Commit screen where ALM Types are changing to old ALM type names after resaving details on the ALM Management screen (internal ticket).
Fixed an issue with Pre-validation merge where the Object file content was empty in the CodeScan Analysis SCA report (internal ticket).
Fixed an issue with EZ-Merge where Diff was not being generated even though there were file changes between the source branch and the destination branch (#50323).
Fixed a UI bug in DataLoader where user was switching from Graphical View to Grid View but Graphical View options were still being displayed (#50431).
Fixed an issue with nCino where the Insert/Update With Null Values option was not getting updated for CI jobs (#50259).
Fixed an issue where users were unable to re-authenticate the Salesforce Org after refreshing their personal sandboxes (#48533).
Fixed an issue where Environment Provisioning Template was not functioning as expected for Custom Labels containing URL (#47892).
Fixed an issue with EZ-Commit where user was trying to deploy Permission Sets and Profiles together, and the pre-validation process was stuck in In-Progress status (#49340).
Fixed an issue where old Commit Labels were not getting auto-rejected as configured (#49874).
19 September 2022
(ARM v22.1.25) This is a maintenance release. The following items were fixed and/or added:
Fixed multiple issues with CodeScan<>ARM Integration (internal ticket).
Fixed an issue where CI Jobs and Deployments were both failing for Reports and Dashboards because the folder could not be found (internal ticket).
Fixed an issue with New Commit screen where the Select All checkbox was getting unselected when navigating from the DELETED tab to the ADDED/MODIFIED METADATA COMPONENTS tab and back to the DELETED tab (internal ticket).
Fixed an issue with Version Control Prevalidation Commit where for the selected Custom Metadata and Permission Set, Diff was being generated as expected but the Deployment was failing (internal ticket).
Fixed an issue with Version Control Prevalidation Merge where SCA report was empty, and throwing the following error in the console:
Uncaught TypeError: Cannot read properties of undefined (reading 'length')
(internal ticket).Fixed an issue where user was unable to reset the AutoRABIT password, and was getting an error:
getAttribute: Session already invalidated
(#50145).Fixed an issue where the user tried to merge to the Dev branch but the CI Job failed and was throwing a Duplicate error (#49661).
Fixed an issue where user was trying to install Unlocked Package via CI Job but it was failing and throwing the following error:
ERROR 178928269770891:275 - For input string: "0-2" java.lang.NumberFormatException: For input string: "0-2"
(#50093).Enhanced Vlocity loggers for Branching Baseline by displaying to the user Status Count of Remaining, Success, Error and Ignored (internal ticket).
Fixed an issue where Test Connection was failing on the Version Control Summary page under the Admin module (#49299).
Fixed an issue with Prevalidation Merge by increasing the SCA Response timeout from 50 minutes to 5 hours (#48613).
Fixed an issue where merging Master Branch with the Production branch was throwing the following error:
No merge head specified
(#46594).Fixed a bug where New A-Z Merge was throwing an error (#46754).
Fixed an issue with Autorabit Commit Label related to Permission Sets Deployment (#48709).
11 September 2022
(ARM v22.1.24) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where user was selecting a single package to import, but all available package versions were being imported (#49426).
Fixed an issue with Profile Manager where user was comparing a profile but the deployment was not starting (#48620).
Fixed an issue where deploying components with profiles was not working as expected and throws the following error:
Duplicate layoutAssignment:PersonAccount (PersonAccount.Person_Prospect)
(#49021).Fixed an issue where custom metadata records were not being selected during deployment (#49167).
Fixed an issue in Version Control Commit Labels history where Created By and Created Date values were exchanged (internal ticket).
Fixed an issue where user was getting an error while trying to deploy Vlocity Metadata using CI Jobs (#47568).
Fixed an issue where Branching Baseline was not retrieving Workflow Metadata types (#49403).
Fixed an issue where Release Label failed to load revisions from a particular branch and the browser was hanging and throwing an Out of memory error (#48563).
Fixed an issue where EZ-Commit was not getting auto-rejected when CodeScan analysis failed, even though user select the option to run Static Code Analysis (#47155).
Fixed an issue where merge was failing at the Validate Deploy step even before selecting the org to validate (#49724).
Fixed an issue where Layout was being removed from the Diff while deploying Profile changes with related Layouts and RecordTypes (#48268).
Fixed multiple issues with CodeScan<>ARM Integration (#49605).
04 September 2022
(ARM v22.1.23) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where the CI job was not working as expected and throws the following error:
java.lang.NullPointerException: null
(#48706).Fixed an issue where few fields were not being analyzed in CodeScan SFDX. User was selecting Custom Fields, Apex Classes, and Record Types in E-Z Commit, but Static Code Analysis was only Apex Classes (#48547).
Fixed an issue where dashboards and reports were changing to Destructive and getting deleted (#48119).
Fixed an issue where discrepancies for Document, Assignment Rule and AutoResponseRule metadata types content was observed in package.xml for SFDX and non-SFDX CI Jobs (#47017).
Fixed an issue where nCino CI Jobs via RBC were failing during parallel deployment. Instead of falling in queue, the first job was failing while the other succeeded, and the user had to retrigger the failed job (#47335).
Fixed an issue where creating multiple deployment jobs from the same source org to the same destination org for different templates, the jobs were failing with Null Pointer Exception error (internal ticket).
Fixed an issue with DX Pre-validation merge where Destructive Deployment for custom labels failed without any errors (internal ticket).
28 August 2022
(ARM v22.1.22) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where Unpackaged Packages Directory folder was being created in the Deployment Promotion zip package when deploying Static Resource Metadata type using Single revision DX Deployment (internal ticket).
Fixed an issue where after upgrading the AR instance, deployment jobs kept removing the custom metadata access on the Permission Sets (#48296).
Fixed an issue where Org difference jobs were running for more than 24 hours (#48324).
Fixed an issue where Environment provisioning template was not working when trying to update custom label values that contain URL, and the incorrect value was being updated in the org (#47892).
Fixed an issue where choosing the Select Manually option while doing a commit was resulting in a blank screen for the Deleted tab (internal ticket).
Fixed an issue where while doing Prevalidation commit in AR, Commit Only Permissionsets For The Selected Metadata functionality was not working properly for both DX and Non-DX cases (internal ticket).
Fixed an issue in Dataloader where an Undefined Error was displayed when user was trying to create and save the Screens Template (internal ticket).
Fixed an issue where user was trying to validate the commit using single revision, but was getting an Empty Package error even though there were changed files in the commit (#47530).
Fixed an issue where DataLoader Pro jobs were failing with an error duplicate value found: SetupOwnerId duplicates value on record with id for the custom setting Multichannel_Settings_vod__c, even though there is no field mapped with name SetupOwnerId (#48230).
Fixed an issue where the search functionality was not working in Dataloader Configuration as well as Dataloader Test Environment Setup (internal ticket).
Fixed an issue where EZ Commit Logs and Change Labels were not displaying for some of the commit labels (#45364).
Fixed an issue where the user was not able to see the deployment report because the build was failing when only custom fields were being selected without the related object (#45663).
Fixed an issue where merge request was being auto rejected if the selected approver was no longer with AR (#48084).
Fixed a bug where user had enabled Squash and Merge while performing a new merge, but the Squash and Merge option was not displayed after the Merge Request was approved (#48246).
Fixed an issue in CI Jobs deployments where Bulk API option for Attachments was throwing an error (internal ticket).
Fixed an issue where nCino CI Jobs were failing the first time and completing the second time successfully (#46545).
21 August 2022
(ARM v22.1.21) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where the CI job build was getting stuck in In-progress status (#47934).
Fixed an issue where RunSpecifiedTest level execution was failing with Test classes dependency errors (#47666).
Fixed an issue where DX CI Job build failed if document metaxml change commit revision includes in the build [Including Email templates and Static Resources types] (internal ticket).
Fixed an issue where entire branch merge was failing with multiple common ancestor errors (#47334).
Enhanced the Dataloader history screen (internal ticket):
Column mover added to table column alignment for text view.
Moved Last Run details to the Date/Time column.
Fixed an issue where Standard fields are not retreiving when included in package.xml, and retrieving through E-Z Commit (Package Manifest) option (#47961).
Fixed an issue for the nCino CI Jobs were failing due to default selection of AutorabitExtId__c in Mappings (internal ticket).
Fixed an issue for the nCino Deployments where even if LookupKey is available, by default Name is selected in External ID Mapping (internal ticket).
Fixed an issue for the nCino CI Jobs where Attachments were failing due to External Mappings not being set to the NAME field (internal ticket).
Added the feature to dynamically handle the respective nCino Prefix rather than depending on the JSON file to identify the External Id field
14 August 2022
(ARM v22.1.20) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue with the Profile Manager where the user were unable to select the default app permission during the profile deployment (#47462).
Fixed an issue where the merge revisions were missing from the CI jobs (#46862).
Fixed an issue where the users were unable to commit Vlocity card from one org to another org in ARM (#44938).
Fixed an issue where for both CI Jobs and Deloyments (Non-DX and DX), the deployment was getting failed with the below error although the Ignore missing visibility settings is checked:
permissionset error--- Error in field: customPermission not found
(internal ticket).Fixed an UI bug where while performing test connection for any successful Salesforce org registered, the messasge is displayed as "Success" instead of "Testconnection was successful" (internal ticket).
Fixed an issue where the ALM integration was not working when the files are pushed with special characters in their name (#47414).
Fixed an issue where the commit labels was getting auto-rejected while committing Profile FLS (#46844).
07 August 2022
(ARM v22.1.19) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where the package URL was not visible for the SFDX modules successfully configured in ARM (internal ticket).
Fixed an issue where our internal team members got the undefined error while creating a new scratch org and selecting the module (internal ticket).
Fixed an issue where after triggering the CI job, the File Changes and Check-ins results mismatched (#40119).
Fixed an issue where the package created to deploy ExperienceBundle misses some of the folder and metadata files contained in it (#46692).
Fixed the below deployment-related issues:
Fixed an issue where the deployment failed to initiate when search and substitute rules are selected (#47802).
Fixed an issue where the status log .csv files are inconsistent for deployment via CI jobs (internal ticket).
Fixed an issue where the users were unable to process the migration of RBC object (nForce__Views__c) using the nCino CI jobs, feature template migration, or the Dataloader Pro jobs (#47098).
Fixed an issue where while deploying a nCino-User Interface template, only partial records are deployed and no deployment logs are generated (#47494).
Fixed an issue where the users, while performing an EZ-Commit by enabling the run SCA option, the CodeScan analysis is getting failed, but EZ-Commit is not getting auto-rejected (#47155).
31 July 2022
(ARM v22.1.18) This is a maintenance release. The following items were fixed and/or added:
Upgraded the Spring and AWS libraries on ARM for addressing the Spring vulnerability (#46970).
Fixed an issue where the users were unable to login to ARM via SSO (internal ticket).
Fixed an issue where the ARM is not able to fetch any component using the release label (#46662).
Fixed an issue where the baselining of branches has wiped out the records types for many records, and the users were forced to do manual changes to the Record types (#42719).
Fixed an issue where the ARM allows to associate only one branch to one package, and not able to build beta package versions from various branches. This is now fixed (#46841).
Fixed an issue where the CI job, while deploying manage packages, is installing all the manage packages instead of installing a single package (#46832).
Fixed an issue where the links on the CI Job log screen are redirected to the user's login page instead of redirecting to user's Salesforce org screen (#47151).
Salesforce API version 55 (Beta support) is upgraded. The label is modified throughout ARM application to Salesforce API version 55.0 (#47404).
Duplicate classes from the ARM repo has been removed (internal ticket).
Fixed an issue with the Profile Manager where the user were unable to select the default app permission during the profile deployment (#47462).
Fixed an issue where the merge revisions were missing from the CI jobs (#46862).
Fixed an issue where the users were unable to commit Vlocity card from one org to another org in ARM (#44938).
Fixed an issue where for both CI Jobs and Deloyments (Non-DX and DX), the deployment was getting failed with the below error although the Ignore missing visibility settings is checked:
permissionset error--- Error in field: customPermission not found
(internal ticket).Fixed an UI bug where while performing test connection for any successful Salesforce org registered, the messasge is displayed as "Success" instead of "Testconnection was successful" (internal ticket).
Fixed an issue where the ALM integration was not working when the files are pushedwith special characters in their name (#47414).
Fixed an issue where the commit labels was getting auto-rejected while committing Profile FLS (#46844).
Fixed an issue where the merge was getting failed with the following error:
Fetch operation is failed due to some runtime exceptions from Git
(#46773).Fixed an issue where the username and passwords fields were not editable for users registered in ARM with basic authentication (#47099).
24 July 2022
(ARM v22.1.17) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where the Rollback settings were not getting saved in the My Account page (internal ticket).
Fixed a bug where the users could not edit/modify their CI jobs when the build was in progress (#43538).
Fixed an issue with the permissionsets where instead of delta changes, the Permissionset retrieving entire file from the branch and causing dependency issues (#46846).
Fixed an UI bug where the ARM application displays unwanted scrollbar when "Exclude Installed (Managed) components" is selected in the My Account page (internal ticket).
Enhanced the ARM workspace feature to automatically unlock the workspace after sufficient time to run the workspace operations.
Added the feature to set Limit 0 option for the Dataloader Pro jobs. This limit will allow users to skip migrating child or Ancestors objects.
Fixed an issue where while editing an existing nCino CI Job, the version control is not automatically choosing the previous repository set. This is causing the selected nCino Templates to reset (#46952).
Fixed an issue where the ALM labels were missing from the ALM Label lists page (#44410).
Fixed an issue where the settings related with user permissions were erased (#46472).
Fixed an issue where the users when performed EZ-Commit using a package manifest file, doesn't include managed components that are in the package.xml file (#47083).
17 July 2022
(ARM v22.1.16) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where the Execute Anonymous Apex metadata is not working as expected when configured as Environment Provisioning template (#46817).
Fixed a bug where our internal team were able to use the perform the prevalidation commit and direct commit without giving the prevalidation commit label name and without commit comment, which are mandatory fields (internal ticket).
Fixed an issue where the ALM workitems are not retrieved in CI job through merge (internal ticket).
Fixed a bug where our internal team were able to save the Install an Unlocked or Managed Package from a Version Control Branch CI job even though Installation key were not uploaded which is a mandatory field (internal ticket).
[Enhancement] Added the Salesforce versions information in the logs for all Dataloader related jobs activities.
[Enhancement] Added the ability to delete a commit before it is pushed to your remote repository so that you have a choice to redo incorrect commits/ merges.
Fixed an issue where the Delete Commit button was not seen after approving an EZ-Commit label (internal ticket).
Fixed an issue where the toggle button for the dashboard metadata type in the commit label screen is not working as expected (internal ticket).
Fixed an issue for the nCino Feature Deployments where the users were getting audit field issue when trying to deploy with
Insert/Update with Null Values
option (internal ticket).Fixed an issue for the nCino CI jobs using Spreads Templates where the users were getting
NullPointerException
error when trying to deploy withInsert/Update with Null Values
option (internal ticket).
10 July 2022
(ARM v22.1.15) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where the users failed to enable the pull request support for their version control repositories (#46336).
Fixed an issue where the re-use previously validated commit label takes more time to load (#46171).
Fixed an issue where the constructive changes are picked in the CI build, although no constructive changes are in-between From and To revisions (internal ticket).
Fixed a bug marked deployment as failed, whereas the log report says successful (#46737).
Fixed an issue with the SFDX job, where for the Report metadata type, the rollback feature was working weirdly (internal ticket).
Fixed a bug where the users could not edit/modify their CI jobs when the build was in progress (#43538).
Fixed an issue where entering the package installation key in
Install an Unlocked or Managed Package from Version Control Branch
CI Job gets altered when manually entered or pasted (#46836).Fixed an issue where the user could not run the static code scan report on GitHub with APEX PMD Lint Scanner metadata type (#46781).
Fixed an issue with the CodeScan analysis report that failed when running from ARM (#44404).
Fixed an issue where the user could not fetch the latest CI job weekly reports (#42587).
Enhanced the Dataloader Pro, where the attachments are now supported (#41077).
Fixed a bug where editing the Dataloader job shows "Job Group" as null or empty (internal ticket).
Vlocity has been upgraded to v1.15.5.
Fixed an issue with the CI job where the version control using Salesforce with attachments was not picking the attachments during CI build (internal ticket).
Fixed an issue with the EZ-Merge, where merging the main branch to the dev branch failed with a
No merge head specified
error (#46594).Fixed an issue that throws
Schema as invalid
error while running the branching baseline operation (#46593).Fixed an issue where our internal team members could not create a new role from the Admin section (internal ticket).
Fixed a bug where the
Invalid Schema
error is seen for non-SFDX prevalidation merge (internal ticket).Fixed an EZ-Commit issue where additional permissions were removed from Profiles metadata type, which is not a part of the commit (#44543).
03 July 2022
(ARM v22.1.14) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where the deployment via CI job picked unnecessary components for deletion (#44204).
Fixed the issue where the user when trying to delete a component in Community metadata type, deletes the whole Community rather than its components (#43698).
Fixed an issue where DevHub registration in ARM was failing (#46208).
Fixed a bug where our internal team members were not able to view the Salesforce Org URLs in the My Profile section (internal ticket).
Fixed an issue where the deployment using Commit/Release Label was not working (#46419).
Fixed an issue where the Compact Layout were not getting deployed and throws undefined error(#46592).
Fixed an issue where the ALM statuses were not updated/rolled back post CI job rollback completion (#45945).
Fixed an issue where the destructive changes were not working as expected for the CI jobs (#46216).
Fixed an issue where the ARM failed to update the Audit fields when trying to run nCino feature deployment (#46356).
Fixed an issue where our internal team were not able to register their credentials on one of the ARM SAAS instances (#46315).
Fixed a bug where the deleted components were tagged as UC (UnChanged) instead of D (Deleted) in the EZ-Commit (#46087).
Fixed an issue where the metaXML file were not retrieved for the ContentAsset metadata type for the SFDX "Entire Branch" merge case (internal ticket).
Fixed an issue where the deployment validation were failing for the prevaildation merge with the error:
No source backed components present in the package
(internal ticket).Fixed an issue where the merge using single revision (baseline revision) receives the metadata schema error (#46570).
Fixed an issue where the merges were getting failed and throws the
Schema is invalid for the file
error (#45768).Fixed an issue where the exported users list contained inaccurate information (#44782).
26 June 2022
(ARM v22.1.13) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where the Spread Template in the nCino module was not working as expected (#45078).
Fixed an issue where the user was getting
"field integrity exception: unknown (CreatedByID(0051X00000BbMIR) is not in org"
for the records that were available in the destination org.Fixed the issue where the Disable Workflow template in the Environment Provisioning module was not working as expected (#46195).
Fixed an issue where the creation of a scratch org were getting failed. The fix has been deployed to in this weekly release (#46021).
Fixed an issue where the users were unable to use the release label for deployment (#45415).
Fixed an issue where the users were not able to register same DevHub with two different usernames (#46208).
Fixed an issue where the CI Job was picking the deleted components from GitHub branch although the Prepare Destructive Changes checkbox was not selected. This caused the deployment to fail (#42553).
Fixed an issue where the CI Job for backing up from org to the version control branch was failing with null pointer exception error (#45646).
Fixed an issue where the EZ-Commits, when included Profile, was not working as expected (#45902).
Fixed an issue where the commits were getting stuck at the delta stage (#45101).
Fixed an issue where the Git tags were being added to the queue but not being processed (internal ticket).
Fixed an isse where the delta was getting failed in the EZ-Commit flow (internal ticket).
Fixed an issue where the Dalaloader Pro job is failing with
Required field missing on "nCino_Screen__c" object
, however the user were able to view theScreen__c
object has a value in their source org (#45139).Fixed an issue where the user were not able to save the Dataloader Pro jobs and throws the
JAVA.NullPointerException
error (#46385).Fixed a bug where the users were not able to view the log reports after registering Tags via ARM (internal ticket).
Fixed an issue where the tags creation got failed when the tag name contains 'error' with custom API flow (internal ticket).
19 June 2022
(ARM v22.1.12) This is a maintenance release. The following items were fixed and/or added:
Fixed a minor bug where the child members checkboxes remained checked even when the parent metadata type was unchecked (internal ticket).
Fixed an issue where CI job build ToRevision number was mismatched in the CI Job Results and the CI Build Info page (#45580).
Fixed an issue where the request parameters were empty in the nCino Feature Commit History screen (#45855).
Fixed an issue where the users while accessing the commits older than 30 days, ARM throws
Request parameters are empty/null
error (internal ticket).Fixed an issue where the users when accessing the Commit History page throws
Invalid FilterExpression
error (internal ticket).Fixed an issue where the user were unable to fetch the latest CI job weekly reports (#42587).
Fixed an issue where the Diff report in the Merge Request was not working as expected (#45315).
Fixed an issue where the user ran the branching baseline operation by excluding the Managed package components, however, the Package.xml file still had all the managed package components listed in it (#45125).
Fixed an issue where the code coverage report was being generated at a different time than what was scheduled (#45703).
Fixed an issue where the exported users list contained inaccurate information (#44782).
Fixed an issue where the TAF execution were getting failed (internal ticket).
Fixed an issue where the From Revision was not visible when user access their CI job from CI Job History page (internal ticket).
Fixed an issue that caused Chrome to crash anytime a user attempted to view the functional test results for the task of running a Selenium Maven test. The functional test results screen enters a continuous cycle of requests, which crashes the browser (internal ticket).
Fixed an issue where the skip members feature of ARM was not working as expected (internal ticket).
Fixed an issue where the user while performing EZ-Commit with SonarQube code analysis was getting failed with
Failed to run the sonar-scanner: null
error (#46070).
12 June 2022
(ARM v22.1.11) This is a maintenance release. The following items were fixed and/or added:
Fixed the issue where the Dataloader Pro jobs was not working as expected (#43966).
Fixed an issue where the users while performing org to org migration of nCino record based configurations, all the related items are getting carried over except the notes and attachment of the Credit Memo from source to the destination environment (#40990)
Fixed an issue where the Jenkins builds were failing during the CI/CD process (internal ticket).
05 June 2022
(ARM v22.1.10) This is a maintenance release. The following items were fixed and/or added:
Fixed the issue for the SFDX jobs where the user permissions were picked up for the deployment even if the user opts for "Remove User Permissions" (#44027).
Fixed an issue where new tags gets automatically added for the sharing rules after the ARM 22.1 upgrade (#44032)
Fixed an issue where the SFDX CI job picked up extra content for workflow and custom labels (#44028).
Fixed an issue where the quick deployment functionality was not working as expected (#42521).
Fixed an issue where the users could not view the commits list to merge them into a release label (#43718).
29 May 2022
(ARM v22.1.9) This is a maintenance release. The following items were fixed and/or added:
Fixed the issue where the Dataloader Pro jobs was not working as expected (#43966).
Fixed an issue where the users while performing org to org migration of nCino record based configurations, all the related items are getting carried over except the notes and attachment of the Credit Memo from source to the destination environment (#40990)
Fixed an issue where the Jenkins builds were failing during the CI/CD process (internal ticket).
22 May 2022
(ARM v22.1.8) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where performing a validation merge on the Azure repository branch creates the merge label and an external commit label with the same name and the same revision number (#39287).
Fixed the issue where the DiscoveryAIModel metadata type was unsupported, which caused the CI jobs to fail (#42981).
Fixed an issue where the users were unable to fetch the standard fields from the custom objects (#43378)
Fixed an issue where the ARM user interface gets distorted when the zoom is 100% (#43735).
Fixed an issue where the ALM workflow was mismatched (#43775).
Fixed Spring4Shell vulnerability by upgrading the Spring Boot version to 2.6.6 for the AR Agent (#43584).
Fixed an issue where the "invalid session" error occurs when the user tries to delete and resave the cloned CI job.
Fixed an issue where the Conflict Resolution screen was not showing all the merge conflicts (#43663).
Fixed an issue where the CI job build status fails with "java.util.ConcurrentModificationException" error when running the nCino feature migration templates (#40752).
Fixed an issue with the Dataloader Pro job where the users, when trying to migrate the case object along with feed item & feed comment, the ARM application throws the "invalid cross reference id" error (#43703).
Fixed an issue where the merge process, after being sucessful, did not display the code coverage report (#42079).
15 May 2022
(ARM v22.1.7) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where performing a validation merge on the Azure repository branch creates the merge label and an external commit label with the same name and the same revision number (#39287).
Fixed the issue where the DiscoveryAIModel metadata type was unsupported, which caused the CI jobs to fail (#42981).
Fixed an issue where the users were unable to fetch the standard fields from the custom objects (#43378)
Fixed an issue where the ARM user interface gets distorted when the zoom is 100% (#43735).
Fixed an issue where the ALM workflow was mismatched (#43775).
08 May 2022
(ARM v22.1.6) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where performing a validation merge on the Azure repository branch creates the merge label and an external commit label with the same name and the same revision number (#39287).
Fixed the issue where the DiscoveryAIModel metadata type was unsupported, which caused the CI jobs to fail (#42981).
Fixed an issue where the users were unable to fetch the standard fields from the custom objects (#43378)
Fixed an issue where the ARM user interface gets distorted when the zoom is 100% (#43735).
Fixed an issue where the ALM workflow was mismatched (#43775).
Fixed Spring4Shell vulnerability by upgrading the Spring Boot version to 2.6.6 for the AR Agent (#43584).
Fixed an issue where the "invalid session" error occurs when the user tries to delete and resave the cloned CI job.
Fixed an issue where the Conflict Resolution screen was not showing all the merge conflicts (#43663).
Fixed an issue where the CI job build status fails with "java.util.ConcurrentModificationException" error when running the nCino feature migration templates (#40752).
Fixed an issue with the Dataloader Pro job where the users, when trying to migrate the case object along with feed item & feed comment, the ARM application throws the "invalid cross reference id" error (#43703).
Fixed an issue where the merge process, after being sucessful, did not display the code coverage report (#42079).
01 May 2022
(ARM v22.1.5) This is a maintenance release. The following items were fixed and/or added:
Fixed the issue for the SFDX jobs where the user permissions were picked up for the deployment even if the user opts for "Remove User Permissions" (#44027).
Fixed an issue where new tags gets automatically added for the sharing rules after the ARM 22.1 upgrade (#44032)
Fixed an issue where the SFDX CI job picked up extra content for workflow and custom labels (#44028).
Fixed an issue where the quick deployment functionality was not working as expected (#42521).
Fixed an issue where the users could not view the commits list to merge them into a release label (#43718).
Fixed a bug where selecting the "Deployment" icon after signing in to the ARM application caused the user to log off and on and return to the home page (#44040).
Fixed a bug where the check-ins display the wrong number of files changed during commit (#40119).
Fixed an issue where the users while accessing the help center from ARM application, receiving the ({"result":"failure","cause":"E105 - Request Delayed"}) error (#43579).
Fixed a bug where the commits was getting failed due to SCM (Software Configuration Management) authentication failure (#42276).
Fixed an issue where extra metadata members are picked up for the profile component during the EZ-Commit process (#41361).
24 April 2022
(ARM v22.1.4) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where performing a validation merge on the Azure repository branch creates the merge label and an external commit label with the same name and the same revision number (#39287).
Fixed the issue where the DiscoveryAIModel metadata type was unsupported, which caused the CI jobs to fail (#42981).
Fixed an issue where the users were unable to fetch the standard fields from the custom objects (#43378)
Fixed an issue where the ARM user interface gets distorted when the zoom is 100% (#43735).
Fixed an issue where the ALM workflow was mismatched (#43775).
Fixed Spring4Shell vulnerability by upgrading the Spring Boot version to 2.6.6 for the AR Agent (#43584).
Fixed an issue where the "invalid session" error occurs when the user tries to delete and resave the cloned CI job.
Fixed an issue where the Conflict Resolution screen was not showing all the merge conflicts (#43663).
Fixed an issue where the CI job build status fails with "java.util.ConcurrentModificationException" error when running the nCino feature migration templates (#40752).
Fixed an issue with the Dataloader Pro job where the users, when trying to migrate the case object along with feed item & feed comment, the ARM application throws the "invalid cross reference id" error (#43703).
Fixed an issue where the merge process, after being sucessful, did not display the code coverage report (#42079).
17 April 2022
(ARM v22.1.3) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue for the Chrome browser where the ApexPMD ruleset was not uploading incorrectly (under the Plugins section). For other browsers, it was working as expected (#42954).
Fixed an issue where the Salesforce-DX deployment and rollback mismatches (#35947)
Added the criteria to trigger the callout URL post-deployment. If you set it to success, the callout URL is activated if the salesforce deployment is successful (#38990).
Enabled feature flag settings to select between classic ARM and Salesforce CLI process to generate package manifest.
Fixed an issue where the commit validation is successful for an empty field, whereas the CI job fails (#43324).
Fixed an issue where the deleted metadata components were showing under the "File Changes" tab but did not appear under the "Destructive Changes" column while carrying out a manual deployment (#41670).
Fixed Dataloader Pro job issue where the job is completed successfully without loading all ancestors/master objects data to the destination environment (#43276).
Fixed the below nCino issues:
Unable to proceed with feature deployment using an existing community feature migration template due to the following error: "No External Id field exist in source org." This is now fixed and working as expected (#43263).
Non-template records were being picked up during nCino deployment.
Non-template records are fetched in the dataset.
Spread Statement Record failing with the error “Missing Statement Types.” This is now fixed.
10 April 2022
(ARM v22.1.2) This is a maintenance release. The following items were fixed and/or added:
Fixed the issue where the SFDX deployment is getting failed even though the user uploaded the correct file.
Fixed a bug where the static code analysis (SCA) status shows as in progress for a failed execution.
Fixed an issue where deleting a custom field was affecting other custom objects where the globalpicklistvalue is shared by multiple objects (#42782).
Fixed a bug where the users were not able to view specific values under the standard value sets in the New EZ-Commit screen (#41773).
Fixed a bug where the New EZ-Commit > Deleted Component tab throws a null error on expanding the metadata types.
Fixed a bug where the deploying records via record based configurations (RBC) was throwing error: "No external Id field exists in the source org" (#43263).
Fixed an issue where creating a new nCino feature migration template takes longer than expected (#41855).
Addressed out of memory (OOM) and other performance issues in this weekly release.
03 April 2022
(ARM v22.1.1) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where the skip members feature was not working for the Version Control, Deployments, and CI Job module (#41531).
Fixed an issue where the users were receiving layout permissions errors when using Prevalidation Commit.
The SCA option where not working when users use the EZ commit/ Merge operation. The issue has now been fixed (#39288).
Fixed an issue where the users were unable to generate the deployment report and received validations errors for EZ-Merge operation (#41639).
Fixed an issue where the users were unable to update any changes in the permission section.
Fixed an issue where the non-licensed users were receiving the deployment email failure notification for the unsuccessful deployment (#41705).
Fixed an issue where the users were unable to use the nCino feature after the ARM was upgraded to v21.6 (#41108).
27 March 2022
(ARM v22.1.0) This is a maintenance release. The following items were fixed and/or added:
Fixed an issue where the users were unable to switch the tab from the Test Coverage to the Class Coverage in the Apex test results page (#41455).
Fixed an issue where the users were unable to save Salesforce settings in the My Account screen (#41329).
Fixed an issue where the users were not able to save the exclude metadata types in the My Account page (#41529).
Fixed an issue where the users having difficulty with the datamigration.properties file while creating a new instance (#41510).
Last updated
Was this helpful?