--- title: "January" slug: "january-1" updated: 2025-01-28T13:50:35Z published: 2025-01-28T13:50:35Z canonical: "docs.saasify.ai/january-1" --- > ## 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. # January ### **In this Article** - [Salesforce](/v1/docs/january-1#salesforce) - [Known Issues](/v1/docs/january-1#known-issues) - [Next Release](/v1/docs/january-1#next-release) ## These release notes provide information about new features and bug fixes in SaaSify Salesforce package 3.95 ## Salesforce : > [!NOTE] > Note: > > Below are the updates for Salesforce Package Version - 3.95 ### Mappings #### Feature Updates - Introduced **Validate Mappings** functionality under all modules - This functionality will help users to add newly introduced mappings in any module whenever they upgrade the package - Users can also identify if any mapping is outdated and needs to be deleted from Custom Metadata - Introduced a new field: **Reseller Notification Recipients** under **Microsoft Private Offer** Module - Increased height for dual list of AWS products to get visibility of more products under ACE Co-sell - Introduced a new field - **Private Offer Dependent Records** under **AWS Private Offer Module**. Currently only custom apex mapping type is supported for this field. #### Resolved Issues - Resolved an issue where mappings for additional dimensions in the AWS Private offer module should appear under usage dimensions while creating an AWS Private offer. - Fixed Custom Apex Mapping type issues for Microsoft Private Offer module ### AWS Private Offer #### Feature updates - **Customer Email** and **Customer Company Name** fields will be optional now while creating AWS Private offer / ABO - Addition of **Offer Created Date** and **Product** **Pricing model** fields under details screen - Renamed Entitlement type with **Purchasing options** under details screen - Renamed **Buyer can choose one or more options offered** with **Multiple dimensions per contract** - Renamed **Buyer can choose One tier to multiple** **tier** **offered** with **Single dimension per contract** - Implemented the functionality to show the calculation of end date under details screen when Contract duration is selected while creating FDA offer - Disabled the selection of activity breadcrumb from details screen #### Resolved Issues - Resolved issue where previously inserted dimensions were still shown in the Product dimension selection drop down - Fixed the issue under usage dimensions where it was not showing previous private offer usage dimension price for Agreement based offer ### AWS CPPO #### Feature updates - Support for Scheduler to create CPPO records - Action Supported: **Create as Draft** & **Create and Submit** - Removed the functionality of adding multiple buyer account id and changed the tooltip of Buyer Account Id field - Enhanced Reseller agreement selection with drop-down values - **Authorization Name field changes:** - Whitespaces will be allowed - Modified the Note - Minimum limit of entering characters changed to “1” #### Resolved Issues - Fixed the issue where **Tracking id** copy functionality was not working ### AZURE Private Offer #### Feature updates - Implemented MPO New Field and Email Notifications - Addition of New field while creating MPO - **Reseller Notification Recipients** - Implemented MPO Email Notifications - **Azure MPO is ready to be created** - **Event to configure from Notifications from WebApp-** Private offer ready for purchase - **Azure MPO extended to Customer** - **Event to configure from Notifications from WebApp -** Azure: Private offer pending acceptance from partner - Refactored the Private Offer/MPO status breadcrumb. Awaiting update status will only appear when the user withdraws the private offer, not all the time. - Disabled the selection of activity breadcrumb from details screen - Removed date resetting for the Start date type field when changing products. #### Resolved Issues - Fixed the issue where if user selected Start date type as Accepted date and publish the private offer. It resulted in error. ### AZURE Multiparty Private Offer #### Feature updates - Introduced New MPO Stages - **Details shared with Partner** - **MPO Published** #### Resolved Issues - Fixed the issue where Publish button was showing up under MPO Published stage. ### GCP Private Offer #### Feature updates - Implemented the functionality to preview Standard and Custom EULA file when Private Offer is published - Disabled the selection of activity breadcrumb from details screen ### ACE Co-sell #### Feature updates - Support to associate / lookup existing private offer in Co-sell - Implemented the Closed Lost Reason a required field per AWS API - Disabled the selection of activity breadcrumb from details screen - Renamed **Provider ID** with **ACE ID** - Implemented a banner message to display the rejection reason for Partner Originated Co-sells on the Overview screen when AWS rejects them. - Added a Save and Submit option to the Edit Co-sell pop-up #### Resolved Issues - Fixed the issue when user hovered on Associate Offer link or Stage, it was not showing hand icon. - Fixed the issue where AWS Originated co-sells were not getting launched through Scheduler ### Scheduler #### Feature updates - Added **Filter Type** drop-down under Scheduler and possible values are: - **Filter builder** – User can create co-sell / private offer records using filters on fields on related object - **Filter Query** - Allow users to use Apex SOQL queries to filter and create Co-sell records based on the query. ## Known Issues - Currently we are not showing **Reseller name** while creating the AWS CPPO Authorization in SFDC. - SFDC- While creating a new GCP PO / Amend offer, if user enables Auto Renew and check the total contract value. Total contract value will be shown more than the expected contract value in SF. - SFDC- While amending a GCP private offer, installments will not be shown correctly in case of renewals. - After Microsoft Private Offer purchase, changes made to the auto-renew setting in the Azure Portal will not be automatically synced in Salesforce (SF). ## Next Release - February, 2025.