🐱💻 In development
Tiering was already supported via Transformers but we aim to extend support for Standard and Inherited tiering using simplified deployment model, which would enable administrators to use the Rates UI interface for adding new tiers.
Service oriented architecture
Moving towards a service oriented architecture using RabbitMQ
Administrator managed notifications
Administrators can manage users notifications in the user manager
Attachments with workflow notifications
Ability to include files as attachments with a workflow notification (i.e. for exception handling)
Support sending out notifications when a budget threshold is met
Cost summary report notification
The ability of a user to receive a cost summary report
Data aware report filters
Making the report filters more intelligent to avoid selecting filters that do not apply to the report data
Highly available scheduler
Rewrite of the scheduler to support the new message bus architecture and add the ability to run on multiple nodes at the same time
Webhook notification channel
A new webhook notification channel. When used will post a JSON payload to a custom webhook URL.
Improved error reporting
Add more error codes to workflows, to support different status and support to ability to continue depending on the severity of the error
Unified Consumption Report
We will integrate the existing Accounts, Services and Instances reports into a single report while maintaining all existing drill-down and filtering capabilities. This will improve the overall user experience when using the reporting functionality in the GUI.
Full support for running the entire Exivity stack on Linux platform
Event state management
Functionality to produce usage data from consumption start/stop/update events, including the consumption which spans several days.
Custom Attributes for SAML2
Currently, a single SAML2 attribute (email) is used and linked to an Exivity account. This feature will enable administrators to customize the SAML2 attributes that are being used for populating Exivity user names, e-mail addresses, and display names.
Claims-based account access provisioning
The ability to automatically map SAML2 users to relevant accounts in Exivity, based on SAML2 response key/values
Ordering of adjustments
At this time, Adjustments are applied in the order of which they are created. We aim to add support for users to re-arrange the order of Adjusments, such that the order of how Adjustments are applied is controllable.
Extended support for translating the Exivity user interface to custom languages
Service subscription management
The ability to manage contracts and subscriptions for recurring charges without a defined and/or usage based data source
The ability to manage meta data with services in similar way how this is done currently with Accounts
The ability to manage variables independently of scripts to make it easier to transfer Extractor and Transformer scripts between various different systems such as in a DTAP street
Management of Budgets on a per customer / account level