IXON Weekly update
- Week 05
- IXwebapp version: 2.13.0
- API version 0.1.86 (details)
What is the IXON weekly update?
The IXON Cloud and IXON’s API are updated weekly with bug fixes, changes to the platform, and new features. This weekly update informs you of everything that was added to, changed, and fixed in the IXON platform this week.
In this week’s release, we rolled out a couple new features and multiple fixes.
Features
- End users will now see a proper message in the portal when the API servers are unavailable with a link to the status page for further information.
- Furthermore, the sorting order in the card view will be now remembered between sessions.
Conditional alarm triggers
You are now able to use a variable to trigger an alarm when a dynamic threshold is reached.
What’s new?
- Instead of choosing a value threshold to trigger an alarm you can now choose between two threshold types. One threshold type is a value, like you used before, the new threshold type is a variable.
Why might it be valuable for you?
-
It is now possible to get an alarm notification when two variables are reaching each other’s intersection. This can be valuable when you are working with dynamic thresholds stored in one variable.
-
When you have one machine handling multiple types of materials and each type has its own temperature threshold stored in one variable, you can create an alarm trigger which sends a notification when the temperature threshold of materials X is reached.
Fixes
- Trial licence “unextendable”
- Float8 and Float16 selectable in data sources using floats
- Correct validation for ‘factor’ field of metric type component inputs
- Validation message for ‘decimals’ field of metric type component inputs
- Browser crash loading line-graph with no data
- Localization doesn’t affect logbook / cloud connection status date format