We create release notes for each Coupa version so you can quickly get up to speed with what's changed and what the impact will be to your existing Coupa implementation. The release notes aren't intended to be the definitive source of information about how features work, but instead as a tool to help you successfully upgrade to the latest version and take advantage of new features after your implementation is complete.
To make it easier to plan and execute your upgrade, the release notes are broken up into four main sections:
|Section||Description||How to Use It|
|About||Information about the new release like these instructions, Release Schedule, Supported Browsers, and more.||Make sure you know how you can use the release notes in order to receive the latest version.|
|Upgrade Guidance||Detailed information about the changes we've made to integrations and roles/permissions.||Check out the Upgrade Impact List to see what changes impact integrations and permissions.|
High-level information about the new features we've introduced in the release so you can get your head around what we've introduced in the new release. We've changed how we organize our documentation so it's based on the applications and licenses available.
Look at the new features based on which Coupa apps you've purchased so you can understand what you can take advantage of today.
Take a look at some of the apps you haven't purchased to learn how you can get more value out of Coupa.
|Maintenance Updates||Area of the release notes where we list the issues we've resolved in the major release, and information about each maintenance and daily update we make to the release.||See if we've resolved any issues you've reported to us through the Support Portal.|
We've reorganized our documentation based on app and license details to make it easier for you to understand what new features you can take immediate advantage of. We've applied this organization to both the New Features section and our core documentation.
|Platform||Practically every customer has the Coupa platform unless you've only bought certain stand-alone apps.||Not apps, but features like accounts, approvals, currencies, custom fields, notifications, reporting, and roles and permissions.|
|Core Applications||The primary parts of Coupa when you buy P2P or P2O, or a stand-alone Coupa application.||Procurement (including basic contracts, inventory, spot buy, etc.), Invoicing, Expenses, and some stand-alone apps.|
|Power Applications||Applications that you may have purchased as an add-on to a Coupa core application.||Add-on apps like Coupa Analytics, Coupa Contract Collaboration, Inventory, Coupa InvoiceSmash, Coupa Risk Aware, Services Maestro, Sourcing, Coupa Sourcing Optimization, and Supplier Management.|
|Early Access Program Apps & Features||New apps and features that are still in testing phase, and not yet available for most customers. See About Coupa's Early Access Program for more info.||Early Access Program apps change with each release. See the current list for details.|
Different sections of the release notes are formatted differently. Use this list of formats to understand how and why we've chosen to document things the way we do.
Upgrade Impact Assessment
When trying to understand the scope of the new release, start by checking out the impact each new feature has when you take the upgrade.
|Topic||The name and link to the article for the new feature in the New Features section.||Let me link out to in case I really want to see that feature documentation now.|
|Description||A high-level overview of what changed and why we changed it.||Give me a sense of what the feature's about. If I can understand it enough here, maybe I don't need to read that item in the New Features section.|
|Enabled||Indicates if the feature is turned on by default. It may still require configuration, but you don't need to reach out to Coupa in order to get it, assuming you have a license for the app.||Who do I need to talk to in order to get this feature in my Coupa instance?|
|Integrations||Indicate if there's any change to SFTP or API integration objects or behaviors.||Show me which features I need to pay attention to because they could potentially impact the integrations my Coupa instance has with my other systems.|
|Permissions||Indicate if we added or removed permissions, split up permissions, added new system roles, or made changes to existing system Coupa roles.||Show me which features introduced changes that might affect my custom roles and help me understand what new permissions affect what new features.|
A permission is a unique combination of a Controller/Action pair. We organize the new permissions by the controller name, and then show each of the new actions. and provide the details below. See Understanding Roles and Permissions for detailed info.
|Action||The specific action we added. For example, index, create, or show history.||Tell me what new actions were added.|
|Description||The description of what the action does or where it's applied||I need to know what the action does.|
|Associated permissions||Some actions only work in association with other actions. We'll try and suggest combinations that can achieve business outcomes. Unless otherwise stated, the action listed is part of the same controller.||What's the difference between index, and show, or create and new? Help me figure out how to build my custom role.|
|Migration||The existing permission that, if in a custom role, will cause the role to automatically receive the new action. Called Propagation in Release 19.||I need to know when you change what a permission does, and what new permissions received some of the functionality of the old permission.|
|Feature||The new feature where the change was introduced.||Show me what feature is associated with the new permissions so I can learn more about the change.|
New Features Topics
When we document a new feature, we want you to have an easy-to-follow format that helps you quickly understand the impact to your existing implementation, and decide how you'll address each new feature.
|Introduction||Gives you a high-level overview of what we've changed. Explains why we added the new feature, or made the change, with a particular focus on the problem we're trying to solve.||Let me quickly decide if I care about this feature.
After reading the introduction, I still can't decide if I care or not. Tell me why you made this change, and why I might care.
What problem is it trying to solve or what business benefit will this feature provide to me?
|How it works||Specific detail about what has changed, and what new business logic we've introduced into Coupa. The goal is not to explain every detail of how the features work or how to configure it, but instead to help you understand what it does and why.||
Okay, I’m interested. Tell me more about
Maybe I don’t need all the details right this second, but point me to where the details are.
Information about changes to roles and permissions, integration, and other system impacts. The goal is to give you a heads-up about changes that can impact you, even if you don't intend to implement or use the feature.
|Have you changed the system Coupa roles? What do I need to know from integration perspective if I want to use this feature or maintain my current functionality?|
|Availability||How does the customer get it? Does this feature need to be enabled by the Coupa Support team?||Alright, I'm sold! What do I need to do to start using this new feature? Am I already paying for it? Is it already enabled?|