Last Plugin Update and Last Source File Match fields- meaning and use cases

This article explains two of the fields that are associated with every project inside the UI: Last Plugin Update and Last Source File Match Date. It further explains their role and examines which situations lead the value of these fields to remain unchanged.

These two fields can be found on each project’s main page, under the Project vitals section:

The role of the ‘Last Plugin Update’ and ‘Last Source File Match Date’ fields

Last Plugin Update: reflects the last time a project was updated using the Unified Agent.
Last Source File Match Date: reflects when the last time the project was scanned and the libraries were identified by matching source files into a source library.

The two fields are independent of each other, meaning that they can reflect different values after a scan.

Use-cases when ‘the Last Plugin Update’ and ‘Last Source File Match Date’ fields do not change their value

• The 'Last Plugin Update' field will not get updated if:

-the latest scan performed only checked the policies without updating the project ( checkPolicies= true, updateInventory=false)

• The 'Last Source File Match Date' will not get updated if:

-the latest scan did not include any different source files than the previous one (this means that no new source file matching has taken place since it was not necessary).

If the latest scan will present no changes from the previous one, then the project will not be updated inside the UI. In this case, the logs will print the message “No new projects found. No projects were updated.” and the two fields will suffer no changes inside the UI as well.