DLP Custom Field [sn_dlir_custom_field] - How do you find them to apply logic e.g. make mandatory
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2023 06:42 AM
I have added a new record in the Custom Field [sn_dlir_custom_field], a choice list, its visible and working ok
However I have now been asked to make it Mandatory, on closure of the DLP Incident when Members of a specific Group, close the DLP Incident
Can see the field I created on the 'Additional Details' form section in the DLP (Ops) Workspace, but unable to find the field / where the field is stored, to be able to apply logic to it
Any ideas very welcome?
- Labels:
-
Best Practices
-
DLP
-
Security Operations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 09:24 PM
Following as I am having similar issues
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2024 10:35 PM
Hi,
Actual field values are stored in table 'sn_dlir_custom_field_value' for custom fields. One simple way i can think of is to write an before Update BR on DLP incident table with conditions 'active' changes to false and check for the record in 'sn_dlir_custom_field_value' table and throw error message if record is not present.
Other way is to customise the UIB 'Additional Details 'page which is usually not recommended.
Feedback is noted and will be added in the product in upcoming releases.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2024 10:18 PM - edited 04-15-2024 10:30 PM
Hi @GG-Amitola ,
DLP Custom fields are more of like work notes for DLP analysts. Instead of having their notes as work notes and scrolling down in the activity section every time they have to look for that specific info, they can have it instead as custom fields which appear in the Additional Details tab in the form. This way, there's no need for scrolling down/up to search for it. Whenever you create a DLP custom field (to distinguish it from custom fields in the platform), you always have to make sure that the field will not be used for reporting purposes (they are not reportable) and that no logic will be applied to them. Otherwise, make them as custom field instead. So to answer your question, no you won't be able to make them mandatory nor apply logic into them