Improved validation for SaaS Documentation data: If the delivery model on an AWS Marketplace Co-sell is not 'SaaS or PaaS', you are no longer required to complete the SaaS Documentation fields to close a co-sell.

Access granted to view for SaaS Documentation fields: Tackle Operators now have access to view and edit SaaS Documentation fields post creation, enhancing operational awareness and flexibility.

Simplified the Closed Won workflow: Target Close Date in ISVA and SaaS Documentation Close Won workflows was removed as a requirement, streamlining the process for users.

Lead Creation flow enhancements: If Buyer Email, Buyer Last Name, or Customer Company Name are not filled in, the attempt to create a lead will not be performed as these are mandatory fields.

Operators can view and edit co-sell vendor solutions: Operators can now view and edit co-sell vendor solutions that the Tackle Integration user created.​

Unnecessary API callouts during close co-sell workflows: Users were experiencing errors when closing co-sells due to too many API calls occurring. We've reduced the number of calls, making the closing process smoother.

Payload issue for Closed Lost reason: The payload is now corrected to ensure Closed Lost reasons are not included unless the record is actually closed lost.

Errors in the Closed Lost flow: Submission errors were not being captured on the co-sell record when the co-sell was successfully submitted to Tackle. We’ve reduced some of these errors, improving the experience.

Revoking the second connection step results in a ‘Proxy’ error on screen: This issue has been fixed and the connection status now reflects this.

Unable to edit fields due to validations: To fix this issue, we’ve removed validations, making it easier for users to edit a co-sell that’s in the Action Required status with more success.

Issues when creating co-sell without solutions: This fix now prevents users from creating co-sells for AWS Marketplace and Microsoft commercial marketplace without solution records.

Auto-attach Metadata Fields added: We’ve reintroduced automatic attachment of Salesforce Opportunity ID and Name fields in AppExchange version 1.49 to maintain consistency in the metadata for Tackle Offers.

Extended description support for Microsoft listings: The capacity for Microsoft listing plan descriptions has been increased, allowing users to include larger data descriptions and add clarity to their listing information.

Close_Co_Sell_when_Opportunity_is_Closed

Insert_Lead_on_Inbound_Tackle_Co_Sell

Option 1: Use Packaged Flows

Option 2: Reapply Customizations

Create AWS Marketplace private offers directly on marketplace without signing in to Tackle: Any users with the new Send Offers To Marketplace Custom Permission can create any AWS offer, including all Direct, Partner, and Amended offers, directly on AWS without ever leaving Salesforce. Learn more about AWS direct offers in Salesforce.

Create AWS future dated agreements (FDAs) from Salesforce: When creating AWS Offers, you now have the option to select a future dated billing term with specific start and end dates for direct offers or select a max service start date when creating partner offers. The billing term, start date, end date, and max service start date can be pre-populated from mapped opportunity data by utilizing the Tackle Set Up Assistant field mapper. Learn more about FDA from Salesforce.

Amend existing AWS contracts by creating amended (agreement based offers) from Salesforce: When creating a direct AWS private offer, you can now see any existing AWS contracts for the same buyer AWS account number and listing combination. You can then chose to amend that contract to create an agreement based offer, or create a new direct offer. Learn more about amending AWS offer in Salesforce.
​
​Note: AWS currently only allows one agreement term to be active for the same buyer and listing combination. Any new direct offer must start after the existing contract ends.
​

New field for AWS private offers in Salesforce, Dimension API Name: For AWS private offers, you must now enter an API Name for pricing dimensions. Dimension API Names can also be pre-populated from opportunity data by using the Tackle Set Up Assistant field mapper.

Reseller Agreements to AWS partner offers from Salesforce: For AWS partner private offers, users can now attach reseller agreements to their partner private offers when creating them from Salesforce. Learn more about AWS partner private offers in Salesforce.

Object: Tackle Offer (tackle__Tackle_Offer__c)

Field: AWS Eula Version (tackle__EULA_Version__c)

Value: Legal Terms for Current Agreement

API Name: use-existing

Value: Enterprise Contract for AWS Marketplace

API Name: aws-enterprise

Improved field mapping experience. Based on your feedback, we have added three new features to improve your field mapping experience.

Increased Solution workflow efficiency. Scale more efficiently with our improved solution workflow.
​

Required permissions check during setup. To help ensure you’re successful during the setup process with Tackle, we’ve included a "Permissions Check" that verifies the user running through the setup process has the appropriate permission sets.

Added visibility into Opportunities and Prospects. Visibility is crucial. That's why we've added two new data points.

Improved communication with ACE. Strong partnerships are built on great communication. You now have the option to provide a "Rejection Reason" when declining an inbound Co-Sell from ACE.

"Action Required" and "Declined" stage values were not being set on Co-Sell records.

Incorrect Industry fields were being passed for MSPC Co-Sells.

Some Field Mapper entries were not saved when upgrading to 1.45 and above.

We have updated the Tackle Co-Sell Record Page to display the AWS Country field.

Resolved broken links from Tackle’s Salesforce Managed Package Listing.

The “Additional Notes Area” now displays for all clouds, and is sent to the Tackle Platform.

Error messages are now formatted and handled properly.

The Field Mapper invocable was overwriting fields.

Apply the latest version of the Tackle Co-Sell Record Page Lightning Record Page or merge changes with your customized page. See How to reassign the Lightning Record Page for more information.

