In this Article
These release notes provide information about new features and bug fixes in SaaSify Salesforce package 3.165
Salesforce :
Mappings
Feature Updates
Introduced Renewal Type & Public Offers for Renewal fields under Microsoft Private offer module
Introduced Auto Activation field under Microsoft Private offer module
Azure Private offers
Feature Updates
We've expanded Azure private offer flexibility with two new capabilities that give you more control over contract structure and subscription renewal paths.
What's included:
Enter terms in months (1–120) or years (1–10) - whichever fits your offer
Support non-standard durations like 18 or 45 months for specialized agreements
Works across SaaS and Professional Services products
Available for: SaaS and Professional Services (New Plan type only)
Note: Flexible billing remains capped at 70 installments.
SaaS Subscription Renewal Behavior - Control exactly where subscriptions renew at contract end. Choose whether customers renew into your private offer terms or fall back to your public listing all configured during offer creation.
What's included:
Define renewal paths for every private offer
Renew into the private offer at custom negotiated terms
Renew into the public offer at standard listing terms
Configure in the new Renewals section during offer creation (right after Billing Frequency)
Available for: SaaS products (New Plan type only)
Note: Renewal options available depend on your selected billing frequency.
Auto Activation: A new toggle in SaaSify webapp that lets ISVs control when a customer's SaaS subscription and billing start.
Applies to: SaaS products only
When Enabled:
Subscription activates immediately after the customer purchases in Azure Marketplace (public offer)
Billing starts right away
Customers do not need to configure their account
Configured at Plan level
When Disabled:
Customers must configure their account after purchase
ISV must activate the subscription within 30 days
AWS Resale Authorizations
Feature Updates
SaaSify SFDC now shows AWS's "Deployed on AWS" badge under Product name on Authorization Details and Channel partner private offer screens
This tells resellers upfront whether a product counts toward the customer's AWS spend commitment (EDP/PPA), removing the manual public listing lookup
A new Refresh control on the Authorization Summary panel lets resellers pull the latest Authorization details and Product details on demand, instead of waiting for the scheduled sync.
General Enhancements
Feature Updates
Field mapping now supports sourcing values directly from a record's associated documents. Previously you could map from static values, context, expressions, formulas, and Apex extensions - but there was no way to pull document metadata into your target module. Document Finder closes that gap with a query-based mapping type that retrieves document data and maps it automatically.
Custom tags for funding - ability to add a next level filter for partner request , now user can assign a key value pair to have one deeper level of filtration
PST automation for signatures - Generate, send, track, and retrieve signed cash-claim documents directly from the funding request no leaving your CRM, no touching the signing platform. It's fully managed: the e-signature provider is abstracted behind SaaSify.
Co-sell Enhancements
Feature Updates
Partners can now see and act on their co-sell opportunities right from the Salesforce Opportunity, without jumping between records. Every co-sell linked to the opportunity appears as a card in the Co-sells tab under the newly introduced SaaSify widget, showing at a glance:
Card header with the cloud provider logo, the opportunity name, a stage sub-label (e.g., Technical Validation), and a color-coded status badge (green for Accepted/Approved/Launched, orange for Action Required/Rejected, gray for Closed Lost).
Key details — Opportunity ID, Opportunity Owner, Customer Company Name, TCV, and Target Close Date.
Cloud contacts — AWS, Microsoft, or Google contacts assigned to the referral, each with name, role (where available), and one-click email, shown once they're assigned and kept current on sync.
AWS Signal — collapsible section with the AWS Marketplace Engagement Score (High/Medium/Low) and AWS Recommended Actions when present.
Partners can open the full co-sell detail page from any card, or create a new co-sell directly from the tab.
Unified Widget — "Needs Attention" section for Co-sell - The Unified SaaSify Widget now includes a Needs Attention section at the top, above the module tabs, surfacing high-priority co-sell action items so partners can spot and act on important updates without opening individual records. The section covers three co-sell triggers:
AWS Next Step Added (High) - if a new AWS Next Step was added to a co-sell within the last 7 days.
Co-sell Closing Soon (High) - If a co-sell's Target Close Date falls within 14 days.
Stage Mismatch (Medium) - If the hyperscaler stage differs from the mapped SFDC opportunity stage.
Managed and Unmanaged customer sections in Microsoft Co-sell, the Country label now appears before the Company Name label (previously Company Name showed first), matching the expected order.
In the AWS Address Enrichment form, Customer Company Name and Domain are now shown as separate input fields, so partners understand that both keys are essential for accurate address enrichment.
AMP customer search results now display each customer's MACC status, so partners can identify MACC-eligible customers directly from the search.
Administrators can now prevent sales users from changing the ACE Owner on an AWS co-sell. The ACE Owner edit (pencil) control is driven by the Co-sell Details page layout, so admins can turn it off for relevant profiles.
Administrators can now control which users have access to Co-sell Bulk Actions (Bulk Create, Bulk Accept, Bulk Transfer Owner) in the new Salesforce managed package. This lets partners roll SaaSify out to their sales teams while keeping bulk actions restricted to Admins (or any chosen users). Access is granted through Custom Permissions rather than packaged Permission Sets, so it stays flexible and doesn't count against Salesforce's Permission Set limits.
Configuration:
After installing the managed package, create a Permission Set that includes the required Custom Permissions:
Go to Setup → Permission Sets and create a new Permission Set (e.g., "Bulk Actions").
Under Custom Permissions, enable the Bulk Action permissions you want to grant — all of them for full access (SaaSify Cosell Bulk Create, SaaSify Cosell Bulk Transfer Owner, SaaSify Cosell Bulk Accept), or only the specific ones needed.
Under App Permissions, enable the Run Flows system permission.
Save, then assign the Permission Set along with the required base Permission Set(s).
Required Permission Set combinations:
Bulk Create — SaaSify Cosell Creator + Custom Permission Set with SaaSify Cosell Bulk Create
Bulk Accept — SaaSify Cosell Reader + Custom Permission Set with SaaSify Cosell Bulk Accept
Bulk Transfer Owner — SaaSify Cosell Reader + Custom Permission Set with SaaSify Cosell Bulk Transfer Owner
Partners can now Autofill mapping fields with default suggestions based on the Salesforce objects selected in Setup. This speeds up mapping setup by pre-filling related fields instead of mapping each one manually.
Note:
If no object is configured (the "Salesforce Objects for Mapping Suggestions" setting is empty), a warning prompts the admin to Add [Account / User] object in Setup → Mapping Settings.
Autofill applies to standard mapping fields. It excludes the workflow and opportunity-creation mapping fields, and any custom fields with mapped/hardcoded IDs that aren't available by default in the org.
The Unified Widget now requires both the Co-sell Reference lookup and the Co-sell Out of Sync field to be configured on the host object before allowing Co-sell creation, preventing co-sell create/update failures on objects missing the Out of Sync field. When the field isn't configured, the Co-sell create button is disabled with admin guidance naming both required fields.
We've updated the Co-sell Details view to line up more closely with the Microsoft Partner Center experience, giving partners clearer, more accurate visibility into a referral and how it's progressing.
MACC Eligibility now visible on Co-sell Details. A customer's Microsoft Azure Consumption Commitment (MACC) eligibility is now shown directly on the Co-sell Details view — on both create and update — so partners no longer need to look elsewhere to confirm whether a referral qualifies.
Solution Play removed - The Solution Play field has been removed from the Co-sell Details view, in line with Microsoft's current Partner Center layout.
Changes to Hero Program – Include Conversation. Added an "Include Conversation" dropdown to the Hero Program section
Team Members - The Team Members section now supports adding and removing contacts, matching Partner Center's Add/Delete behavior for a simpler, more consistent experience.
Solutions – edit after submission. Partners can now add new Solutions, and remove existing ones, even after a co-sell has been submitted — in line with Partner Center.
Notes - Notes now behave in line with Microsoft: read-only for IP Co-sell and Service Co-sell deals, and editable (Help from Microsoft) for Private and Partner-led deals.
Bulk Transfer excludes inactive users — Fixed an issue where inactive users appeared in the co-sell owner transfer list and could be selected as the new owner. Inactive users are no longer shown, so partners can only transfer co-sell ownership to active users.
Edit capability for “Not Accepted” co-sells — Partners can now edit GCP outbound co-sells that are in the Not Accepted stage and resubmit them directly from Salesforce, matching Partner Hub behavior.
Acceptance-rate improvement tips across Co-sell creation - Partners now see contextual guidance while creating a Microsoft Co-sell, similar to Microsoft Partner Center, showing how completing certain fields can improve a referral's acceptance rate. These informational tips appear at the relevant steps and never block submission:
Customer Contact — a note that adding a valid customer email and phone helps Microsoft sellers better evaluate the opportunity (no outreach happens until the referral is accepted).
Estimated Deal Value — adding an accurate deal value can increase the acceptance rate by 15%.
Customer Needs — adding relevant notes can increase the acceptance rate by 5%.
Help from Microsoft — choosing a specific type of help can increase the acceptance rate by 8%.
MACC Eligibility — when a MACC-eligible customer is selected, a tip prompts partners to choose solutions that qualify under MACC to help the customer fulfil their commitment.
Known Issues
When an AWS Private Offer or ABO is manually cancelled, users can no longer change its Expiration Date or make it active again
Before creating a GCP private offer or RPOP, ensure the Channel Type is set to 'Direct' in the GCP Private Offer mapping module and 'Reseller' in the GCP RPOP mapping module else it will not let user to create a private offer or RPOP
GCP Private offer: Validation is missing for invalid email addresses entered in the Sales Agent Primary Contact field
GCP SaaS Amend offer: For the "existing end date" option, the amendment end date initially appears two days earlier than expected. However, modifying other fields such as offer duration resets the end date to the correct value.
Custom frequency is not supported while creating Private offer / CPPO in Buyer Installment Plan
Number of Instalments, Outstanding Amount and Total amount in plan fields are not supported under Buyer Installment plan while creating Private offer
Next Release
September, 2026.