July
- 11 Sep 2024
- 7 Minutes to read
- Print
July
- Updated on 11 Sep 2024
- 7 Minutes to read
- Print
Article summary
Did you find this summary helpful?
Thank you for your feedback
In this Article
These release notes provide information about new features and bug fixes in SaaSify Salesforce package. Salesforce :
ACE Co-sell
Feature Updates
Renamed the label AWS Marketplace Engagement with AWS Marketplace Engagement Score.
Enhanced the Stage Ribbon of Co-sell
If Co-sell is in Current Stage, then it will be in Blue colour
If Co-sell stage is completed, then it will be in Green colour
If Co-sell is in Closed Lost stage, then it will be in Red colour
For ACE Originated Co-sells, now we are showing Partner Acceptance Status under Co-sell Summary screen instead of AWS Status. Also, renamed the label of Partner Acceptance Status with Partner Status under Co-sell summary
Under Co-sell Summary, now we are showing Opportunity Name under Reference instead of Opportunity Id
For ACE Originated Co-sells, linking of reference is changed to lookup field instead of text field
If there is any error on any Co-sell, toaster message will remain as it is until user removes the message
Renamed Opportunity Owner with ACE Opportunity Owner and Opportunity Owner Email with ACE Opportunity Email
Resolved Issues
Fixed the issue when Co-sell is approved from ACE, it should automatically sync the stage from Opportunity to Co-sell based on Mappings configured
Fixed the issue while launching the Co-sell for Consulting Partners, AWS Account ID was not showing Asterisk symbol
Fixed the issue under Additional details after co-sell is launched and if user update the fields, data under Parent Opportunity ID was missing in Co-sell form
Fixed the issue where validation of providing less than 12 digits in AWS Account ID was missing while creating/ updating the co-sell
Fixed the issue under Customer Business Problem field if opportunity description (Only if Opportunity description/ any custom field under opportunity is mapped to Customer Business Problem) had more than 255 characters it used to show the same under Co-sell > Customer Business Problem field, it was not trimming the description from opportunity to 255 characters
Fixed the issue where Next step field was missing from Co-sell details screen
Fixed the issue for Auto-Sync if user update the Next step from Opportunity to Co-sell, data was not updating to Co-sell
Fixed the issue if user updates any ACE Originated Co-sell from Partner Central by providing Partner CRM Unique Identifier, Co-sell was not getting linked to Salesforce Opportunity automatically
Fixed the issue under Scheduler where it was picking up the Co-sell records which had different seller account. Now, scheduler will only pick the co-sell records that has the same seller code configured in Scheduler
Private Offers
If there is any error on any Private offer, toaster message will remain as is, until user dismisses the message
Fixed the issue while editing Private offer from SF, if a user provide no data under ISV Notification Recipients, Custom Metadata or Customer Notification Recipients then a pop-up used to show of component error
AWS Private Offer (New Private Offer / Future dated agreements)
Feature updates
Added Offer Description field for New Private Offer and FDA
Renamed Buyer targeted offer type with Contract duration
Added a sub section under Contract duration à Contract start date
Renamed New Offer with Start upon buyer acceptance
Renamed New offer starting at future date with Start at a future date
For New PO/ FDA, added options under Contract duration i.e. Enter a contract duration and Enter an end date
Under Contract Duration, added Duration unit and Duration fields
Renamed the label of Usage dimensions with Pricing per usage dimension
Removed the selection of Entitlement types for FPS based offers and users will be able to add multiple product dimensions with minimum quantity of “1”
Added the option to upload custom EULA under Public and Standard EULA under Legal terms
Under Usage Dimensions, now user will be able to see the price populated automatically from Public Plan defined under Offers in SaaSify
Renamed For Migration renewal offer with Existing Customer Moving to AWS Marketplace and Renewal Offer with Existing Customer on AWS Marketplace under Renewal type
Changed the labels of Renewal options,
Renamed Yes with Yes, this is a renewal offer.
Renamed No with No, this isn’t a renewal offer.
AWS CPPO
Feature updates
Implemented Renewal section under CPPO Opportunity. (Added a validation for Buyer Account ID if Renewal is selected as Yes then it will be a mandatory field)
Introduced a new field called Maximum service allowed date under CPPO Authorization. (When ISV gives this date while extending Authorization to CP, CP (While creating Private offer for Customer) can only select the Contract Start date within the range provided under Maximum service allowed date)
Introduced new workflow activity for CPPO Authorization i.e Published to Marketplace, Details shared with Partner, CPPO Published, Purchased from Marketplace.
Resolved Issues
Fixed the issue under Opportunity Name where it was not accepting hyphen and underscores
Renamed Payment ($) with Payment (USD) under Payment Schedule while creating the CPPO Authorization
Renamed Additional Usage Fees ($) Outside Of Contract with Additional usage fees (USD) outside of contract
Renamed Rate ($) with Rate (USD) and Payment ($) with Payment Amount (USD) in details screen
Fixed the issue under CPPO Stages Ribbon where Details shared with Partner stage was showing at last
GCP Private Offer
Feature updates
Multiple Orders under single Billing Account ID
We can now create multiple Private offers using same Billing Account ID and Product Combinations
Introduced a new checkbox under SaaSify > Offers > Providers > Enable multiple orders for Flat fee plans (This should be enabled in GCP Portal also).
To enable Multiple Orders Functionality from GCP Producer Portal, follow the steps mentioned below:
Navigate to Private offers from side menu
Navigate to Settings
Click on Multiple Orders tab (It will be visible only if it is enabled by GCP for your project)
Enable the Product for which you want Multiple Orders support
Added a drop-down under Offer Term (Available Active Offers): This will show all the active order ids for Amendment.
Added a table to show existing active order ids with plan name and start and end date of existing entitlement/Order.
If we have purchased 2 or more private offers with flat fee, on selecting different plan type other than flat fee we will get a validation message
Unused Commitment Rule
Unused commitment includes both commitment and partner-sponsored free credit. Unused commitment rules define how any remaining, unused committed resources or amounts are handled at the end of a billing period.
Introduced new unused commitment rules for CUD-1 and CUD-2 type of Usage based plans. Those are Rollover, Expire, and Custom.
These will be applicable on Installment schedules for both Custom and Non-Custom (Custom will be disabled) billing frequencies.
Note:
To get the latest SaaSify salesforce package with bug fixes and new feature updates, kindly reach out to saasify-support@spektrasystems.com.
Known Issues
Currently Reseller Notification Recipients is not supported from SFDC under CPPO, it’s implemented in SaaSify Web Interface
Users can only upload 1 document under Custom EULA and Custom Contract for AWS Direct Private Offer and Reseller Private Offer from SFDC
Users cannot upload multiple documents for Public and Standard EULA from SFDC for AWS Private Offers
EULA files (AWS Private offer/ FDA) along with Public or Standard are merged into a single PDF by SaaSify Web API and the combined file is not available for download via SFDC. It is only available for SaaSify Web Interface
There can be some minor changes in user experience in Salesforce for AWS Private Offer and CPPO as compared to AMMP Portal due to platform limitations.
Next Release
August 11th, 2024.