Exam CSA topic 1 question 98 discussion

A. UI action - not applicable B. Table - mandatory C. Fields to update - important settings under ACTION tab. This is the purpose we creating business rule D. Who can run - optional - WHEN-TO-RUN tab -> role conditions E. Script to run - optional - advanced scenarios only - script box F. Application scope - auto fill G. Update set - not applicable H. Timing - WHEN-TO-RUN tab I. Condition to evaluate - optional - advanced scenarios only - script box A, G - not applicable B, C, D, H - required E, I - advanced scenarios F - auto fill except A, G, all is valid B,C,D,H is generally required

Answer is "BEHI" according to the updated San Diego ServiceNow Learning platform

Straight from the SNAF Course / Book: Every business rule includes: 1) what table to run against = B TABLE 2) timing (before or after insert) = H TIMING 3) what conditions to evaluate = I CONDITION TO EVALUATE 4) what script to run based on the evaluation = E SCRIPT TO RUN Answer is: BEHI

H. Timing - I don't thik this mean When to run

I went to dev instance, picked "UI Action", "New record". I needed to update table, script to run, application scope, condition to evaluate

eBook chapter 7.1 - script tipes: business rules quote: Every Business Rule includes what table to run against and timing (before or affer insert and more), what conditions to evaluate, and what script to run based on the evaluation.

A. UI action - NA B. Table - m]Mandatory C. Fields to update - Important settings under ACTION tab. This is the purpose we creating business rule D. Who can run - optional - WHEN-TO-RUN tab -> role conditions E. Script to run - optional - advanced scenarios only - script box F. Application scope - Auto Fill G. Update set - NA H. Timing - WHEN-TO-RUN tab I. Condition to evaluate - optional - advanced scenarios only - script box

I have written detailed explanations many times, wont submit??? but the answer is B...the table the rule works on F is always set and not optional G is alwasy set and not optional, even though its outside of the context of a BR H only for options, no None value, so again is ALways set All the rest are optional fact, try it...these are the only fields that are either always sate with something or optional. simple as that

BEHI. When creating a business rule, the following four things need to be specified: Table: The table that the business rule will apply to. Timing: When the business rule will run. Condition: The condition that must be met for the business rule to run. Script: The script that will be run when the business rule runs.

https://docs.servicenow.com/bundle/washingtondc-build-workflows/page/script/business-rules/concept/c_BusinessRules.html#t_CreatingABusinessRule

I was just re-reading the SN Administration Fundamentals - Vancouver and I came upon this info: Every business rule includes what TABLE to run against and WHEN to run (BEFORE a database actions, AFTER a databse action, ASYNC (QUEUED), DISPLAY before the record is displayed) what CONDITIONS to evaluate and what SCRIPT to run based on the evaluation. Based on this I would definitely vote for BEHI

Everyone has to approve that table and application needs to be part of created BR. On the other hand you should not be a snow employee ... Now, if "timing" means a summary for insert, update, delete, query, ... then h) is correct too. Imo, condition and scripting and fields to update are not necessary. They are just an option how BR could be created. So conclusion is : B) F) H) and the fourth option choose among condition, scripting or fields

Straight from Fundamentals: Every Business Rule includes what table to run against and timing (before or after insert and more), what conditions to evaluate, and what script to run based on the evaluation.

Table: You need to specify the table on which the Business Rule will be triggered. The Business Rule will apply to records in this table when certain conditions are met. When to run: You have to specify the conditions that trigger the Business Rule. This includes defining the events that will cause the Business Rule to run, such as on insert, update, delete, or when a condition is met. Advanced conditions (Script): You can write a script to define additional conditions that must be met for the Business Rule to execute. This script can be written using the ServiceNow scripting language (e.g., GlideRecord queries, JavaScript) to add complex logic to the Business Rule. Actions: You need to specify what actions the Business Rule should perform when triggered. These actions can include setting field values, adding comments, sending notifications, or invoking other scripts or workflows.

BEHI Table Timing Condition Script

This should explain it: https://docs.servicenow.com/en-US/bundle/utah-employee-service-management/page/product/universal-request/task/ur-create-busrule-service.html

Business rules include: table, timing, what condition to evaluate, what script to run.