Following new features, enhancements, and significant changes have been introduced into Applixure products in this half of the ongoing year:
Applixure Analytics
Agent devices list's customisation is now available
In the Analytics' device listing view, each displayed row for the agent device previously contained a fixed set of fields from that device's data, namely a hostname, a device user (principal or last user), operating system name, installed memory and number of processors:
We have now enabled a possibility for users to customise agent fields that get shown for agents (as a per-user customisation) from a list of relevant data to display in the listing format. You can enter the customisation mode by clicking on the Customize list view... -link on the top-right of the device search results -list, and then dragging and dropping fields between seven available "slots" shown for the agent (hostname and device score are always shown) and the menu of all possible fields to shown above it:
Changes are saved automatically upon closing the customisation mode, or you can reset the shown fields back to the default layout. Once customised layout is in use, all agents in the listing are shown using the selected layout and you can also sort the results based on most of those fields:
New connectivity-related graphs in the Use dashboard
If your environment has connectivity data enabled – and optionally also an IP address reporting enabled in addition to that – Use dashboard now displays two new graphs related to detected connectivity data from your devices:
The first one shows a breakdown of devices with detected VPN connections within the past seven days and devices with no active VPN connections within that period. The second graph, provided that IP address detection is enabled, shows a breakdown of the IP addresses configured for devices: dynamic, static (fixed) or mixed.
Internet browsers' add-on software inventory is now available
We have added support to both Windows and macOS Analytics Agents to inventory installed browser add-ons from the most used and popular browsers available for those platforms. Currently supported browsers are Chrome and other common Chrome-derived browsers (Edge, Brave, Opera, Vivaldi), Firefox, and Safari as a macOS-specific browser.
As the number of software products reported in the Software dashboard for an environment can grow significantly after enabling add-on inventorying, and for some customers, getting information about add-ons installed by the end-users themselves into their browser might introduce privacy implications, this feature has to be separately enabled for each Applixure Environment. Please consider this feature as a beta at this time of release since some inaccuracies can still occur with the inventoried data, given that the add-on data has to be parsed by the Agent from the browsers themselves. You can enable this feature from the Environment's overall settings, under "Optional components & features":
Once enabled, it might take a while before receiving the add-ons as part of the software inventory from devices. Software products classified as add-ons as deployment type will show the hosting applications (i.e. the browser) and their enablement status (except for Safari where presently it will always show as enabled) inside the browser when viewing at the specific product version level:
Please note that since Applixure Analytics is unable to monitor issues or usage with add-ons as they are executed inside the browser itself, no usage information is calculated or shown for the software with add-on as deployment type, nor is any software score calculated for them.
Okta is now supported as Single Sign-On (SSO) provider
We have added support for using Okta as an SSO identity provider (IdP) with Applixure user logins. You can now connect your Applixure Account or Environment to your Okta organisation and set user accounts to perform login using Okta, using official Applixure OIDC integration published in Okta's OIN catalogue.
To read more about enabling SSO with Okta for your Applixure Account or Environment users, please refer to our overall SSO configuration article and the configuration article for the Okta integration.
Device and software tagging have been improved
You can now see and edit (if granted sufficient user permissions for the Applixure Environment) tags for agent devices and software directly on top of the detail page for both. Previously, asset-specific tags were displayed and edited in a separate section at the bottom of the asset details page, while the newly introduced layout brings better visibility and visual indicators for the assigned tags.
By pressing "Edit device tags" or "Edit software tags" you can open up in-place editor to pick already-existing tags to assign for the device or software, remove already-assigned tags, or to create a new one by writing its contents and selecting the appropriate type (or group) for the newly created tag.
Custom information / attributes are now available for agent devices
It is now possible to enter some custom information for the devices similar to the software products. You can record an organisation-specific asset tag or ID of the device and a purchase date for it. Since the purchase date is typed as date data, it can be used in a device search for filtering using functions such as YEAR() or MONTH(). The custom information for agent devices is available on the device details page, in the right-hand side data section.
You can also assign these two custom attributes to multiple agent devices at once using the import functionality of the Analytics. Please refer to our Helpcenter article on mass import for more information.
Applixure Workflow
Added a flag for invalid board-level data filter
If you have defined a manual filtering string for the board-level data filter, Workflow will notify you if the entered filtering string is syntactically invalid. This notification will be displayed below the data filter after it has been processed by the Workflow's backend and thus won't immediately be validated and visible after saving the data filter for the board.
If the filtering syntax is invalid, no filtering will be in effect at the board level – before any rule-based filtering – until the filter string is fixed. You can refer to the search syntax article in our Helpcenter to review syntactic requirements for the filtering string – or alternatively, switch to building a data filter using a graphical builder, which will always result in a valid filter. Saving or making any changes to the data filter will cause a re-evaluation of the board-level filter.
Applixure Feedback
0 Comments