Technology portfolio audit in Enterprise Architecture workspace.

[sonali panda1]

Hi,

We're currently working with the Technology Portfolio Management module within ServiceNow's Enterprise Architecture workspace, and I have a question regarding the "Verified" and "Rejected" statuses available when managing the records in Technology Portfolio Audit.

Could someone clarify:

What are the functional and downstream implications of marking an entry as "Verified" or "Rejected"?

Does this status influence application lifecycle decisions, technology standards, or portfolio compliance reporting?

Are there best practices or out-of-the-box workflows tied to these markings?

Any insights, documentation links, or real-world implementation experiences would be greatly appreciated.

Thanks in advance!

[sonali panda1]

@Namita Mishra @yogesh41  Can you help me here ?

[yogesh41]

Hi,

Here is the document article that explains the origin of Technology Portfolio Audit logs, its attribute details as well as what is expected when the user update `Verification status` choice value. 

Managing requests, certifications, and assessments

Update verification status

Any exception identified during `Populate TPM Discovered Technologies and Lifecycles` phase appears as Audit logs, such as miss match in exact version, missing information etc. once the concern person review audit log status and update `Verification status`, it impacts TPM records as explained doc.

Yogesh

[sonali panda1]

@yogesh41  Thank you for your response. I want to understand what is the implication of selecting rejected or verified. Does it do anything in SN? Or from process standpoint something should be done? Can you help me with this?

[yogesh41]

Hi,

Whenever  Verification Status of Technology Audit log record ( sn_apm_tpm_technology_lifecycle_exception)  gets updated, it runs below logic

• If the verification_status of the current record is "rejected":
  • It updates technology lifecycle reference on the current (sn_apm_tpm_technology_lifecycle_exception) record and clears the corresponding date fields (eos_date, eoes_date, eol_date) in the technology lifecycle record.
  • It also clears the match_status and match_notes fields.
• If the verification_status is not "approved":
  • It sets the corresponding date fields in the technology lifecycle record to the start_date from the current record based on the lifecycle_phase.

• Updating Exception Count:
  • The script updates the match_exceptions field in the technology lifecycle record with the count of exceptions found earlier.

You can review update BR on sn_apm_tpm_technology_lifecycle_exception table to get more details. 

Yogesh