Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Subscription Management release notes

Log in to subscribe to topics and get notified when content changes.

Subscription Management release notes

ServiceNow® Subscription Management application enhancements and updates in the Helsinki release.

Activation information

Active by default.

New in the Helsinki release

Subscription enforcement for ServiceNow Store apps
By default, the system monitors and reports on usage of subscription applications and suites but does not block users who are not subscribed. If a developer enables subscription enforcement for a ServiceNow Store app, then users who are not subscribed are blocked from performing fulfiller actions in the app.
Flexible method for allocating users to per-user subscriptions: User sets
In earlier releases, you allocated users either by role or by group. The method could become complex and is no longer used. In this release, you can allocate users using either or both of the following methods:
  • Allocate users individually.
  • Add user sets to the subscription. A user set is a pool of users that you define. For example, all fulfiller users from the IT department. When you add a user set to a subscription for a ServiceNow application or application suite, all users in the set are subscribed.
After you allocate users to the subscription, you can add or remove user sets and individual users as needed. In addition, you can exclude an individual user to ensure that the user is not subscribed.

If you allocated users to a subscription in an earlier release, the subscribed users are auto-migrated to new user sets.

Overview of the auto-migration process

Note: This section applies only if you used the Subscription Management application in an earlier release.
Because the application now manages allocation to subscriptions with user sets instead of roles and groups, the system auto-migrates subscribed users from earlier releases into user sets. The system performs the following process when you upgrade:
  1. Create a user set for each role that contained the subscription role. Use the following Name for each user set: Users with roles that contained <RoleName> subscription role
  2. Create a user set for each group that contained the subscription role. Use the following Name for each user set: Users in groups that contained <GroupName> subscription role
  3. Add the new user sets to the appropriate subscription.
  4. If any users are set to the Pending state, allocate the users individually.
  5. Activate the Auto-sync user sets option for the subscription to periodically update all user sets to reflect updates in users and groups.