Add the Label and Identifier to the Tackle Vendor Solution Search Layout:

Added Finalized Deployment Need to Sales Activities pick list field for AWS Co-sell. Includes steps to complete upgrades and manual fixes:
​
​Important: If you are upgrading to this version 1.46, you must manually update the pick list field.

Improves speed of the field mapper.

Resolves an intermittent “APEX timeout” issue observed in the Setup Assistant in Salesforce sandboxes.

New fields required by AWS: We now allow you to use the “ACE v14” fields in your Salesforce integration, including tying your AWS Solutions to your ACE Co-Sells. See the ACE v14 migration documentation for detailed information.

“Close A Co-Sell” Flow: We now allow you to display and use the “Close a Co-Sell” flow on your Salesforce Opportunity Record page. Based on your Tackle Solutions settings, we will display additional fields in your Close A Co-Sell flow.

For ISVs who have Debug Logs enabled: The integration will associate your Package Logs to Co-Sell records automatically, so you can see the last time it was synced. We also now report all inbound (Tackle -> Salesforce) errors in your Package Logs. Please see our doc on enabling debug logs for more information on this feature.

Resolved intermittent issue with Co-Sells being unable to progress beyond “Sent to Tackle”.

Resolved issue which resulted in “Has Co-Sell” not being set.

Resolved issue which resulted in AWS “Sales Stage” always being set to “Prospect”.

We now display an “Expired” status for Inbound Co-Sells that have expired in ACE.

Resolved intermittent issue that resulted in Co-Sells being stuck in “Pending Acceptance”.

Resolved “Data Mapper apex heap size to large” that impacted organizations with many fields on their Salesforce Opportunities.

Create an Offer form: We now enforce the maximum sizes of EULAs that can be attached to a Tackle Offer:

Sandbox Vendor Accounts: We now support Test Accounts in Tackle. We recommend you associate any Salesforce sandbox environments. The Tackle Salesforce integration will remove any connection from your production vendor from your Salesforce sandbox on upgrade, in order to ensure you do not mix environments.

Display Salesforce connection status in Tackle: We will display the Salesforce connection status and a link to the connected org on your Integrations page in Tackle.

Object: Co-Sell (tackle__Tackle_Co_Sell__c)

Field: Stage (tackle__Stage__c)

Full Name: Expired

Label: Expired

Expected Monthly Revenue

Target Close Date

Solutions

Related Offers

Procurement Type

Customer Software Value

Customer Software Value Currency

Contract Start Date

Contract End Date

Support multiple co-sell records on one opportunity: You can now create one Tackle co-sell record per cloud on your Salesforce Opportunities. When clicking Create Co-Sell Opportunity, you will be informed if there is already a co-sell shared with the opportunity. It will show which cloud and includes a link so you can easily see the record that was already created.
​
See our create a co-sell opportunity guide.
​
For co-sell bulk submission, we will not allow creation of co-sell record for the same cloud. If the co-sell record attached to the opportunity is no longer being worked on and you wish to create a new co-sell record, you can either delete the record or unlink it from the opportunity record.
​

Link a Tackle co-sell record to an opportunity without error: You can now link a Tackle co-sell record to an opportunity without error. Tackle Operators or Tackle Integrators are able to change the opportunity to which Tackle co-sell records are attached to easily maintain the relationship accuracy of their data. Previously, validation locked the opportunity lookup field from being edited when in certain stages. Now it can be updated on the Tackle co-sell standard form/layout without issues.
​

Data Mapper support for Text Area Fields: In the Data Mapper, Tackle Integrators can now enter default values that are longer than 255 characters. For example, in the Referral Description field you can provide adequate information to AWS to ensure your co-sell opportunity is accepted.
​

Tackle Co-Sell Page Layouts per Cloud: We recognize that each cloud has specific co-sell program requirements and data. Therefore, when viewing the Tackle co-sell record page, you will only see fields specific to the cloud the record belongs to. We've upgraded the Record Detail page on the Tackle co-sell object to Dynamic Forms. Here’s what this means for you:
​

Submission Errors

Cloud Partner

Cloud ID

Sent to Tackle At

Submitted to Cloud Partner At

Map the Opportunity owner to the Microsoft customer contacts for Co-Sell Field: Tackle Integrators can now map their contact fields for Microsoft to the opportunity owner info like first name, last name, email, and phone. They can be found in the field dropdown in Data Mapper starting with the label User.

Use the Tackle Co-sell Field Mapping data in your own flows: You can now use the data mapper in your automation flows to make it easier for SFDC admins to configure. Your admin can add the enhanced Tackle co-sell sync method in the flow and you can control the field mappings through the data mapper. For example, you could build a flow that auto-creates a co-sell when it hits certain criteria.

Map the co-sell industry field using a formula field: You can now map your custom industry field to the ACE industry field by creating a formula field. Follow this guide.

Create a Tackle co-sell in your own flows: When submitting co-sells to the Tackle API on the same transaction in which you make changes to the records in the database, you might get a Salesforce error saying you have uncommitted work pending. To avoid this, we added this method which handles the callout to the Tackle API asynchronously by splitting the transaction in two. Read how to create a Tackle co-sell in your flows.

Improved error logging for inbound co-sell flows: We enhanced the Insert Lead On Inbound Tackle CoSell flow to create a package log when an error occurs while creating the Lead record in this flow. Learn more about how to manage inbound co-sells using Leads and how to configure them.