With  the latest release of Data Platform (version 5.5.45, available since the end of September 2021), we introduced the concept of standardized mashup which allows users to create a mashup data using "Simple" mashup process, all from within the interface of Admin Console. Please find all the details on this capability along with the instructions to create the mashup data using this new process in the attached document below. As usual, please reach out to us if you have any questions. ... View more

We released Inventory Normalization Statistics in IT Visibility last month (August 2021, see this blog post). On the software side, the statistics were available for Installer evidence only. There were placeholders for both “File evidence” and “Other evidence” on the Sankey diagram with zero counts. This month’s enhancement (September 2021) brings an improvement to the “Other evidence” by including the statistics for evidence used to recognize operating systems. Operating system recognition could come from OS-related WMI evidence, OS evidence from third-party discovery systems, and OS evidence from commands such as os-release on Linux, sw_vers on MacOS, and uname on other Unix systems. On the sample Sankey diagram above, "Other Evidence" is now showing the counts for these OS evidence (with the value of 1103). This number will also affect subsequent counts—Recognized and Unrecognized count as well as Consolidated, Duplicate and Irrelevant values—depending on the evidence. Active and Ignored counts would reflect the computer status returned with software (from Installer evidence) and operating systems (from Other evidence). Find further details in our online help reference (see Viewing Inventory Normalization Statistics). For more information on new features and enhancements for Flexera One, see What's New in Flexera One. ... View more

The latest monthly patch for Data Platform, 5.5.44, is available as of the end of August 2021. This release brings in several new capabilities, which includes: the ability to identify Technopedia entries that have been marked 'To be deleted' on User Console This will prevent users from selecting any of these 'To be deleted' entries and, instead, use the replacement entries that have been provided alongside. This also ensures consistency views of Technopedia across different consumption methods (Publish database, API, and now User Console). enhanced mapping cube in Analyze report Mapping cube will provide a better transparency into what Normalize is doing on the evidence/discovered data. Users can see all package and file entries that have been processed in Normalize (deduplicated or not, hidden or not) along with the normalization status (Mapped, Irrelevant, Unknown). For Mapped entries, the corresponding Technopedia products and/or releases will be shown side by side, so that users can use this infromation in any troubleshooting scenario. Finally, users can also identify which of those packages or files are part of their private catalog and/or mapping. This release also brings several fixes around extractors, correction of incorrect behaviors in Data Platform as well as User Console. Details on 5.5.44 (August 2021) release can be found in the release notes posted in the documentation section of Data Platform. ... View more

July 31, 2021 marked the first of our Data Platform's Q3 releases: version 5.5.43. This release brings several usability and product inconsistency improvements in User Console. One of them is the addition of 'To be deleted' dimension to Technopedia Software cubes which allows identification of Technopedia entries that have been marked 'To-be-deleted' (along with the reason for deletion, actual date of deletion, and replacement id). In absence of these fields, users might have falsely interpreted certain Technopedia software products and/or releases that look similar as 'duplicates,' furthermore risking them into choosing incorrect entries. Details on other fixes and enhancements, both on the Admin Console and User Console, can be found in the  release notes  posted in the  documentation section  of Data Platform.   ... View more

We're happy to announce that the latest monthly patch for Data Platform, 5.5.42, is immediately available as of the end of June, 2021. This release brings several bug fixes as well as usability improvements such as: improved performance of Normalize process during publish step, mapping step, as well as Search Index step consistency between User Console's Analyzer and Interactive reports to show SW Vuln Count and SW Threat Score fields fixes on several security issues around authentication cookie, HTTP header response, and loginuser storage Details on 5.5.42 (June 2021) release can be found in the  release notes  posted in the  documentation section  of Data Platform. ... View more

We're happy to announce that the latest version of ServiceNow Scoped App integration (v5.0.5) has passed certification and is now available in the ServiceNow Store. This release includes some notable changes, including: Improved transform map performance Resolved an ACL issue that may over-limit user access Updated virtual machine representation behavior Added the ability to cancel long running or stuck task with better job management Flexera Integration with Scoped App 5.0.5 is supported on the latest release of ServiceNow (Quebec) as well as the previous two releases (Paris and Orlando). It can be downloaded at ServiceNow's store at this link (or search using the keyword "Flexera" which will return the "Flexera Integration" app). Documentation can be found at this link (you can also find it in the Product Documentation section of the Community Portal). Please reach out to us if you have any further questions! Notes: first available on ServiceNow Store on June 17, 2021 ... View more

