SUBSCRIPTIONS | |||||||||||
Issue Key | Summary | Description | Issue Type | Release | |||||||
V5-1399 | Subscription Self-Service Web APIs | Subscription Self-Service Web APIs | Improvement | 5.4.1.0 | |||||||
V5-1271 | Subscription & Billing Settings UI Enhancements | Subscription & Billing Settings UI Enhancements | Improvement | 5.4.0.0 | |||||||
V5-1267 | Product Catalogue Process enhancements | Enhancements required in setting up and using the product catalogue for termed and one-time services | Improvement | 5.4.0.0 | |||||||
V5-1266 | Product Catalogue UI enhancements | Product Catalogue enhancements related to service products sold as part of a subscription. Enhancements include changes in configuring the setting of the product catalogue (e.g. tier paths) as well as setting up the catalogue as such | Improvement | 5.4.0.0 | |||||||
V5-371 | Change Ownership | Ability to change the owner of subscription services by:
| Story | Candidate Features | V5-370 | Provisioning of Subscription Services | Provisioning of Subscription Services
| Story | Candidate Features | ||
V5-369 | Apply Grace Period | Ability to provide a grace period to subscribers to pay off their outstanding billing debts | Story | Candidate Features | |||||||
V5-366 | Service Delivery | Service Delivery is the process responsible for managing subscriptions throughout their life cycle by combining the subscriptions and billing business rules with a customer's service purchases and requests for changes. In summary, the process is responsible.
| Story | 5.4.1.0 | |||||||
V5-365 | Billing Behaviour | Billing Behaviour
| Story | 5.4.3.0 | |||||||
V5-364 | Trial Periods | Trial Periods allow contacts to try out a service for a short period of time with no billing or contract obligations before turning the service into a paid one. The trial period of a service is defined in its pricing terms. Automated communications are sent to contacts prior to their trial ends through Communication Plans Segments of contacts in the trial can also facilitate running marketing campaigns to minimise cancellations. | Story | 5.4.3.0 | |||||||
V5-361 | Manage Subscription Services | Provide the ability to purchase termed and one-time services through a product catalogue and manage their core behaviour throughout their life cycle through various subscription actions:
| Story | 5.4.0.0 | |||||||
V5-360 | Manage Subscriptions | Create a Subscription that groups together services of the same billing period. A subscription is created only when a termed service is purchased through an Order. Manage the subscription throughout its life cycle through various subscription actions which are performed per service:
| Story | ||||||||
V5-1973 | Promotions for Subscriptions | Improvements in Promotions so as to be applied to on selling subscription services | Improvement | 5.4.5.0 | |||||||
V5-2218 | Improved Subscriptions Self-service Web APIs | Product pricing for self-service in order to implement ordering of services on the Release app. | Improvement | 5.4.5.2 | |||||||
V5-2126 | Ability to specify the Wallet as the funding source of a subscription | The Wallet is used as the method of paying off subscription services | Improvement | 5.4.4.1 | |||||||
V5-1598 | Subscription services webhooks: On activate and on deactivate | New webhooks: | Improvement | 5.4.4.0 | |||||||
V5-367 | Subscription Devices | Ability to utilise Devices that will provision (i.e. deliver) a number of subscription services to subscribers
| Story | 5.4.4.0 | |||||||
V5-2346 | Enhanced billing and disconnection of wallet-funded services | Differentiation of billing behaviour between account and wallet-funded services. | Improvement | 5.4.5.3 | |||||||
V5-2055 | Ability to send provisioning commands to a group of devices | Ability to send provisioning commands to a group of devices:
| Improvement | 5.4.4.1 | |||||||
V5-368 | Usage Based Billing | Ability to order termed or one-time services that allow usage consumption | Story | 5.4.6.0 | |||||||
V5-1959 | Payment-driven subscriptions | Payment-driven subscriptions | Improvement | 5.4.6.0 | |||||||
V5-2353 | Ability to support WIFI platforms for subscriptions and billing | Core APIs created Support the device MAC address as contact authentication Enhance the organisation UI to provide usage analytics for WIFI | New Feature | 5.4.6.0 | |||||||
V5-2433 | The ability for an organisation to purchase one-time/termed services | The ability for an organisation to purchase one-time/termed services
| Improvement | 5.4.6.0 | |||||||
V5-2433 | The ability for an organisation to purchase one-time/termed services | The ability for an organisation to purchase one-time/termed services Only merchants/service providers can perform the purchase using their accounts 1959 | Payment-driven subscriptions | Implementation of payment-driven subscriptions | Improvement | 5.4.6.1 | |||||
V5-1959 | Payment-driven subscriptions | Implementation of payment-driven subscriptions | Improvement | 5.4.6.1 | V5-368 | Usage Based Billing | Ability 368 | Usage Based Billing | Ability to order termed or one-time services that allow usage consumption | Story | 5.4.6.1 |
V5-2616 | Improved Provisioning Provider Filtering | Available filters:
Content views to be included also | Improvement | 5.4.6.2 | |||||||
V5-2542 | Enhanced Subscription Promotions | 1 ) Ability to apply the discount
3 ) Advanced Subscription Promotions
| Improvement | 5.4.6.3 | |||||||
V5-2846 | Ability to call Provisioning Provider Integration Web APIs for services | Ability to call Provisioning Provider Integration Web APIs for services | Improvement | 5.4.6.3 | |||||||
V5-2797 | Ability to group one-time services in a subscription | Ability to group one-time services in a subscription
| Improvement | 5.4.6.3 | |||||||
V5-2764 | Ability to deactivate/reactivate services based on an amount threshold | Introduction of a new Subscription business rule called the Activation rule. The rule determines whether a service can remain in the Effective state or can move into the Effective state as long as the account's outstanding amount meets an activation threshold. A service is a candidate for deactivation when its account has an outstanding amount (unsettled and overdue), and this amount is greater than the threshold amount. The threshold defaults to 0 amount (set in the business's base currency) | Improvement | 5.4.6.3 | |||||||
V5-2760 | Ability to view a service's allowed and remaining usage allowance | Ability to view a service's allowance, i.e. how much usage a contact is allowed to consume in general based on what the product catalogue specifies, as well as the remaining of this usage per transaction, day and billing cycle In addition, present the recorded usage records of a subscription | Improvement | 5.4.6.3 | |||||||
V5-1964 | Implementation of service bundles | Implementation of service bundles | Task | 5.4.6.3 | |||||||
V5-2797 | Grouping of one-time services in a subscription | Ability to group one-time services in a subscription
| Improvement | 5.4.6.4 | |||||||
V5-2779 | Ability to set up business rules for Pausing a service | Ability to set up and apply business rules for Pausing a service
| Improvement | 5.4.6.4 | |||||||
V5-2834 | Enhanced usage consumption based on the usage being consumed | Enhanced usage consumption based on the usage being consumed
| Improvement2779 | Ability to set up business rules for Pausing a service | Ability to set up and apply business rules for Pausing a service
| Improvement | 5.4.6.4 | ||||
V5-2834 | Enhanced usage consumption based on the usage being consumed | Enhanced usage consumption based on the usage being consumed
| Improvement | 5.5.0.0 | |||||||
V5-2811 | Event-based Recurring Charges | Event-based recurring charges are a set of policies triggered on various subscription events that identify if and which Expenses will be applied on a subscription and will be charged on a recurring basis, i.e. per subscriber billing cycle. Recurring charges policies include two major events - the event that will add the recurring expense to the subscription and the event that will remove it. | New Feature | 5.5.0.0 | |||||||
V5-28112773 | Enhanced Event-based Recurring ChargesExpenses | Enhanced Event-based recurring charges are a set of policies triggered on various subscription events that identify if and which Expenses will be applied on a subscription and will be charged on a recurring basis, i.e. per subscriber billing cycle. Recurring charges policies include two major events - the event that will add the recurring expense to the subscription and the event that will remove it.New Featurebased Expenses
| Improvement | 5.5.0.0 | |||||||
V5-2773 | Enhanced Event-based Conditional Expenses | Enhanced Event-based Conditional Expenses
| Improvement | 5.5.0.0 | V5-1838 | Enhancements in Pause Services action | Enhancements in Pause Services action Ability1838 | Enhancements in Pause Services action | Enhancements in Pause Services action
| Task | 5.5.0.0 |
V5-2717 | Enhanced service change process | A service change can be classified as an upgrade or a downgrade. What classifies the service change is either:
| Improvement | 5.5.1.0 | |||||||
V5-3253 | Ability to manage devices for a Company | Ability to create a subscription (through an Order) for a contact of type 'Company' and be able to view and modify the DEVICES. Flow should be the same as for Contact of type' Person.' | Improvement | 5.5.1.0 | |||||||
V5-3224 | Include service locations in Invoice communications | On sending a communication for an Invoice that bills termed services, provide the ability to also display the services' locations | Improvement | 5.5.1.0 | |||||||
V5-3084 | Automation to automatically activate a service when settled |
| Improvement | 5.5.1.0 | |||||||
V5-2778 | Communication Tags and Subscriptions Segmentation & Automation Enhancements | Ability to segment contacts based on subscription services conditions and trigger Automation based on new subscription events | Improvement | 5.5.1.0 | |||||||
V5-3110 | Ability to bill upcoming billing cycles in advance | Ability to bill upcoming billing cycles in advance
| New Feature | 5.5.2.0 | |||||||
V5-3084 | Automation to automatically activate a service when settled |
| Improvement | 5.5.2.0 | |||||||
V5-3423 | Ability to send service commands to a Provisioning Provider through the front-end | Ability to send service commands to a Provisioning Provider through the front end. New Self-service Web APIs allow consumers to send provisioning commands for their services to the provisioning provider | Improvement | 5.5.2.3 | |||||||
V5-3427 | The billing engine issues a single financial transaction according to the total billed amount | The billing engine issues a single financial transaction according to the total billed amount | Improvement | 5.5.3.0 | |||||||
V5-3335 | Product Dependencies are to be applied across all contact services, not per subscription. | Product Dependencies are to be applied across all contact services, not per subscription. | Improvement | 5.5.3.0 | |||||||
V5-3287 | Ability to hide Churned subscriptions in the Contacts screen | Ability to filter the subscriptions based on their state | Improvement | 5.5.3.0 | |||||||
V5-3161 | Enhanced listing of subscription actions to present additional information | Enhanced listing of subscription actions to present additional information
| Improvement | 5.5.3.0 | |||||||
V5-369 | Apply Grace Period | Ability to provide a grace period to subscribers to pay off their outstanding billing debts
| Story | 5.5.3.0 | |||||||
V5-2713 | Ability to regret a service | Provide the ability to regret a subscription service
| New Feature | 5.5.3.2 | |||||||
V5-3495 | Ability to set up billable and non-creditable states per service | Ability to set up additional billable and/or non-creditable states for specific services | Improvement | 5.5.3.3 | |||||||
V5-2729 | Enhanced Trial Management | Trial Management rules define whether a contact gets a Trial service once (amongst all subscription services) upon subscribing to the first service that includes a Trial period in its price terms or a trial period for each service to which they subscribe. | Improvement | 5.5.3.3 | |||||||
V5-3687 | Improvements in resetting a Subscription's Billing Day | Business rules included in Subscription Settings define when the Billing day is reset on a Subscription | Improvement | 5.5.3.4 | |||||||
V5-3838 | Ability to view and manage future Subscriptions | Contacts are able to order services and schedule their first activation on a future date. Provide the ability to view and manage these services prior to their activation
| Improvement | 5.5.3.5 | |||||||
V5-4027 | Ability to add multiple services within the UI | Ability to add multiple services from the back-end
Supported both adding a service to the Contact and to a subscription. | Improvement | 5.5.4.1 | |||||||
V5-4247 | Ability to communicate a subscriber's upcoming bill | Introduce a new communication tag that returns a contact's upcoming bill. The tag will be used in communication plan templates. The communication plan runs on a daily basis and notifies contacts whose upcoming bill is due in an X number of days. | Improvement | ||||||||
V5-4180 | Ability to set up Usage Charge Limits and Usage Allowance settings per Contact | Ability to set up Usage Allowance Limits and Usage Charge Limits per Contact that override the business's default business rules when it comes to these settings | New Feature | 5.6.0.0 | |||||||
V5-3854 | Ability to extend a service's trial period | Ability to extend a service's trial period | New Feature | 5.6.0.0 | |||||||
V5-4469 | Enhanced Period billing in Calendar Billing | Ability to define a specific day of month and a month of a year when services' billing model is set to Period Billing. This option is applied only for services with billing cycle longer than a year. Ability to define a day of week on which services with billing cycles shorter than a week will be billed. | Improvement | 5.6.0.2 | |||||||
-4647 | Enhanced UI/UX when changing a service, managing subscription actions |
| Improvement | 5.6.0.4 | |||||||
V5-4646 | Ability to send payment intents during the billing run process to settle outstanding amounts | Ability to send payment intents during the billing run process to settle outstanding amounts. This feature ensures that any outstanding subscriber amounts will still be settled during the billing run process, even if their credit limit is not exceeded. | Improvement | 5.6.0.4 | |||||||
V5-4404 | Ability to set up Usage Allowance settings per contact | Ability to set up Usage Allowance Limits per contact, that override the business's default rules when it comes to these settings | Improvement | 5.6.0.4 | |||||||
V5-4696 | Enhanced traceability of subscription actions related to devices |
| Improvement | 5.6.0.5 | |||||||
V5-4870 | Enhanced billing rules on payment intents amount to collect | During billing run process, on posting an invoice if credit limit exceeded then collect the whole invoice amount. If invoice does not exceed the credit limit, then just post it, with no payments. Automated, recurring process responsible for collecting the outstanding amount of a subscriber. Process to automatically retry to collect the outstanding amount for 10 days, as a result subscription’s deactivation due to outstanding debt is prevented for 10 days. | Improvement | 5.6.0.6 | |||||||
V5-4707 | Ability to apply event-based charges with a calculated charge amount | Ability to apply event-based charges with a calculated charge amount. The amount of the charge is calculated based on a period of time. | Improvement | 5.6.0.6 | |||||||
V5-4757 | Ability to define a device's conditional access ID | Ability to define whether a device’s conditional access identifier (CAID) is its serial number or its electronic ID. This configuration must be set on integrator’s integration settings and managed accordingly when forwarding commands to the provider. | Improvement | 5.6.0.6, even if their credit limit is not exceeded. | Improvement | 5.6.0.4 | |||||
V5-4404 | Ability to set up Usage Allowance settings per contact | Ability to set up Usage Allowance Limits per contact, that override the business's default rules when it comes to these settings | Improvement | 5.6.0.4 | |||||||
V5-4696 | Enhanced traceability of subscription actions related to devices |
| Improvement | 5.6.0.5 | |||||||
V5-4870 | Enhanced billing rules on payment intents amount to collect | During billing run process, on posting an invoice if credit limit exceeded then collect the whole invoice amount. If invoice does not exceed the credit limit, then just post it, with no payments. Automated, recurring process responsible for collecting the outstanding amount of a subscriber. Process to automatically retry to collect the outstanding amount for 10 days, as a result subscription’s deactivation due to outstanding debt is prevented for 10 days. | Improvement | 5.6.0.6 | |||||||
V5-4707 | Ability to apply event-based charges with a calculated charge amount | Ability to apply event-based charges with a calculated charge amount. The amount of the charge is calculated based on a period of time. | Improvement | 5.6.0.6 | |||||||
V5-4757 | Ability to define a device's conditional access ID | Ability to define whether a device’s conditional access identifier (CAID) is its serial number or its electronic ID. This configuration must be set on integrator’s integration settings and managed accordingly when forwarding commands to the provider. | Improvement | 5.6.0.6 | |||||||
V5-4977 | Improved UI/UX when managing a SaaS Subscription |
| Improvement | 5.6.8.0 | |||||||
V5-5074 | Enhanced Anniversary billing behaviour when subscriber opts-in to a billing day | Enhanced Anniversary billing behaviour when subscriber opts in to a specific billing day. Once subscriber opts in to a specific day, then Calendar billing rules are not applied for the subscription and therefore, billing day is not reset on various events. Applicable only for Anniversary models. | Improvement | 5.7.0.0 | |||||||
V5-5465 | Maintain subscriptions based on services' billing model | Ability to maintain subscriptions in order to group contact services based on their billing model; pre-bill and post-bill | Improvement | 5.7.1.1 | |||||||
V5-5952 | The ability for a community owner to share a usage allowance with all community members |
| Improvement | 5.7.2.5 | |||||||
V5-5880 | Ability to easily set up a member's allowance based on the owner's service usage allowance | Ability to easily set up a member's allowance based on the owner's service usage allowance. Instead of adding each individual product allowance per member, simply enable Usage Allowance for a community member and then specify that the member has the same usage allowance as the community owner’s service allowance. | Improvement | 5.7.2.5 | |||||||
V5-5873 | Ability to perform preview billing in trial services | Ability to perform preview billing in trial services. Bill preview returns the expected date that the service will be billed and how much it will be billed (event-based/recurring charges also included). While in trial, though, the service cannot be billed in advance. | Improvement | 5.7.2.5 | |||||||
V5-5868 | Enhanced Bill Preview information per subscription | Enhanced Bill Preview features:
| Improvement | 5.7.2.5 |
Page Comparison
General
Content
Integrations