The lifecycles for software models are not displayed correctly on the Technology Portfolio Management (TPM) DashboardIssue There is a requirement for the APM dashboard to capture the application software with the software lifecycle without having to match the full version but instead, the closest version in order to have the lifecycle info displayed. Currently, the only way to change the software model discovery is to map it with a full version lifecycle record in order to make the info display on the dashboard. This is not feasible when hundreds and thousands of applications might need to be updated manually.ReleaseSan Diego and TokyoResolutionTPM fix Overview This TPM fix brings the following enhancements: The retrieval of product lifecycles from ServiceNow Software Asset Management (SAM) by adding heuristics to find the best matching lifecycles for a discovered software model version. This will result in TPM reporting a larger number of software model lifecycle dates to enhance TPM lifecycle risk assessment.A script to get an audit report of TPM lifecycle matching. This will enable you to perform an audit on the heuristics applied by SAM to match lifecycles.A minor TPM UI fix Details SAM Matching Algorithm Using the full software model version, the SAM lifecycle version matching algorithm is enhanced to find a matching lifecycle at a higher version level, by gradually trimming the version from the right, up until a match is found, e.g., it will stop at the major version level. If a match is found, the lifecycles for that model version are returned to TPM. If no match is found, no lifecycle is returned to TPM. Audit Script The audit script can be run on-demand to populate the table sn_apm_tpm_audit_data. Note: The table must be created manually before installing the update set. See installation instructions below. Note: See the installation instructions to run the script. The script will generate the list of products whose lifecycles were not an exact match as reported from the Software Asset Management (SAM) Content library. The table columns are: u_software_model - Reference to the software modelu_status - Type of lifecycle algorithm applied to match a product lifecycle from the Content library to the discovered software model version. The values are: No Match (value: no_matched): The product version does not exist because the product was not discovered correctlyMulti-matched (value: multi_matched): Multiple matching lifecycle versions were found in the Content libraryNo Lifecycle (value: no_lifecycle): No lifecycle could be found in the Content library. This entry should be automatically submitted to the ServiceNow SAM Content team if the Opt in option is enabled as defined here. If the Opt-in version is not enabled, you will need to work with your Support team to manually submit the list of software models with no lifecycles to the SAM Content team. u_full_version (String) - Version of the discovered running product for which lifecycles must be associated to.u_all_versions (String) – All model versions for the software model which are available in the SAM Content libraryu_all_lifecycle_versions (String) – All lifecycle versions for the software model which are available in the SAM Content library Supported Releases San Diego: SD-APM-TPM-SAM-UpdateSet.zipTokyo: Tokyo-APM-TPM-SAM-UpdateSet.zip Installation instructions Requirements: SAM Pro Ensure the SAM Pro plugin (sn_samp) is installed. Set the scope: Application Portfolio ManagementCreate the table Create the table sn_apm_tpm_audit_data Columns Controls Extensible: NoLive feed: NoAuto-number: NoUser role: sn_apm.apm_admin Application Access Use defaults Unzip the update set zip file for your platform version. It contains 2 XML update set files. Import both files.Run the script whenever needed. To run the script, you need to run the 'APM Reconciliation Job' on-demand background job. Note: Before you run the script a second time, you will need to first clear the table.