Update Set Scan Best Practises

[akbalFTV]

I am trying to implement the Update Set Scan as a pre-requisite for release process before moving an update set across instances. I have a couple of questions around that.

1. The Scan runs fine and gives findings as expected. But I’m struggling to understand how to use these effectively. In the below example, it has 2 findings and if I go to the Results Dashboard in the Related Links, it shows the latest scan findings but only d where we can see all the scan findings and their nature. The OOB dashboard ‘Instance Scan Results’ does not have any data.
   
   
   
   
   
2. What are the best practices for using this in multiple instances and how are others using this? We would like to track the scans and findings in Production but our development process would need these to be run in Dev before moving the update sets to another instance to mitigate the scan findings. The scan findings in Dev would eventually be scrapped off after periodic clone from prod. Do you suggest we run the scan again in Production before committing update sets?

Thanks,

Akshatha

[Idea Igniter]

Hi @Mark Roethof , I meant only for the update set scan, not instance scan in general. You can run instance scan in your production or sub-production instances.

[Mark Roethof]

@Idea Igniter just checking, because I think its a best practice to use instance scan in every instance 😁 Ofcourse with care when developing the scan checks.

[Idea Igniter]

Yes, absolutely. 

[jeffreyluto]

So what does "Scan" do that preview does not?

Or what does it do specifically?