New Features and Enhancements
Terminology Adjustments
Now that we offer metadata deployment, we’ve refined some terminology for more clarity. In short, configuration data = reference data + metadata.
- Configuration data – Configuration data for low-code apps is the reference data and metadata you create during app configuration to define your system.
- Reference data – Reference data is a type of configuration data you create during app configuration that is stored as record data within the app’s objects.
- Metadata – Metadata is a type of configuration data you create during app configuration that influences information architecture and look and feel of your environment.
Also, these terms describe the current state of our version control development:
- Org-to-org deployment – Org-to-org deployment means to update data in a destination org with data from a source org directly, not including handling deletes, using a deployment plan or data sets. Data does not pass through or automatically get captured by the VCS, but you can manually capture snapshots of the data for versioning or backup.
- Version-control deployment – Version-control deployment means to update data in a Salesforce org with data from the VCS branch associated with the org, including handling deletes, without the need for a deployment plan or data sets.
Refer to the full glossary for definitions of all Prodly terms.
AppOps Release Tab
The AppOps Release tab is now your starting point for all things AppOps Release for both org-to-org deployment and version control. Beginning with this release, Prodly’s development includes a shift from “data-set-centric” deployment to “org-centric” deployment. Rather than focus on data sets and then the source and destination orgs for your deployments, with the new approach you add your orgs to the management board and then control deployment from there.
While the legacy deployment center remains available, Prodly strongly recommends adopting the new org-centric deployment approach for these reasons:
- We’ve made a significant behind-the-scenes backend improvement to track record IDs between orgs in a more robust, global way.
- Metadata deployment is available only via the new guided deployment.
- Data backup and rollback for org-to-org deployment is available only from the management board.
- Version-control deployment is available only from the management board.
- Prodly’s roadmap shows all future enhancements evolving our products into a single change management system with all deployment controlled from the AppOps Release tab.
Management Board
The management board now works independent of, as well as in conjunction with, your version control system (VCS). Organize and manage your orgs from a single place, whether you are doing org-to-org deployment, version-control deployment, or both. Refer to Management Board for details.
The management board now provides the ability to unmanage an org. Refer to Unmanaging an Org for details.
Metadata Deployment
AppOps Release now deploys metadata via our new guided deployment feature! We’ve had a lot of requests to support metadata deployment over the years and we have now responded with a unique, intuitive interface that is certain to ease the pain you’ve experienced using change sets.
Not all types are supported in this first release, so refer to Deployable Salesforce Metadata Types for details.
Guided Deployment
The new guided deployment feature improves on the legacy deployment center user interface by presenting more options is a very user-friendly accordion-style wizard.
Choose your source and destination orgs, data set or deployment plan, and metadata, then deploy with ease. Refer to Guided Deployment for details.
By default, the Deploy buttons in the data set editor and the deployment plans page point to the legacy deployment center to maintain backwards compatibility. Prodly strongly recommends configuring the buttons to use the new guided deployment feature, so that you can deploy both data and metadata with a single click.
To match the functionality of the legacy deployment center, you can now deploy to up to five destination orgs at once via guided deployment. Refer to Selecting the Source and Destination for details.
Deployment History
After clicking Deploy in the Confirm Deployment section of Guided Deployment, the new Deployment History page shows the status of the current deployment and of all past deployments. You can drill into the familiar deployment results views, which now include metadata deployment results.
Refer to Deployment History for details.
Version Control
You can now use your version control system (VCS) to capture snapshots of your reference data after org-to-org deployments for versioning or backup. Refer to Org-to-Org Deployment and the VCS for details.
And for the scenario where you always deploy all records in a specific set of objects (that is, you do not need the query filter to filter records), you can now track and deploy your data without the need for data sets or deployment plans! Refer to Version-Control Deployment for details.
You also now can change the list of objects you are managing under version control. Add and remove objects from the list at any time. Refer to Editing the Managed Objects List for details.
Azure Cloud Integration
AppOps Release now supports integration with Microsoft Azure Cloud. So you can now integrate AppOps Release with the GitHub, Atlassian Bitbucket, and Microsoft Azure version control system (VCS) frameworks. Upgrade users must perform these configuration steps.
View Encrypted Data
We’ve eliminated the need to set the View Encrypted Data system permission flag.
Usability Improvements
- The most significant usability improvement is the combining of the apps and the central focus of the product under the AppOps Release tab.
- Controlling both org-to-org deployment and version control deployment from the management board is another significant improvement.
- We’ve done many little user interface tweaks to the management board and elsewhere for better usability.
- We’ve increased these governor limits:
- Maximum events per event type per event scope – from 10 to 100.
- Maximum data sets per deployment plan step – from 15 to 100.
- Maximum data sets per deployment plan – from 30 to 1000.
Resolved Issues
This table lists resolved issues in Prodly AppOps Spring ‘21 major and minor releases.
| ID | Description | Release Date |
|---|---|---|
| AP-5087 | Deployment mysteriously failing. In certain cases, AppOps Release was submitting an empty CSV file to upload as a bulk data job, causing deployment to fail. | August 5, 2021 |
| AP-5086 | Data not deploying correctly. On rare occasions, certain fields and values were getting transposed on insert. | August 5, 2021 |
| AP-4859 | AppOps Release and AppOps Test tabs don’t display contents. For software installed in a sandbox created off a production org, tab contents weren’t displaying due to a failing license check. | June 29, 2021 |
| AP-4810 | DX plugin needs access token. When a connection has no refresh token, the DX plugin now uses the access token. | June 15, 2021 |
| AP-4797 | Modified Apex class failing metadata compare. When users updated information in just the body of the class, the AppOps Release metadata comparison function wasn’t recognizing the changes. | June 15, 2021 |
| AP-4785 | 500 – Internal Server Error When the number of deployment orgs for a Prodly account was exactly divisible by the batch size, AppOps Release was attempting to process a batch of size 0, causing the error. | June 15, 2021 |
| AP-4653 | Unchanged lookup fields show as changed in metadata compare. AppOps Release was interpreting metadata lookup fields with filters in Salesforce as changed metadata, even when the filters where the same in the source and destination orgs. | June 8, 2021 |
| AP-4565 | Some records are being duplicated. Deployment was creating duplicates when records were previously deployed using a separate installation of the Prodly AppOps managed package. | June 1, 2021 |
| AP-4564 | Log messages are sometimes incomplete. We’ve once again beefed up our internal logging to give our customer success team more information to solve deployment issues that arise. | June 1, 2021 |
| AP-4560 | Modified custom field does not appear in metadata compare. Under certain circumstances, the metadata compare was not recognizing recently-modified custom fields. | June 1, 2021 |
| AP-4539 | Metadata components incorrectly shown as changed. Under certain circumstances, the metadata compare was erroneously listing some components as changed even though the values matched. | May 25, 2021 |
| AP-4533 | Endless spinner appears on control org card when no control org connection. When accessing the management board before ever creating a control org connection record, AppOps Release was erroneously displaying a spinner on the control org card. | May 25, 2021 |
| AP-4529 | “Access unavailable from this org” page shows up unexpectedly. When there are no managed org cards, we now display the management board instead of the unexpected “no access” page. | May 25, 2021 |
| AP-4505 | VCS setup wizard sometimes appears when clicking the Management Board page. An authorization check that was required back when we first designed the management board, but is no longer needed, has been removed. | May 25, 2021 |
| AP-4503 | Guided Deployment page resets after navigating away. When you click another tab or page and then return to the Guided Deployment page, the information on the page is now retained. | May 25, 2021 |
| AP-4481 | Concurrent deployments sometimes fail. When selecting more than one destination org in guided deployment, deployments were failing when the deployment was the very first time any data was being deployed to a newly managed org. | May 25, 2021 |
| AP-4466 | Metadata comparison failing with workspace error. We’ve added a check that prohibits starting a new metadata compare on orgs with a metadata deployment currently in progress. | May 25, 2021 |
| AP-4462 | Add custom setting to exclude metadata types. For orgs with a huge amount of metadata, a new custom setting (accessible only to Prodly support) now provides a way to reduce the amount of metadata retrieved for the org comparison. | May 25, 2021 |
| AP-4461 | Add personal access token option to all VCS options. During initial VCS integration, you can now specify a personal access token for each VCS integration that supports them. | May 25, 2021 |
| AP-4459 | Not all repositories are retrieved during VCS setup. We now retrieve all the repositories (instead of just the first 100) and have added a search box to filter the results for easier selection. | May 25, 2021 |
| AP-4458 | Improve order of initial checks. We’ve resequenced the initial validity checks (valid license, valid account, control org, etc) when displays the AppOps Release and AppOps Test tabs to present any errors in an order that better diagnoses the problem. | May 25, 2021 |
| AP-4456 | Null pointer during deployment. We’ve added a check to ignore the extra batch with no records that Salesforce occasionally returns during deployment. | May 25, 2021 |
| AP-4445 | Improve metadata retrieval for workflows. We’ve improved workflow retrieval time by first querying objects for workflows. | May 25, 2021 |
| AP-3485 | Clicking outside of the VCS setup dialog box should not hide it. The VCS setup dialog box now remains visible when clicking elsewhere in the tab window. | May 25, 2021 |
| AP-3222 | Endless spinner on the control org card. After deleting the control org connection record and recreating it under a different user, returning to the management board was erroneously displaying a spinner on the control org card. | May 25, 2021 |
| AP-4528 | Repository branch not populated for Azure. When selecting Azure as the VCS, the initial org data retrieval was not correctly populating the VCS repository branch. | May 18, 2021 |
| AP-4465 | Metadata compare is falsely showing some objects as deleted. The retrieval query was not returning all object names in all cases, resulting in false mismatches when comparing the source and destination metadata. | May 11, 2021 |
| AP-4440 | Not all records are deploying. A fix done in minor release 9 was inadvertently causing only the first 1000 records in a batch to deploy. | May 11, 2021 |
| AP-4429 | Batch result from Salesforce returns null. For pending records, the batch result was erroneously null. | May 4, 2021 |
| AP-4425 | Updates to custom fields are not recognized in metadata compare. After creating and deploying a new custom metadata field, changing the field then comparing the metadata a second time was not recognizing the changed field. | May 4, 2021 |
| AP-4424 | Managed orgs shown for wrong account. When two browser tabs were open, each logged into a different Prodly AppOps managed package installation, the guided deployment source and destination connection selections for both installations were being listed. | May 4, 2021 |
| AP-4408 | Reduce management board load on the system. When deployments are not running, we’ve lessened the frequency the management board polls for updates to reduce the overall load on the system. | May 4, 2021 |
| AP-4406 | Tabs don’t work in Safari. Privacy settings for the Safari web browser prevent the AppOps Release and AppOps Test tabs from displaying. Refer to Configuring the Safari Browser for details. | May 4, 2021 |
| AP-4397 | “Initialization in progress…” spinner spins forever with no error message. Occasionally when managing an org, the initialization steps were getting stuck in a queued state and never executing. | May 4, 2021 |
| AP-4395 | Deployment plan failed with 414 error. An issue with some relationship queries was causing deployment to fail. | May 4, 2021 |
| AP-4394 | Null pointer exception during deployment. Under certain circumstances, deployment was failing when the deployment request contained access tokens. | May 4, 2021 |
| AP-4370 | Add more logging for metadata compare and deploy. We’ve added more internal logging to help customer support help you resolve your issues faster. | May 4, 2021 |
| AP-4369 | Add error handling to metadata. As you can see below, we’ve added a lot of error checking as part of this minor release. | May 4, 2021 |
| AP-4073 | Null pointer error during deployment. An unexpected null pointer was causing the whole deployment to fail. We’ve changed it to just fail the record instead of the whole deployment. | May 4, 2021 |
| AP-3800 | Unexpected 502 error. We’ve added a proxy timeout check to catch some 502 errors before they happen. | May 4, 2021 |
| AP-3799 | Unexpected 502 and 503 errors. We’ve reduced the batch size of some of our processing functions to help minimize these errors. | May 4, 2021 |
| AP-3715 | Cannot manage org. After first deploying from the deployment center, subsequent attempts to manage the destination org were failing. | May 4, 2021 |
| AP-3540 | Improve the “500 – internal server error” message. This error can occur for several reasons, so we now provide a better description of each possible error. | May 4, 2021 |
| AP-3532 | Card name has disappeared. On the management board, cards with inactive connections were displaying without a name. | May 4, 2021 |
| AP-3489 | Manual refresh required to see new managed org. Under certain circumstances, initialization of a new managed org was successful, but the card failed to appear on the board. | May 4, 2021 |
| AP-3488 | Unexpected “no VCS authentication token” error. We’ve resolved an issue that was losing track of the connection to the VCS. | May 4, 2021 |
| AP-3469 | VCS setup wizard redirects to wrong AppOps Release page after Bitbucket authentication. For Bitbucket only, after the authentication step, the VCS setup wizard was not correctly advancing to the next step. | May 4, 2021 |
| AP-3467 | Clear out managed objects list when disconnecting repo. When disconnecting from the VCS and then reconnecting, all previously-managed objects were being included, not just the ones selected in setup. | May 4, 2021 |
| AP-3462 | New Managed Org fails without explanation when object missing from destination. When an object (for example Consumption Schedule) was missing from the org’s schema, new managed org was silently failing when attempting to deploy the branch data to the org. | May 4, 2021 |
| AP-3451 | Deployment History filter resets itself after a couple of seconds. An automatic screen refresh was ignoring the column filters. | May 4, 2021 |
| AP-3445 | Connection name has disappeared from control org card. The control org card name was coming up blank due to the way we were retrieving information differently for the control org. | May 4, 2021 |
| AP-3430 | Deployment history page loads twice. When a deployment is launched from guided deployment, the deployment history page no longer loads then reloads. | May 4, 2021 |
| AP-3423 | Make “Could not manage org” error message more informative. We’ve updated the message to “Cannot manage the selected org because it is already managed by another account.” | May 4, 2021 |
| AP-3236 | Several minor UI fixes. We’ve done some minor fixes and text phrasing adjustments here and there to align with the shift to “org-centric”. | May 4, 2021 |
| AP-3718 | Expired token is causing failures. We now make sure the control org access token is valid before attempting deployment. And if the token has expired, we refresh it. | April 19, 2021 |
| AP-3716 | Unexpected 401, 502, and 503 errors. Because many of these errors occur due to timing issues, we are now retrying the failed records a second time before failing the deployment. | April 19, 2021 |
| AP-3714 | Deployment fails with large number of content version records. Under certain circumstances, deployment was failing with as little as 200 content version records. | April 17, 2021 |
| AP-3554 | Deploying to the same object in the same org causes a 500 error. When the source and destination was the same org, transformations to the same object were failing. | April 15, 2021 |
| AP-3553 | Deploying to the same org with transformations causes a 406 error. When the source and destination was the same org, transformations to another object were failing. | April 15, 2021 |
| AP-3551 | Empty batch causes 500 error. Under certain circumstances, splitting batches was creating a batch of size 0, causing a null pointer error. | April 15, 2021 |
| AP-3550 | Duplicate record inserted after update fails. Under certain circumstances, AppOps Release was erroneously reinserting the record after attempting to update it failed. | April 15, 2021 |
| AP-3547 | DX plugin erroneously giving “Deployment failed due to Do Not Allow As Destination” error. We’ve corrected an issue where deployments to a scratch org using our DX plugin were failing because of unnecessarily checking for the “do not allow” flag. | April 14, 2021 |
| AP-3543 | Some records created through a Salesforce refresh are being duplicated. When deploying, AppOps Release was creating duplicates for records in the destination org that were never previously deployed through AppOps Release. | April 14, 2021 |
| AP-3535 | Existing destination org record values cause conflicts. Another corner case resulting in the 500 error had to do with unexpected record values in the destination org. | April 12, 2021 |
| AP-3531 | Prevent 500 error source record conflict. Under certain circumstances, AppOps Release was attempting to insert a new record rather than update the existing record. | April 12, 2021 |
| AP-3526 | Prevent 406 error from happening in the first place. The issue that was creating the need for earlier detection of deployment failures has itself now been resolved. | April 10, 2021 |
| AP-3525 | Null pointer error during deployment simulation. We’ve corrected an issue that was causing a null pointer error to occur during some deployment simulations. | April 8, 2021 |
| AP-3524 | Halt failed deployments sooner and display a better message. Under certain circumstances, deployment failure is now being detected sooner, reporting a more meaningful message. | April 8, 2021 |
| AP-2875 | Erroneously getting “Deployment failed due to Do Not Allow As Destination” error. We’ve corrected an issue where deployments were not proceeding because Do Not Allow As Destination was selected on the control org connection record. | April 7, 2021 |
| AP-3365 | Add VEID support for the attachments. We now support deploying the Attachment object using VEID. | April 6, 2021 |
| AP-3244 | Null pointer exception during data set deployment. We’ve resolved an issue with a null pointer specific to a customer’s use case. | April 6, 2021 |
| AP-3125 | Rename deployment result name field. To accommodate the addition of the Deployment Name, we’ve renamed the old Deployment Result Name field to Deployment Results Number. | April 6, 2021 |
| AP-3124 | Add deployment name to legacy deployment pages. With the ability now to specify a deployment name in guided deployment, we’ve also added deployment name to the legacy deployment pages. | April 6, 2021 |
| AP-3119 | Failed deployment needs error message to explain. We’ve added “Deployment failed because you have Do Not Allow As Destination selected for the destination org.” to the deployment results. | April 6, 2021 |
| AP-3093 | Show query filters on deployment results. We’ve added query filters as another related list on the deployment results. | April 6, 2021 |
| AP-3090 | Deployment result schema changes. To accommodate the new “org-centric” focus, metadata deployment, and query filtering through the API, we’ve connected these new objects to the Deployment Result object,: Deployment, Metadata Deployment Result, Metadata Component Deployment Result, and Query Filter. | April 6, 2021 |
| AP-2893 | Plan deployment throws null pointer exception. We’ve corrected the issue of a null pointer occurring while processing the fields in DeploymentDatasetUtilities. | April 6, 2021 |
| AP-2794 | Error deploying Content Version and Content Document objects. In org-to-org deployment, the Content Version and Content Document objects were not deploying due to an attempt to write to a non-updateable lookup field and the way Salesforce autogenerates documents. | April 6, 2021 |
| AP-2764 | Refreshed dev sandbox causes VEID record mismatch during org-to-org deployment. After deploying records from a dev sandbox to test to UAT to production, refreshing the dev sandbox then redeploying through the sequence again was causing duplicate records under certain other conditions. | April 6, 2021 |
| AP-2739 | Show the AppOps Release product on the Prodly Account tab. With the apps merging, the Prodly Account tab now lists the AppOps Release product, rather than just the version control/change management feature. | April 6, 2021 |
New Features and Enhancements
Terminology Adjustments
Now that we offer metadata deployment, we’ve refined some terminology for more clarity. In short, configuration data = reference data + metadata.
- Configuration data – Configuration data for low-code apps is the reference data and metadata you create during app configuration to define your system.
- Reference data – Reference data is a type of configuration data you create during app configuration that is stored as record data within the app’s objects.
- Metadata – Metadata is a type of configuration data you create during app configuration that influences information architecture and look and feel of your environment.
Also, these terms describe the current state of our version control development:
- Org-to-org deployment – Org-to-org deployment means to update data in a destination org with data from a source org directly, not including handling deletes, using a deployment plan or data sets. Data does not pass through or automatically get captured by the VCS, but you can manually capture snapshots of the data for versioning or backup.
- Version-control deployment – Version-control deployment means to update data in a Salesforce org with data from the VCS branch associated with the org, including handling deletes, without the need for a deployment plan or data sets.
Refer to the full glossary for definitions of all Prodly terms.
AppOps Release Tab
The AppOps Release tab is now your starting point for all things AppOps Release for both org-to-org deployment and version control. Beginning with this release, Prodly’s development includes a shift from “data-set-centric” deployment to “org-centric” deployment. Rather than focus on data sets and then the source and destination orgs for your deployments, with the new approach you add your orgs to the management board and then control deployment from there.
While the legacy deployment center remains available, Prodly strongly recommends adopting the new org-centric deployment approach for these reasons:
- We’ve made a significant behind-the-scenes backend improvement to track record IDs between orgs in a more robust, global way.
- Metadata deployment is available only via the new guided deployment.
- Data backup and rollback for org-to-org deployment is available only from the management board.
- Version-control deployment is available only from the management board.
- Prodly’s roadmap shows all future enhancements evolving our products into a single change management system with all deployment controlled from the AppOps Release tab.
Management Board
The management board now works independent of, as well as in conjunction with, your version control system (VCS). Organize and manage your orgs from a single place, whether you are doing org-to-org deployment, version-control deployment, or both. Refer to Management Board for details.
The management board now provides the ability to unmanage an org. Refer to Unmanaging an Org for details.
Metadata Deployment
AppOps Release now deploys metadata via our new guided deployment feature! We’ve had a lot of requests to support metadata deployment over the years and we have now responded with a unique, intuitive interface that is certain to ease the pain you’ve experienced using change sets.
Not all types are supported in this first release, so refer to Deployable Salesforce Metadata Types for details.
Guided Deployment
The new guided deployment feature improves on the legacy deployment center user interface by presenting more options is a very user-friendly accordion-style wizard.
Choose your source and destination orgs, data set or deployment plan, and metadata, then deploy with ease. Refer to Guided Deployment for details.
 | By default, the Deploy buttons in the data set editor and the deployment plans page point to the legacy deployment center to maintain backwards compatibility. Prodly strongly recommends configuring the buttons to use the new guided deployment feature, so that you can deploy both data and metadata with a single click. |
