You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/vendor/licenses-about.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ When you make changes to a license in the Vendor Portal, the customer does not n
55
55
56
56
### License Updates with KOTS
57
57
58
-
When you edit customer licenses for an application installed with KOTS, your customers can use the KOTS Admin Console to sync their license with the latest from the Vendor Portal, then deploy a new version that includes the license changes. Deploying a new version with the license changes ensures that any license fields that you have templated in your release are rendered with the latest license details from the Vendor Portal.
58
+
When you edit customer licenses for an application installed with KOTS, your customers can use the KOTS Admin Console to sync their license with the latest from the Vendor Portal, then deploy a new version that includes the license changes. Deploying a new version with the license changes ensures that any license fields that you have templated in your release using [KOTS template functions](/reference/template-functions-about)are rendered with the latest license details from the Vendor Portal.
59
59
60
60
For online instances, license updates are pulled from the Vendor Portal when:
61
61
* An automatic or manual update check is performed by KOTS.
0 commit comments