Find your people. Pick a challenge. Ship something real. The CreatorCon Hackathon is coming to the Community Pavilion for one epic night. Every skill level, every role welcome. Join us on May 5th and learn more here.

Scan Engine Properties are not working as expected

Lakshmi Naraga
Tera Contributor

There is an option in the Scan Engine properties called “Exclude Suggestion Finding.”
As per the documentation , when this option is enabled, real-time messages for Suggest level findings should not be displayed.
I tried it, but I believe its not working as expected. 

9 REPLIES 9

pr8172510
Giga Guru

Hi @Lakshmi Naraga,

the “Exclude Suggestion Finding” property does not always behave as strictly as the documentation suggests, especially in real-time scenarios.


🔹 Expected behavior (as per docs)

When enabled:

  • Suggestion level findings should be hidden in real-time
  • Only:
    • Review
    • Warning
    • Error
      should be visible

🔹 What actually happens (in practice)

Even after enabling:

  • Suggestion messages may still appear in some cases

This usually happens due to:


🔹 Possible reasons

1. Session caching issue

  • Property changes are not applied immediately
  • Try:
    • Logout/login
    • Clear cache (cache.do)

2. Real-time scan already initialized

  • If the editor session was already open:
    • Old scan behavior may persist

Open a new form/script editor session and test again


3. Not all suggestion messages are treated equally

  • Some “suggestions” may internally behave like:
    • Review-level findings
  • These can still appear depending on rule definition

4. Property scope limitation

  • This property only affects:
    Real-time scanning UI

It does NOT affect:

  • Background scans
  • On-demand scans
  • Existing findings already generated

5. Definition-level configuration

  • Some Scan Engine rules may override behavior
  • Suggestion-level classification can vary per definition

    🔹 Recommendation

    • Re-test after:
      • Cache clear
      • New session
    • Validate on fresh script changes only
    • Cross-check with Scan Engine Definitions for severity mapping

Lakshmi Naraga
Tera Contributor

 

Hi  pr8172510, 

 

Thanks for the response. I did try all the options and in multiple instances, but its the same case.

Just raise a case with SN. They need to fix it

Yes, i created. But its been a week. They are still analysing.