Our team is pleased to announce the general availability of SLASCONE 7.0, highlighting the following features:
- Metering Scenarios
- Pure metering scenarios (in which there is no actual limitation) have been integrated in the existing consumption heartbeat logic. This does not only allow a simpler implementation of such models, but also seamlessly switching from pure metering to capped and vice versa.
- Constrained Variables and Custom Lists
- Constrained variables, as their name implies analogous to variables, constitute a new license property. The distinction resides in the fact that while variables can receive any value, constrained variables can only receive values from predetermined custom lists, enabling more bullet-proof workflows.
- Read more.
- Email Branding
- All emails (e.g., invitation email, welcome email) can now be customized in order to reflect your company’s brand. This is particularly important for reseller and customer scenarios.
- Read more.
- Portal User Delete (AD B2C)
- Until now, deleting a user removed it from the SLASCONE database, but not from the underlying AD B2C. With 7.0, after deleting the user from the SLASCONE database, you can optionally delete it from AD B2C as well, thus facilitating GDPR compliance.
- Read More.
- Data/Heartbeat Archiving Options
- Contrary to many similar systems, SLASCONE’s heartbeats, are retained indefinitely. Depending on the data volume, this can obviously lead to data explosion, particularly in the context of usage heartbeats. You can now optionally:
- Aggregate older license heartbeats.
- Delete older analytical and usage heartbeats.
- A nightly job aggregates/deletes data that is older than X months. You can set the number of months.
- Read more.
- Contrary to many similar systems, SLASCONE’s heartbeats, are retained indefinitely. Depending on the data volume, this can obviously lead to data explosion, particularly in the context of usage heartbeats. You can now optionally:
- Remote Activation
- It is now possible to remotely activate a client from the SLASCONE Portal. Until now, activation could be only performed through the API. This facilitates:
- Pre-activation of clients before shipping (hardware scenarios).
- Development/Testing scenarios.
- It is now possible to remotely activate a client from the SLASCONE Portal. Until now, activation could be only performed through the API. This facilitates:
- Strict Heartbeats
- Until now, heartbeats for non-compliant (e.g., expired or inactive) licenses, returned a 200 success code, containing the non-compliant information in the response body. Strict heartbeats return a 409 conflict code for non-compliant licenses.
- This facilitates workflows in low-code platforms, such as Logic Apps, Power Automate, Zapier.
- This behavior is optional, thus existing workflows are not affected.
- UI/UX Improvements
- Performance: Issues affecting licenses with a very high number of tokens or users are resolved.
- Development System Label: To make it easier for users to distinguish between development and production, development environments are now clearly labeled.
- Resizing/Layout: Several issues affecting in smaller screen sizes (e.g., in tablets) are resolved.
Register to our Argus Demo Vendor now in order to experience SLASCONE 7.0 live or schedule an online demo.