You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The text was updated successfully, but these errors were encountered:
RomuDeuxfois
added
bug
use for describing something not working as expected
needs triage
use to identify issue needing triage from Filigran Product team
labels
Jan 29, 2025
@EllynBsc This was done on purpose at the code level.
Do we confirm that the UI should tell what we must save? If there are no expectations, then we don't create them by default? Today, we create technical expectations by default if if it's empty.
By default we always provide detection and prevention to technical injects
If the user wants to remove it via the UI he should be able to have the option.
By default we always provide detection and prevention to technical injects If the user wants to remove it via the UI he should be able to have the option.
Is this logic blocking us in some way ?
Not all
Actual logic:
User create a technical inject with expectations -> we create expectations provided by the user
User create a technical inject without expectations -> we create prevention & detection expectations by default
User update a technical inject by removing expectations -> OK
New logic:
User create a technical inject with expectations -> we create expectations provided by the user
User create a technical inject without expectations -> we don't create expectations by default
User update a technical inject by removing expectations -> OK
Description
The text was updated successfully, but these errors were encountered: