Release Date | December 12, 2022
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.
What we are most excited about
Highlights from our latest release
- System Integrator Engagement Tracker
- Partner accounts are now able to track their projects with by creating Engagements and linking them to their deployments
- Engagements must include
- Engagement Name (Text)
- Engagement Type (Managed Services or Implementation)
- Type of Project (Text)
- Target Completion Date (Date)
- Account (Text)
- Engagements must be linked to Environments
- When adding a new Environment, users must link an existing engagement or create a new one
- Engagements to be associated with an deployment can be selected within Guided Deployment after choosing a source and destination
- If no engagements exist, users are prompted to create one
- Engagements related to the Destination org will determine what Engagements are available for selection for a deployment
- For Deployments to multiple destinations, only Engagements that are common amongst all destination orgs will be available for selection
- Only one Engagement can be selected per deployment and is a requirement
- Associated Engagements will also appear on Product Usage reports
- System Integrators can create scratch orgs without having to link engagements
For our users, from our users
Suggested improvements and feature requests from our users
- Environment Access Control Information
- Users will now be presented with a pop up message when adding a new Environment to inform them of how to take advantage of Prodly’s Environment Access Control
- The message will include a link that directs users to the Sharing Settings page where they can modify user’s access to specific environments
- Scratch Org Enhancements
- Users will now receive an email containing the relevant error messages if a Scratch Org creation fails so they can be notified immediately of any issues
- Only Production org types will be available for selection as a Source when creating a Scratch Org
- If DevHub is not enabled users will not be able to create a scratch org
- Users can drag and drop to select the order they want to install their packages in
- Scratch Org initial deployment results will include the rollback features chosen by the user upon creating the scratch org
- Auto-install Advanced Processing for CPQ objects with VC
- When one of the following objects are selected to be managed in Version Control, Prodly will automatically insert Managed Fields and Managed Relationship records along with the Managed Object
- Consumption schedules
- Price rules
- Product rules
- Unmanaging one of these objects will remove the Managed Fields and Managed Relationship records along with the Managed Object
- When one of the following objects are selected to be managed in Version Control, Prodly will automatically insert Managed Fields and Managed Relationship records along with the Managed Object
Bug Fixes & Enhancements
Latest fixes and updates
- PM-1393 Selecting the Deployment Name in Deployment History for Deployments with Version Control now redirects to Deployment Result page and Source link navigates to the connected repository in a new page
- PM-1456 Data Preview will stop running and reset when Data Selection Method is changed
- PM-1963 Metadata deployments now show Start/Completion Date/Time on Deployment Result
- PM-2084 Scratch Org now available for selection as Connection Org type
- PM-2156 Error message clearly states the issue when performing a check in to a Locked Branch
- PM-2169 Data set selection is mandatory for scratch org creation if the Data section is toggled on
- PM-2083 Redeploy will recall Jiras linked to previous deployment and link them again on the rerun
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.222.
*Required: Requires at least read access to this component to use the application
| Component Name (Label) | Component Type | Parent Component | Description | *Required |
| Engagement__c (Engagement) | Custom Object | Parter service integrator engagement tracking. | Yes | |
| Customer_Account__c (Customer Account) | Custom Field | Engagement | Name of the customer account for the engagement. | Yes |
| Engagement_Type__c (Engagement Type) | Custom Field | Engagement | Contains the type of engagement. Required Field | Yes |
| Project_Type__c (Project Type) | Custom Field | Engagement | SI type of project. Required Field | Yes |
| Finish_Date__c (Finish Date) | Custom Field | Engagement | SI date when Implementation will be completed. Required Field | Yes |
| Engagement Layout | Page Layout | Engagement | Page layout for engagement. | Yes |
| Engagement_Membership__c (Engagement Membership) | Custom Object | Associates managed environments with engagements. | Yes | |
| Engagement_Id__c (Engagement Id) | Custom Field | Engagement Membership | Associated engagement for the engagement membership. | Yes |
| Managed_Environment_Id__c (Managed Environment Id) | Custom Field | Engagement Membership | Associated managed environment for the engagement membership. | Yes |
| Engagement Membership Layout | Page Layout | Engagement Membership | Page layout for engagement membership. | Yes |
| Engagement__c (Engagement) | Custom Field | Deployment | Associate an engagement with a deployment. | Yes |