We're happy to announce that the latest version of ServiceNow Scoped App integration (v5.0.5) has passed certification and is now available in the ServiceNow Store. This release includes some notable changes, including: Improved transform map performance Resolved an ACL issue that may over-limit user access Updated virtual machine representation behavior Added the ability to cancel long running or stuck task with better job management Flexera Integration with Scoped App 5.0.5 is supported on the latest release of ServiceNow (Quebec) as well as the previous two releases (Paris and Orlando). It can be downloaded at ServiceNow's store at this link (or search using the keyword "Flexera" which will return the "Flexera Integration" app). Documentation can be found at this link (you can also find it in the Product Documentation section of the Community Portal). Please reach out to us if you have any further questions! Notes: first available on ServiceNow Store on June 17, 2021 ... View more

Change Title: Lifecycle Dates Exception to Change from "Exact date unknown: a date range is provided" to "Exact date unknown: based on a date range" Type: Class 2 Change Notification What: In Technopedia, when Flexera could not find an actual date (even after an extensive research), 'Not Available' string is populated along with specific reasons in the 'Exception' field (refer to this KB Article for detail). One of the exceptions is, Exact date unknown: a date range is provided. This exception value indicates that Exact support and/or lifecycle dates cannot be found, however, there is enough information to provide a potential period they may occur. A date range will be provided, the two dates which bookend the period (e.g. the dates of the immediate previous and subsequent releases). A translated date may be provided as well, where the lower date will be picked for any starting dates (e.g. General Availability Date, Introduction Date, etc.) and the upper date will be picked for any ending dates (e.g. End of Life Date, End of Support Date, etc.) We are planning to change this particular exception value to Exact date unknown: based on a date range. Why: The proposed change is intended to reduce confusion when a report is designed without the date range fields included. The resulting translated date provided in this scenario is still generated based on a certain date range. Therefore, for this exception value to make a better sense, the term a date range is provided is changed to based on a date range.   Potential Impact This change will have potential impact on Data Platform, IT Visibility and/or Technopedia users who rely on the exact string value of the lifecycle dates Exception field to drive their Technopedia integrations   When: The change will be implemented   within 2 (two) weeks ... View more

Change Title: Changes in Virtual Machine Normalization Type: Class 2 Change Notification What: Virtual machines come into normalization via hardware pipeline (along with, e.g., computers). Currently, they are normalized to Manufacturer-level only (i.e., no Technopedia product and/or model is specified). The proposed change is to normalize virtual machines to Technopedia hardware products and/or models under Computers – Virtual Machines category/subcategory. Why: The proposed change is intended to address: the need to clearly identify whether virtual machines are normalized or not—if normalized, they need to be associated with Technopedia product and categorization the need to have a single view of all inventoried devices, regardless of physical or virtual the need to capture additional details provided by the discovery source on virtual machines Current vs. Future Behavior: SCENARIO CURRENT BEHAVIOR FUTURE BEHAVIOR Normalization Normalized to manufacturer-only Normalized to hardware product and/or model Technopedia product/model None Representative hardware product and/or model for virtual machine Technopedia category/subcategory None Computers – Virtual Machines   Examples: Current Behavior on Virtual Machines Examples: Future Behavior on Virtual Machines Potential Impact These changes will have impact on IT Visibility, Data Platform and/or Technopedia users: who expect Technopedia manufacturer to be populated but Technopedia product and model to be empty for virtual machines who manage hardware products, as representative hardware products and/or models are being introduced with potentially blank values for hardware enrichment data (e.g., lifecycle dates, hardware specifications, etc.) who manage hardware taxonomy, as a new category/subcategory is being introduced: Computers – Virtual Machines When: The changes will be implemented within 2 (two) weeks Additional Notes Additional virtualization products and/or categorizations are proposed in the pipeline to distinguish desktop/server virtualization from other types of hardware virtualization: Storage virtualization: Storage – Virtual Storage Network virtualization: Network Equipment - Virtual Network Mainframe virtualization: Mainframe - Virtual Mainframe We are doing additional discovery work to get some sample evidence / discovered data which may fall under one of those virtualization types. At the conclusion of this discovery, we will provide an update to this Content Release Notification with the estimate before making the actual changes. ... View more