Find the release notes for Managed Package 2.5.1, for either the vh or vh2 version of the managed package. Your Vivun Technical Account Manager can tell you which set of instructions to follow.
Managed Package 2.5.1 Release for vh2
Managed Package 2.5.1 Release for vh2
Managed Package 2.5.1 Release
Release Date: 30-MAY-2023
The Managed Package 2.5.1 Release includes the following features, enhancements, and resolved issues.
Reminder: When installing a Hero by Vivun Managed Package into your production org, select Install for Admins Only.
Important Installation Notes
1. Prior to installing the latest Managed Package, reach out to your Technical Account Manager to enable Permissions Set creation, so you can recreate Permissions Sets. Once enabled, run the Create option in the 'Create or Update Permission Sets in Salesforce Now' section of Hero Settings under Setup > Settings > Permission Sets.
2. Once the above is complete, you can proceed with the upgrade.
3. Once the upgrade is complete, you must:
Recreate Permissions Sets; Setup > Settings > Permission Sets, click Start under 'Sync Users from Saelsforce to Hero Now.'
Reach out to Vivun to let us know your installation is complete.
Opportunity Amount Scheduled Job Sync
To ensure data quality with Opportunity Amounts syncing with related Hero Objects, a one-time batch job, ‘Hero_Gap_Amount_Sync,’ is included in Managed Package 2.5.1 for Admins to execute. The job will correctly match the Amount Field selected in the Amount Source picklist on each Opportunity Gap, in batches of 200 Opportunities at a time. This is only required for existing customers who have non-Hero users updating Opportunities.
Before You Begin
It is only necessary to run the job once after package installation to ensure all the Opportunity Amounts sync with their related Team Member Requests and Opportunity Gaps.
If the batch job fails, or TMRs or Gaps fail to update, confirm all Gaps have a Source Amount.
Vivun recommends backing up your data prior to running the batch job below; specifically Opportunity Gaps and TMRs as those amounts are updated with the batch job. The following queries can be used to export:
SELECT CreatedById, CreatedDate, Id, IsDeleted, LastModifiedById, LastModifiedDate, LastReferencedDate, LastViewedDate, Name, SystemModstamp, vh2__Active__c, vh2__Active_Lookup__c, vh2__Amount_Source__c, vh2__Date_Delivered__c, vh2__Description__c, vh2__Opportunity__c, vh2__Opportunity_Gap_Amount__c, vh2__Opportunity_Gap_Weighted_Yield__c, vh2__Opportunity_Gap_Yield__c, vh2__Percent_Complete__c, vh2__Primary_Competitor_Solution__c, vh2__Product_Gap__c, vh2__Status__c, vh2__Type__c FROM vh2__Opportunity_Gap__c ORDER BY CreatedDate DESC | SELECT CreatedById, CreatedDate, Id, IsDeleted, LastModifiedById, LastModifiedDate, LastReferencedDate, LastViewedDate, Name, RecordTypeId, SystemModstamp, vh2__Approver__c, vh2__Approver_Comments__c, vh2__Assigned_Team_Member__c, vh2__BaseURLforEmail__c, vh2__Deliverable_End_Date__c, vh2__Deliverable_Scheduled_Date__c, vh2__Deliverable_Type__c, vh2__Demo__c, vh2__Exception__c, vh2__Opportunity__c, vh2__Opportunity_Amount__c, vh2__Request_Reason__c, vh2__Status__c, vh2__TMR_Flag__c, vh2__Type__c FROM vh2__Team_Member_Request__c ORDER BY CreatedDate DESC |
Scheduled Job Configuration
Complete the following steps to run the one-time batch job in Salesforce:
Navigate to Setup.
Search ‘Apex’ in the Quick Find and select Apex Classes.
Select Schedule Apex.
Enter the following:
Batch Job Name - ‘Hero_Gap_Amount_Sync’
Apex Class - Enter ‘OpportunityAmountHeroSyncSchedulable’ and click Go.
Select a one day period for the job to run.
Click Save.
Add New Account & Opportunity Search Apex Classes
Important Note: This is only required if your organization uses Custom Permission Sets. You can skip this step if you use the Default Permission Sets, as they are added automatically.
There are four new Apex Classes for Account and Opportunity search improvements in 2.5.1. The following Apex Classes must be added to your permission sets:
vh2.AccountSearchRestServiceV2
vh2.HeroVersionService
vh2.OpportunitySearchRestServiceV2
vh2.SObjectDescribeRestService
Enhancements
As part of continuous improvements to the Hero user experience, the Funnel and List Views are optimized to populate Accounts and Opportunities in a single REST API request. Loading and response time on the Funnel and List Views is now up to 10 times faster when making these requests for Accounts and Opportunities.
The minimum API version is updated to v46.0, to support Salesforce’s date time ICU formatting.
If your Funnel view includes more than 2,000 open Opportunities, a message appears prompting you to add filters to reduce the number of items in the Funnel.
Bug Fixes
Issue Description | Resolution |
If a TMR has ‘Clarification Needed’ status, when you add an approving comment and click ‘Approve,’ the status updates to ‘Pending Approval’ instead of ‘Approved.’ You must then approve the TMR again in order for the status to update to ‘Approved.’ | If a TMR has a ‘Clarification Needed’ status, you only need to approve it once now, and the status updates to ‘Approved.’ |
Opportunity and Account Gap Amounts are not updated in Hero when the Source Amount is updated in Salesforce by a user without a Hero permission. | The amount value on Opportunity Gaps now updates correctly with the selected source amount field in Hero when they are updated in Salesforce by any user. |
When you create a Product Gap with a specific status selected, the status reverts back to ‘Unassigned’ after save. | If you create a Product Gap with a specific status selected and save, the status persists. |
Managed Package 2.5.1 Release for vh
Managed Package 2.5.1 Release for vh
Managed Package 2.5.1 Release
Release Date: 30-MAY-2023
The Managed Package 2.5.1 Release includes the following features, enhancements, and resolved issues.
Reminder: When installing a Hero by Vivun Managed Package into your production org, select Install for Admins Only.
Important Installation Notes
1. Prior to installing the latest Managed Package, reach out to your Technical Account Manager to enable Permissions Set creation, so you can recreate Permissions Sets. Once enabled, run the Create option in the 'Create or Update Permission Sets in Salesforce Now' section of Hero Settings under Setup > Settings > Permission Sets.
2. Once the above is complete, you can proceed with the upgrade.
3. Once the upgrade is complete, you must:
Recreate Permissions Sets; Setup > Settings > Permission Sets, click Start under 'Sync Users from Saelsforce to Hero Now.'
Reach out to Vivun to let us know your installation is complete.
Opportunity Amount Scheduled Job Sync
To ensure data quality with Opportunity Amounts syncing with related Hero Objects, a one-time batch job, ‘Hero_Gap_Amount_Sync,’ is included in Managed Package 2.5.1 for Admins to execute. The job will correctly match the Amount Field selected in the Amount Source picklist on each Opportunity Gap, in batches of 200 Opportunities at a time. This is only required for existing customers who have non-Hero users updating Opportunities.
Before You Begin
It is only necessary to run the job once after package installation to ensure all the Opportunity Amounts sync with their related Team Member Requests and Opportunity Gaps.
If the batch job fails, or TMRs or Gaps fail to update, confirm all Gaps have a Source Amount.
Vivun recommends backing up your data prior to running the batch job below; specifically Opportunity Gaps and TMRs as those amounts are updated with the batch job. The following queries can be used to export:
SELECT CreatedById, CreatedDate, Id, IsDeleted, LastModifiedById, LastModifiedDate, LastReferencedDate, LastViewedDate, Name, SystemModstamp, vh__Active__c, vh__Active_Lookup__c, vh__Amount_Source__c, vh__Date_Delivered__c, vh__Description__c, vh__Opportunity__c, vh__Opportunity_Gap_Amount__c, vh__Opportunity_Gap_Weighted_Yield__c, vh__Opportunity_Gap_Yield__c, vh__Percent_Complete__c, vh__Primary_Competitor_Solution__c, vh__Product_Gap__c, vh__Status__c, vh__Type__c FROM vh__Opportunity_Gap__c ORDER BY CreatedDate DESC | SELECT CreatedById, CreatedDate, Id, IsDeleted, LastModifiedById, LastModifiedDate, LastReferencedDate, LastViewedDate, Name, RecordTypeId, SystemModstamp, vh__Approver__c, vh__Approver_Comments__c, vh__Assigned_Team_Member__c, vh__BaseURLforEmail__c, vh__Deliverable_End_Date__c, vh__Deliverable_Scheduled_Date__c, vh__Deliverable_Type__c, vh__Demo__c, vh__Exception__c, vh__Opportunity__c, vh__Opportunity_Amount__c, vh__Request_Reason__c, vh__Status__c, vh__TMR_Flag__c, vh__Type__c FROM vh__Team_Member_Request__c ORDER BY CreatedDate DESC |
Scheduled Job Configuration
Complete the following steps to run the one-time batch job in Salesforce:
Navigate to Setup.
Search ‘Apex’ in the Quick Find and select Apex Classes.
Select Schedule Apex.
Enter the following:
Batch Job Name - ‘Hero_Gap_Amount_Sync’
Apex Class - Enter ‘OpportunityAmountHeroSyncSchedulable’ and click Go.
Select a one day period for the job to run.
Click Save.
Add New Account & Opportunity Search Apex Classes
Important Note: This is only required if your organization uses Custom Permission Sets. You can skip this step if you use the Default Permission Sets, as they are added automatically.
There are four new Apex Classes for Account and Opportunity search improvements in 2.5.1. The following Apex Classes must be added to your permission sets:
vh.AccountSearchRestServiceV2
vh.HeroVersionService
vh.OpportunitySearchRestServiceV2
vh.SObjectDescribeRestService
Enhancements
There are a number of retired process builders in the Vivun Managed Package (vh) that no longer serve any function, but cannot be removed easily due to Salesforce restrictions. In order to avoid potential issues in Hero as a result of these retired but still active process builders, Managed Package 2.5.1 ensures any deactivated retired process builders do not reactivate during future upgrades.
Important Note: Vivun recommends deactivating any active versions of retired process builders to ensure best performance and prevent reactivation during future upgrades.
As part of continuous improvements to the Hero user experience, the Funnel and List Views are optimized to populate Accounts and Opportunities in a single REST API request. Loading and response time on the Funnel and List Views is now up to 10 times faster when making these requests for Accounts and Opportunities.
The minimum API version is updated to v46.0, to support Salesforce’s date time ICU formatting.
If your Funnel view includes more than 2,000 open Opportunities, a message appears prompting you to add filters to reduce the number of items in the Funnel.
Bug Fixes
Issue Description | Resolution |
If a TMR has ‘Clarification Needed’ status, when you add an approving comment and click ‘Approve,’ the status updates to ‘Pending Approval’ instead of ‘Approved.’ You must then approve the TMR again in order for the status to update to ‘Approved.’ | If a TMR has a ‘Clarification Needed’ status, you only need to approve it once now, and the status updates to ‘Approved.’ |
Opportunity and Account Gap Amounts are not updated in Hero when the Source Amount is updated in Salesforce by a user without a Hero permission. | The amount value on Opportunity Gaps now updates correctly with the selected source amount field in Hero when they are updated in Salesforce by any user. |
When you create a Product Gap with a specific status selected, the status reverts back to ‘Unassigned’ after save. | If you create a Product Gap with a specific status selected and save, the status persists. |