To match the functionality of the legacy deployment center, you can now deploy to up to five destination orgs at once via guided deployment. Refer to Selecting the Source and Destination for details.
Deployment History
After clicking Deploy in the Confirm Deployment section of Guided Deployment, the new Deployment History page shows the status of the current deployment and of all past deployments. You can drill into the familiar deployment results views, which now include metadata deployment results.
Refer to Deployment History for details.
Version Control
You can now use your version control system (VCS) to capture snapshots of your reference data after org-to-org deployments for versioning or backup. Refer to Org-to-Org Deployment and the VCS for details.
And for the scenario where you always deploy all records in a specific set of objects (that is, you do not need the query filter to filter records), you can now track and deploy your data without the need for data sets or deployment plans! Refer to Version-Control Deployment for details.
You also now can change the list of objects you are managing under version control. Add and remove objects from the list at any time. Refer to Editing the Managed Objects List for details.
Azure Cloud Integration
AppOps Release now supports integration with Microsoft Azure Cloud. So you can now integrate AppOps Release with the GitHub, Atlassian Bitbucket, and Microsoft Azure version control system (VCS) frameworks. Upgrade users must perform these configuration steps.
View Encrypted Data
We’ve eliminated the need to set the View Encrypted Data system permission flag.
Usability Improvements
- The most significant usability improvement is the combining of the apps and the central focus of the product under the AppOps Release tab.
- Controlling both org-to-org deployment and version control deployment from the management board is another significant improvement.
- We’ve done many little user interface tweaks to the management board and elsewhere for better usability.
- We’ve increased these governor limits:
- Maximum events per event type per event scope – from 10 to 100.
- Maximum data sets per deployment plan step – from 15 to 100.
- Maximum data sets per deployment plan – from 30 to 1000.
Resolved Issues
This table lists resolved issues in Prodly AppOps Spring ‘21 major and minor releases.
| ID | Description | Release Date |
|---|---|---|
| AP-5087 | Deployment mysteriously failing. In certain cases, AppOps Release was submitting an empty CSV file to upload as a bulk data job, causing deployment to fail. | August 5, 2021 |
| AP-5086 | Data not deploying correctly. On rare occasions, certain fields and values were getting transposed on insert. | August 5, 2021 |
| AP-4859 | AppOps Release and AppOps Test tabs don’t display contents. For software installed in a sandbox created off a production org, tab contents weren’t displaying due to a failing license check. | June 29, 2021 |
| AP-4810 | DX plugin needs access token. When a connection has no refresh token, the DX plugin now uses the access token. | June 15, 2021 |
| AP-4797 | Modified Apex class failing metadata compare. When users updated information in just the body of the class, the AppOps Release metadata comparison function wasn’t recognizing the changes. | June 15, 2021 |
| AP-4785 | 500 – Internal Server Error When the number of deployment orgs for a Prodly account was exactly divisible by the batch size, AppOps Release was attempting to process a batch of size 0, causing the error. | June 15, 2021 |
| AP-4653 | Unchanged lookup fields show as changed in metadata compare. AppOps Release was interpreting metadata lookup fields with filters in Salesforce as changed metadata, even when the filters where the same in the source and destination orgs. | June 8, 2021 |
| AP-4565 | Some records are being duplicated. Deployment was creating duplicates when records were previously deployed using a separate installation of the Prodly AppOps managed package. | June 1, 2021 |
| AP-4564 | Log messages are sometimes incomplete. We’ve once again beefed up our internal logging to give our customer success team more information to solve deployment issues that arise. | June 1, 2021 |
| AP-4560 | Modified custom field does not appear in metadata compare. Under certain circumstances, the metadata compare was not recognizing recently-modified custom fields. | June 1, 2021 |
| AP-4539 | Metadata components incorrectly shown as changed. Under certain circumstances, the metadata compare was erroneously listing some components as changed even though the values matched. | May 25, 2021 |
| AP-4533 | Endless spinner appears on control org card when no control org connection. When accessing the management board before ever creating a control org connection record, AppOps Release was erroneously displaying a spinner on the control org card. | May 25, 2021 |
| AP-4529 | “Access unavailable from this org” page shows up unexpectedly. When there are no managed org cards, we now display the management board instead of the unexpected “no access” page. | May 25, 2021 |
| AP-4505 | VCS setup wizard sometimes appears when clicking the Management Board page. An authorization check that was required back when we first designed the management board, but is no longer needed, has been removed. | May 25, 2021 |
| AP-4503 | Guided Deployment page resets after navigating away. When you click another tab or page and then return to the Guided Deployment page, the information on the page is now retained. | May 25, 2021 |
| AP-4481 | Concurrent deployments sometimes fail. When selecting more than one destination org in guided deployment, deployments were failing when the deployment was the very first time any data was being deployed to a newly managed org. | May 25, 2021 |
| AP-4466 | Metadata comparison failing with workspace error. We’ve added a check that prohibits starting a new metadata compare on orgs with a metadata deployment currently in progress. | May 25, 2021 |
| AP-4462 | Add custom setting to exclude metadata types. For orgs with a huge amount of metadata, a new custom setting (accessible only to Prodly support) now provides a way to reduce the amount of metadata retrieved for the org comparison. | May 25, 2021 |
| AP-4461 | Add personal access token option to all VCS options. During initial VCS integration, you can now specify a personal access token for each VCS integration that supports them. | May 25, 2021 |
| AP-4459 | Not all repositories are retrieved during VCS setup. We now retrieve all the repositories (instead of just the first 100) and have added a search box to filter the results for easier selection. | May 25, 2021 |
| AP-4458 | Improve order of initial checks. We’ve resequenced the initial validity checks (valid license, valid account, control org, etc) when displays the AppOps Release and AppOps Test tabs to present any errors in an order that better diagnoses the problem. | May 25, 2021 |
| AP-4456 | Null pointer during deployment. We’ve added a check to ignore the extra batch with no records that Salesforce occasionally returns during deployment. | May 25, 2021 |
| AP-4445 | Improve metadata retrieval for workflows. We’ve improved workflow retrieval time by first querying objects for workflows. | May 25, 2021 |
| AP-3485 | Clicking outside of the VCS setup dialog box should not hide it. The VCS setup dialog box now remains visible when clicking elsewhere in the tab window. | May 25, 2021 |
| AP-3222 | Endless spinner on the control org card. After deleting the control org connection record and recreating it under a different user, returning to the management board was erroneously displaying a spinner on the control org card. | May 25, 2021 |
| AP-4528 | Repository branch not populated for Azure. When selecting Azure as the VCS, the initial org data retrieval was not correctly populating the VCS repository branch. | May 18, 2021 |
| AP-4465 | Metadata compare is falsely showing some objects as deleted. The retrieval query was not returning all object names in all cases, resulting in false mismatches when comparing the source and destination metadata. | May 11, 2021 |
| AP-4440 | Not all records are deploying. A fix done in minor release 9 was inadvertently causing only the first 1000 records in a batch to deploy. | May 11, 2021 |
| AP-4429 | Batch result from Salesforce returns null. For pending records, the batch result was erroneously null. | May 4, 2021 |
| AP-4425 | Updates to custom fields are not recognized in metadata compare. After creating and deploying a new custom metadata field, changing the field then comparing the metadata a second time was not recognizing the changed field. | May 4, 2021 |
| AP-4424 | Managed orgs shown for wrong account. When two browser tabs were open, each logged into a different Prodly AppOps managed package installation, the guided deployment source and destination connection selections for both installations were being listed. | May 4, 2021 |
| AP-4408 | Reduce management board load on the system. When deployments are not running, we’ve lessened the frequency the management board polls for updates to reduce the overall load on the system. | May 4, 2021 |
| AP-4406 | Tabs don’t work in Safari. Privacy settings for the Safari web browser prevent the AppOps Release and AppOps Test tabs from displaying. Refer to Configuring the Safari Browser for details. | May 4, 2021 |
| AP-4397 | “Initialization in progress…” spinner spins forever with no error message. Occasionally when managing an org, the initialization steps were getting stuck in a queued state and never executing. | May 4, 2021 |
| AP-4395 | Deployment plan failed with 414 error. An issue with some relationship queries was causing deployment to fail. | May 4, 2021 |
| AP-4394 | Null pointer exception during deployment. Under certain circumstances, deployment was failing when the deployment request contained access tokens. | May 4, 2021 |
| AP-4370 | Add more logging for metadata compare and deploy. We’ve added more internal logging to help customer support help you resolve your issues faster. | May 4, 2021 |
| AP-4369 | Add error handling to metadata. As you can see below, we’ve added a lot of error checking as part of this minor release. | May 4, 2021 |
| AP-4073 | Null pointer error during deployment. An unexpected null pointer was causing the whole deployment to fail. We’ve changed it to just fail the record instead of the whole deployment. | May 4, 2021 |
| AP-3800 | Unexpected 502 error. We’ve added a proxy timeout check to catch some 502 errors before they happen. | May 4, 2021 |
| AP-3799 | Unexpected 502 and 503 errors. We’ve reduced the batch size of some of our processing functions to help minimize these errors. | May 4, 2021 |
| AP-3715 | Cannot manage org. After first deploying from the deployment center, subsequent attempts to manage the destination org were failing. | May 4, 2021 |
| AP-3540 | Improve the “500 – internal server error” message. This error can occur for several reasons, so we now provide a better description of each possible error. | May 4, 2021 |
| AP-3532 | Card name has disappeared. On the management board, cards with inactive connections were displaying without a name. | May 4, 2021 |
| AP-3489 | Manual refresh required to see new managed org. Under certain circumstances, initialization of a new managed org was successful, but the card failed to appear on the board. | May 4, 2021 |
| AP-3488 | Unexpected “no VCS authentication token” error. We’ve resolved an issue that was losing track of the connection to the VCS. | May 4, 2021 |
| AP-3469 | VCS setup wizard redirects to wrong AppOps Release page after Bitbucket authentication. For Bitbucket only, after the authentication step, the VCS setup wizard was not correctly advancing to the next step. | May 4, 2021 |
| AP-3467 | Clear out managed objects list when disconnecting repo. When disconnecting from the VCS and then reconnecting, all previously-managed objects were being included, not just the ones selected in setup. | May 4, 2021 |
| AP-3462 | New Managed Org fails without explanation when object missing from destination. When an object (for example Consumption Schedule) was missing from the org’s schema, new managed org was silently failing when attempting to deploy the branch data to the org. | May 4, 2021 |
| AP-3451 | Deployment History filter resets itself after a couple of seconds. An automatic screen refresh was ignoring the column filters. | May 4, 2021 |
| AP-3445 | Connection name has disappeared from control org card. The control org card name was coming up blank due to the way we were retrieving information differently for the control org. | May 4, 2021 |
| AP-3430 | Deployment history page loads twice. When a deployment is launched from guided deployment, the deployment history page no longer loads then reloads. | May 4, 2021 |
| AP-3423 | Make “Could not manage org” error message more informative. We’ve updated the message to “Cannot manage the selected org because it is already managed by another account.” | May 4, 2021 |
| AP-3236 | Several minor UI fixes. We’ve done some minor fixes and text phrasing adjustments here and there to align with the shift to “org-centric”. | May 4, 2021 |
| AP-3718 | Expired token is causing failures. We now make sure the control org access token is valid before attempting deployment. And if the token has expired, we refresh it. | April 19, 2021 |
| AP-3716 | Unexpected 401, 502, and 503 errors. Because many of these errors occur due to timing issues, we are now retrying the failed records a second time before failing the deployment. | April 19, 2021 |
| AP-3714 | Deployment fails with large number of content version records. Under certain circumstances, deployment was failing with as little as 200 content version records. | April 17, 2021 |
| AP-3554 | Deploying to the same object in the same org causes a 500 error. When the source and destination was the same org, transformations to the same object were failing. | April 15, 2021 |
| AP-3553 | Deploying to the same org with transformations causes a 406 error. When the source and destination was the same org, transformations to another object were failing. | April 15, 2021 |
| AP-3551 | Empty batch causes 500 error. Under certain circumstances, splitting batches was creating a batch of size 0, causing a null pointer error. | April 15, 2021 |
| AP-3550 | Duplicate record inserted after update fails. Under certain circumstances, AppOps Release was erroneously reinserting the record after attempting to update it failed. | April 15, 2021 |
| AP-3547 | DX plugin erroneously giving “Deployment failed due to Do Not Allow As Destination” error. We’ve corrected an issue where deployments to a scratch org using our DX plugin were failing because of unnecessarily checking for the “do not allow” flag. | April 14, 2021 |
| AP-3543 | Some records created through a Salesforce refresh are being duplicated. When deploying, AppOps Release was creating duplicates for records in the destination org that were never previously deployed through AppOps Release. | April 14, 2021 |
| AP-3535 | Existing destination org record values cause conflicts. Another corner case resulting in the 500 error had to do with unexpected record values in the destination org. | April 12, 2021 |
| AP-3531 | Prevent 500 error source record conflict. Under certain circumstances, AppOps Release was attempting to insert a new record rather than update the existing record. | April 12, 2021 |
| AP-3526 | Prevent 406 error from happening in the first place. The issue that was creating the need for earlier detection of deployment failures has itself now been resolved. | April 10, 2021 |
| AP-3525 | Null pointer error during deployment simulation. We’ve corrected an issue that was causing a null pointer error to occur during some deployment simulations. | April 8, 2021 |
| AP-3524 | Halt failed deployments sooner and display a better message. Under certain circumstances, deployment failure is now being detected sooner, reporting a more meaningful message. | April 8, 2021 |
| AP-2875 | Erroneously getting “Deployment failed due to Do Not Allow As Destination” error. We’ve corrected an issue where deployments were not proceeding because Do Not Allow As Destination was selected on the control org connection record. | April 7, 2021 |
| AP-3365 | Add VEID support for the attachments. We now support deploying the Attachment object using VEID. | April 6, 2021 |
| AP-3244 | Null pointer exception during data set deployment. We’ve resolved an issue with a null pointer specific to a customer’s use case. | April 6, 2021 |
| AP-3125 | Rename deployment result name field. To accommodate the addition of the Deployment Name, we’ve renamed the old Deployment Result Name field to Deployment Results Number. | April 6, 2021 |
| AP-3124 | Add deployment name to legacy deployment pages. With the ability now to specify a deployment name in guided deployment, we’ve also added deployment name to the legacy deployment pages. | April 6, 2021 |
| AP-3119 | Failed deployment needs error message to explain. We’ve added “Deployment failed because you have Do Not Allow As Destination selected for the destination org.” to the deployment results. | April 6, 2021 |
| AP-3093 | Show query filters on deployment results. We’ve added query filters as another related list on the deployment results. | April 6, 2021 |
| AP-3090 | Deployment result schema changes. To accommodate the new “org-centric” focus, metadata deployment, and query filtering through the API, we’ve connected these new objects to the Deployment Result object,: Deployment, Metadata Deployment Result, Metadata Component Deployment Result, and Query Filter. | April 6, 2021 |
| AP-2893 | Plan deployment throws null pointer exception. We’ve corrected the issue of a null pointer occurring while processing the fields in DeploymentDatasetUtilities. | April 6, 2021 |
| AP-2794 | Error deploying Content Version and Content Document objects. In org-to-org deployment, the Content Version and Content Document objects were not deploying due to an attempt to write to a non-updateable lookup field and the way Salesforce autogenerates documents. | April 6, 2021 |
| AP-2764 | Refreshed dev sandbox causes VEID record mismatch during org-to-org deployment. After deploying records from a dev sandbox to test to UAT to production, refreshing the dev sandbox then redeploying through the sequence again was causing duplicate records under certain other conditions. | April 6, 2021 |
| AP-2739 | Show the AppOps Release product on the Prodly Account tab. With the apps merging, the Prodly Account tab now lists the AppOps Release product, rather than just the version control/change management feature. | April 6, 2021 |