Edit Subscriptions from Backoffice
Organization backoffice users can now modify active plans and add-ons directly from the subscription detail page of a Customer or Partner.
When a subscription is upgraded on behalf of the subscriber by adding a new add-on or switching to a higher plan, a Deferred Payment is automatically created. This ensures that no additional costs are charged to the subscriber without their consent. In the case of a downgrade, no payment record is created or modified. Optionally, the backoffice may mark the deferred payment as done; in this way, the upgrade is free of charge until the subscription's next renewal date.
In the Console, no additional configuration is required.
The Edit Subscription action is available in the backoffice view from the Customer or Partner subscription detail page.
Automations on update of Subscriptions or Payments
Two new automation trigger events are now available under General Automations, enabling integrations and workflows to react in real time to changes in Subscriptions and Payments:
On Subscription Updated: Triggered whenever a subscription is modified.
On Payment Updated: Triggered whenever a payment record is modified.
These automations can be used to forward complete subscription or payment details to external systems (e.g., ERP, billing platforms, CRM) upon a specific event.
T&C acceptance on digital service subscription
When an end user proceeds to checkout for a digital service subscription, any Terms & Conditions Agreements that require acceptance are now presented in a dedicated confirmation dialog before the payment is finalized.
The dialog displays a checkbox for each agreement that must be accepted, also including the link to view the full text.
Upon confirmation, the checkout continues as normal, and the acceptance date for each agreement is recorded.
In the Console, each User Agreement can be associated with digital service Plans or Add-ons.
Visibility conditions based on Root/Parent Thing properties
When defining Visibility Conditions in a template within the context of a Sub-Thing, it is now possible to access the properties of the Parent or Root Thing in the hierarchy.
This enables a more expressive and context-aware visibility rules definition for components that depend not only on the current Thing, but also on the parent device in a multi-level asset structure.
Two new utility functions are available in the visibility condition expressions:
getRootThing(): Returns the root Thing in the hierarchy.
getParentThing(): Returns the direct parent Thing.
Timezone based on GPS coordinates
The DPS can now automatically keep the Timezone of a Thing or Location updated based on its GPS coordinates, also in case the thing is moving or is reassigned to a different geographic area.
In the Console, you can enable whether the Timezone property must be automatically updated in case the GPS coordinates are changed.
Bug fixes (DPS)
Address autocompletion was not supported in the Billing Information confirmation dialog.
An error occurred while changing the “Display by” option in the Map widget with a selected area.