The properties of a network feature include its name, description, and priority. Network feature settings appear at the top of the network feature details page once a network feature is created.
| Setting | Description |
|---|---|
| Name | Limited to 32 characters. Names cannot be longer than 32 characters and can contain only letters, number, dashes, and underscores. |
| Feature Code | Must be unique. Consider carefully when creating a feature code. It is used throughout the subscriber provisioning system to identify the network feature and cannot be changed once you create the network feature. |
| Description | Optional. Gives more details about the network feature. A good description will explain what the network feature is intended to do. |
| Smart Services Enabled |
Determines when the network feature is enforced on devices.
This switch is only valid on tenants where subscribers could be managed by either the ItsOn charging system or the tenant's own charging system.
|
| Device users can enable/disable this feature | Determines whether you want embedded-client device users to have the ability to enable and disable the network feature. |
| Default user state |
Available when Device users can enable/disable this feature is enabled.
|
| UX Reference Code |
Defines the way embedded-client device users can enable and disable a network feature when they are allowed to do so. The 2 available options (wifi_auto_accept and connection_optimizer) represent the different options that users will see on their devices, but may not represent the functionality of the network feature that can be enabled/disabled. Using more than 2 UX Reference Codes is not supported within the ItsOn Smart Services software. The features that users can enable/disable cannot use the same UX Reference Code. If you require additional functionality, contact Technical Support.
|
| Priority |
Defines policy priority, which determines what policies take precedence over others. When a usage or other event occurs that matches multiple policies on a device, the priority setting determines which policy's policy event is enforced or which block or intercept notifications are triggered. Lower-priority policies are ignored for that event. When you assign a priority to a network feature, that priority becomes assigned to all policies within the network feature. If you want policies to have different priorities, put them in different network features. See Priority Scenarios for more information. |
| Created by | The user who created the network feature. |
| Created date | The date the network feature was created. |
| Status | Network feature status. Can be Draft, Test, or Published. |