Release Date | February 22nd, 2023
Summary
With each release, Prodly strives to improve our product and deliver the results and features our users need to make their work easier and more efficient. Our release notes are available to our users to review our most anticipated feature releases including requests and suggestions provided by our customers and updates on our latest bug fixes.
For our users, from our users
Suggested improvements and feature requests from our users
- Enhancements on Data set preview
- Schema connection that shows on Data Set preview in Guided Deployment will show as Control org if schema is not set
- Query and Limit preview will show as ‘None’ if nothing is saved on the data set
Bug Fixes & Enhancements
Latest fixes and updates
- PM-87 Error message to indicate incorrect workspace when connecting to Bitbucket
- PM-91 Error message to indicate Bitbucket has not successfully connected
- PM-845 Deployment History filter takes into account all selected filters
- PM-905 ‘Reconnect’ for Version Control will connect to existing connection instead of creating a new connection if the connection exists
- PM-912 ‘Cancel’ will clear all existing input added for all Version Control types when setting up Version Control
- PM-1078 When connecting to Version Control with a token, once connected the status will clearly show immediately without having to refresh
- PM-1350 If an object that does not exist in an environment is selected for Versioning the object will be skipped in save to branch /deploy from branch instead of failing the entire operation
- PM-1595 Detailed results now available for version control operations
- PM-1750 Branch link in confirmation pop up for Bitbucket initial set up in a connected environment no longer leads to a 404 page
- PM-1818 Search bar for Version Control object selection is now more clearly visible
- PM-1835 ‘Need Help’ link on Establish Control screen directs to the Prodly help site
- PM-1896 Link to repository on Environment card is now redirecting to the corresponding repository
- PM-2002 ‘Added By’ showing on Environment card links to the User page in the Control Org
- PM-2153 Version Control setup no longer switching sporadically from Azure to Github
- PM-2355 Branch link in confirmation pop up for VC operations now links to the correct branch
- PM-2433 Deactivating Events with Version Control deployments is now appearing in the detailed Deployment Results as ‘Deactivated Events: Yes’
- PM-2528 Deployment Activity scaled to fit smaller screen view
- PM-2557 Data sets in Guided Deployment are now sorted by the last modified and loads the last 2000
- PM-2560 Version Control setup jobs are now showing in the Deployment History table
- PM-2564 Version Control jobs now have a main result in the Deployment History ‘Result’ column
- PM-2566 Error message appears if adding an Environment with a name that already exists
- PM-2627 When Version Control is not connected the tool tip that appears has been updated to reflect this
- PM-2663 ‘Reauthenticate’ on Environment Card will create a new connection record if no connection record exists
- PM-2674 Changing the name of the repository in Azure will no longer result in ‘No data’ for selected branches in Version Control setup
- PM-2805 When setting up an Environment with JWT the control URL will appear instead of the Sandbox URL
- PM-2834 Control Connection will update instead of creating a new connection if the connection already exists when Establishing Control
Managed Package Schema Changes
This release contains the following changes to the managed package schema. Prodly Permission Sets have been updated to reflect these new components for package 1.226
- Salesforce Managed Package: Salesforce API v57