Hi @VISWANATH KAMAL ,
Hope You are doing great.
To troubleshoot try following below steps to check the issue:
Verify that the abort action is properly implemented within the Business rule. The abort action should be triggered based on the specific conditions that indicate the entry should not be created in the table.
Check the sequence of the Business rule within the system. If there are multiple Business rules operating on the same table, ensure that the abort action is placed before any other rules that might override it. The order of execution is crucial in ServiceNow.
If you have confirmed that the abort action is correctly implemented and the sequence of rules is appropriate, consider examining the differences between the portal and native UI submission processes. Look for any specific events or functions triggered during the submission process that might affect the creation of the entry.
Utilize client-side scripting or UI policies to enforce additional validation rules on the native UI submission form. By adding these validations, you can prevent the submission of the form if certain conditions are not met, thus avoiding the creation of the entry in the table.
if this doesn't work , please share confguration built to look into it.
Please mark the appropriate response as correct answer and helpful, This may help other community users to follow correct solution.
Regards,
Riya Verma
