What needs to be specified, when creating a Business Rule? (Choose four.)
What needs to be specified, when creating a Business Rule? (Choose four.)
ABEF
Reference:
https://docs.servicenow.com/bundle/rome-platform-administration/page/administer/list-administration/task/t_EditingAUIAction.html
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
Thanks! Well explained. The answers are so ambiguous!
C is not required. A script can set the value. I believe that they are saying, a script is need to update the value and that the script is your custom or ootb script when you click of fields to update.
Answer is "BEHI" according to the updated San Diego ServiceNow Learning platform
How can this be when the script is optional.
Taken straight from the training: 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.
Page 438. from the ServiceNow Administration Fundamentals - Tokyo training booklet. States Table, Timing, Conditions, and script.
ChatGPT: When creating a Business Rule in ServiceNow, the following needs to be specified: Table - The table on which the Business Rule will be executed. This is the table where the data is stored and where the Business Rule will trigger when a specific action is performed. When to run - This is the condition that will trigger the Business Rule. It specifies when the Business Rule will execute, such as before or after a record is inserted, updated, or deleted. Condition - This specifies the conditions that need to be met before the Business Rule will execute. This is an optional field, but it is useful when you want to limit the Business Rule to a specific subset of data. Script - This is the script that defines the logic for the Business Rule. It is written in JavaScript and can be used to manipulate data, validate user input, or perform other tasks.
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.
https://docs.servicenow.com/bundle/quebec-application-development/page/script/business-rules/task/t_CreatingABusinessRule.html
When creating a Business Rule, the following items need to be specified: B. Table: The table to which the business rule applies. E. Script to run: The script that the business rule runs when triggered. H. Timing: The point at which the business rule runs (before or after the database action occurs). I. Condition to evaluate: The condition that must be true for the business rule to run.
Business rules include: table, timing, what condition to evaluate, what script to run.
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
BEHI Table Timing Condition Script
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.
B, H, I and 'Specify field values using the Set field values choice lists:' C. The script is optional and hidden unless you checked the 'advanced' checkbox.
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.
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
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
https://docs.servicenow.com/bundle/washingtondc-build-workflows/page/script/business-rules/concept/c_BusinessRules.html#t_CreatingABusinessRule
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
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