- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2021 08:00 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2021 08:08 PM
OnAfter - It is almost similar to an onAfter business rule and you could use it to write any businss logic to be executed on other related tables. For eg when transforming users, you can add users to group or users with roles in an on After script.
OnComplete - Once the entire list of rows are transformed, the onComplete script is triggerred. You could acccess the entire import set in here and process any required logic on the entire rows imported. Since transform map executes row by row, you cannot apply a logic if first row is dependent on the last row and similar logic can be accomplished using it. It can also be used for adding logs or triggering any emails after transform.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-04-2025 02:00 PM
I have a usecase where in I am trying to create vulnerable item records via api and for every row transformation a detection record is created for which the logic is set in OnAfter script. What do you suggest in this case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2025 12:01 AM
@Neha8. in your case, you must use 'onAfter' script to create a detection record. The 'onAfter' script will first query the detection table, which will typically have two columns (a) Detected Vulnerability sys_id and (b) Scan Description (eg: June 2025 Internal Scan). If the query (based on these two parameters) returns false, insert a record.