Hi @mrsahilmir1 ,
Hope you are doing well in your learning. Here is explanation of BR.
An Async Business Rule is a server-side script that runs in the background after a user saves, updates, or deletes a record. Because it runs asynchronously, it doesn't delay the user's interaction; they can continue working immediately after submitting the form. You should use an Async Business Rule for long-running operations that could negatively impact user experience if run in real-time.
Common use cases include:
Making API calls to external systems (e.g., creating a ticket in Jira).
Performing complex calculations or queries that involve many related records.
Generating non-critical related records that the user doesn't need to see right away.
- Sending an email.
A Display Business Rule is a server-side script that runs before a record's form is loaded and presented to a user. Its primary purpose is to pass information from the server to the client-side (the user's browser) for use in client scripts.
It's different from other business rules:
Timing: It's the only type that executes before the form is even loaded. Other types (Before, After, Async) run when a user tries to save or submit a form.
Purpose: Its main job isn't to modify the database record but to prepare data for the client. It uses a special global object called g_scratchpad to act as a bridge, sending server-side information to the client. This is far more efficient than using GlideAjax for information needed on form load, as it saves a server round-trip.
This is a perfect two-part job for a Display BR and a Client Script.
I would suggest try it on PDI, so that you can get better understanding. Check out this Post which explains step by step and executions.
Thanks,
Bhimashankar H
-------------------------------------------------------------------------------------------------
If my response points you in the right directions, please consider marking it as 'Helpful' & 'Correct'. Thanks!
