--- title: "September" slug: "september-3" updated: 2025-09-24T17:03:46Z published: 2025-09-24T17:03:46Z canonical: "docs.saasify.ai/september-3" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.saasify.ai/llms.txt > Use this file to discover all available pages before exploring further. # September ### **In this Article** - [Salesforce](/v1/docs/september-3#salesforce) - [Known Issues](/v1/docs/september-3#known-issues) - [Next Release](/v1/docs/september-3#next-release) ## These release notes provide information about new features and bug fixes in SaaSify Salesforce package 3.133 ## Salesforce : ### Mappings #### Feature Updates - Introduced **Co-sell** Mapping module - To configure default cloud provider while creating co-sell - Enabled picklist for Static Mapping type for below fields in GCP RPOP module: - Payment Frequency - Is Free Credit Enabled - Pricing Model - Unused Commitment Rule Type - Enabled picklist for Static Mapping type for below fields in AWS CPPO module: - Contract duration - Product type ### Partner Funding #### Feature Updates - Support for new template (innovation sandbox) - Added a message prompting users to click the “Add” button to guide them on how to create a cash claim - Users can now add and manage multiple states in the Project Details section. ### All Private Offers/ CPPO/ RPOP (AWS/ AMP/ GCP) #### Feature Updates - Added a support to view uploaded EULA file in Draft status #### Resolved Issues - Updated the error message displayed when clicking Create and Save CPPO under reader roles. The message is now aligned with the existing error message shown for Private Offers, ensuring a consistent experience. - Removed file count limit for private offers, users can now upload unlimited files within the size limit ### AWS Channel Partner Private Offer #### Feature Updates - Removed the validation when FPS model is selected from payment schedules #### Resolved Issues - Resolved an issue where selecting the **Individual Pricing Discount** **type** with FPS enabled caused errors when publishing a CP offer ### Microsoft Private Offer #### Feature Updates - Added validation for the **previous plan name** property in Salesforce. This prevents publish failures when creating AMP POs through the scheduler or public API - Added API-level validation for Azure private offers to ensure the **Accept By** date cannot be set to today’s date, aligning with the existing UI restriction ### GCP Private Offer #### Feature Updates - Added new deal statuses for private offers with a total value greater than or equal to 10 million - The new values to be added under **Status** picklist field in **Private Offer (****Offering__c****)** object. - The new value should be such as: - Label: **Pending Review** **From** **Marketplace** - API Value: **PendingReviewFromMarketplace** - The new value should be such as: - Label: **Rejected By Marketplace** - API Value: **Rejected** - Made the **Customer** **Company Name** field optional ### GCP RPOP #### Feature Updates - Updated validation to allow **Plan End Date** to be the same as **Plan Start Date** ### GCP Co-sell #### Feature Updates - GCP: Terminal stage email notifications for SFDC ### AWS Private Offer #### Feature Updates - Support for visibility of **Product ID** in **New Private offer** and **Agreement based offer** in **details screen** - Support for generating **Buyer** **Installment** **Plan** automatically for New Private offer and FDA based offers - Only **Annual**, **Monthly** and **Quarterly** frequency is supported for now - For AWS Private Offers, the label “**Marketplace Offer Identifier**” has been updated to “**Product ID**” - Products that have visibility status as **Public** and **Limited** will only be shown under Product selection while creating a Private offer / ABO - Visibility of **Product ID** while creating New Private offer / FDA / ABO ### AWS CPPO Authorization #### Feature Updates - Introduced support for **adding multiple product dimensions** for **FPS discount type** while creating authorizations for SaaS products - This is applicable when the public offer has **single dimension per contract** purchasing options enabled at the product level ### ACE Co-sell #### Feature Updates - AWS Invitation record now correctly displays **Customer Business Problem** instead of **Project Description** - Validation added for **Estimated Revenue Amount**: entering or updating with **0** now logs an error across **Manual Creation, Partner Referrals, and AWS Referral co-sells (scheduler auto-sync)** #### Resolved Issues - Fixed Co-sell CRM sync errors caused by **insufficient access on cross-reference entities**, ensuring successful resync across all tenants ### Microsoft Co-sell #### Feature Updates - Added a support of picklist value under **Stage** field called “**Lost**” to resolve sync failures of co-sell caused by missing stage value - **Setup steps**: - Navigate to **Setup (Gear icon**) from top right - Go to **Object Manager** - Search for **Co-sell Microsoft object** and click on it - Select **Fields & Relationships** - Search for **Stage** and click on it - Click on **New** - Add the value as “**Lost**” and click **Save** - Scheduler for **MS Co-sell** now enforces UI validation: amounts must be **> 0** and integers only. ## Known Issues - Currently we are not showing Reseller Name while creating the AWS CPPO Authorization in SFDC. - SFDC – Product dimensions get cleared out in case of AWS CPPO – FPS when user edits the CPPO in draft and let users to add only one dimension - SFDC- 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 - SFDC- There is a validation issue where users are allowed to save when extending **GCP RPOP** with a date beyond the plan end date - SFDC- **GCP Private offer**: Validation is missing for invalid email addresses entered in the **Sales Agent Primary Contact** field - SFDC- **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. - SFDC- Adding custom dimensions is not restricted for **AWS CPPO Professional Services** authorization - SFDC – **Custom frequency** is not supported while creating Private offer in **Buyer** **Installment** **Plan** - SFDC – **Number of** **Installments**, **Outstanding Amount** and **Total amount in plan** fields are not supported under **Buyer** **Installment** **plan** while creating Private offer - SFDC – For Buyer Installment plan, when installments are modified, the **Total Contract Value** will not trigger validation against the defined **Contract Total** - SFDC- Creation of **AMI CPPO Authorization** is not supported from SFDC ## Next Release - October, 2025.