A new Flexera Community experience is coming on November 25th. Click here for more information.
Change Title |
Automatic process to create the next/later versions in Technopedia |
Class 2 |
Customers should be prepared and take actions |
Change Summary |
What? Flexera has been working on an automatic process to create releases for the next/later versions of an existing product in Technopedia to allow for immediate recognition without having to go through the coverage enhancement (aka gap-fill) process. The probabilistic nature of this capability takes into consideration all prior/existing recognition rules and mappings as well as patterns of existing versions already in Technopedia. Why? This process will help us in identifying the potential new versions which leads into creation of new releases faster. Customer can get the benefit of immediate recognition for the submitted discovered/evidence data. Next Steps: Through the new mechanism we have identified around 4,600+ potential new releases that will be created in Technopedia. releases will be added to Technopedia (according to the scheduled implementation below), however, they will initially miss some details like lifecycle dates (General Availability, End of Life, or Obsolete dates). Further curation will be done to complete those missing details soon after. Here’s the plan on how these changes will be implemented: · Approximately 500 new releases will be created in Technopedia each week · These newly created releases will show the lifecycle date values (General Availability, End of Life, or Obsolete dates) as “Not available” with the Exception fields showing “To be curated” · Within a week or two, these releases will be reviewed and further curated with the correct values (upon which the “To be curated” exception will either be removed or replaced with more appropriate values) · Customers can expect approximately 1,000 release updates every week (500 new releases and updates for previously created 500 releases). See the schedule below:
|
||
Impact |
Going forward, this will be a regular activity. Customers can expect approximately 1,000 release updates every week (500 new releases and updates for previously created 500 releases). These newly added releases will have incomplete lifecycle date dates (General Availability, End of Life, or Obsolete dates) for a duration no longer that two weeks after their creation. The spreadsheet List of potential new releases.xlsx provides the complete list of potential new releases. |
||
When |
Customers should expect these changes to occur starting from April 17t onward (according to the schedule above) |