You can configure the business rule logic for various modules and features using the Rules Engine.
Business rules can cover legal regulations ('The FLSA status is required for employees working in the USA'), company policies ('All employees moving to the London office get a compensation for the high cost of living'), or other requirements. Because of specific customer requirements, rules are highly customizable and based on the previous configuration decisions customers have made.
The Rules Engine provides an easy-to-use tool to dynamically configure and manage the customer, country, or scenario specific business logic that needs to occur within GO.
Users do not need to be technically savvy to create business rules.
The intuitive UI allows users to configure rule conditions that need to be checked in order to trigger the rule actions.
These rules can be updated easily to meet the needs of customer’s ever changing business scenarios.
Business Rules are defined in the Rules Engine and the system executes these rules during runtime. Technically, the Rules Engine is based on the Metadata Framework (MDF), but uses its own administrative tool, Configure Business Rules.
Rules can be used to add validation to details entered by a user or autofill some field data (for example, time zone information can be auto filled based on location information).
There are two ways to define rules:
Basic Rules (Not Recommended as it is error prone)
SuccessFactors defined scenarios (Recommended)
Business Rules could be attached to different events. These events include the following:
Initialize Rules: Initialization rules are triggered before all other rules; such rules are useful to autofill default values for different fields. They only run when a new record is created (initialized).
Validate Rules: Validate rules are triggered after a change to an object is submitted but before the change is saved. You can use these rules to validate field values entered by user. These are executed before Save Rules. When you import MDF data using the Import and Export Data UI, the validate operation triggers the validate rules associated with the MDF objects and returns errors found in the data. Administrators can then catch any data issues through validation and correct them before importing it. In fact, the validate rules are executed during both validate and import operations.
Save Rules: Save rules are triggered when a user saves changes. You can use these rules to populate or change field values before saving and they are based on user inputs values. For example, you want to auto populate region field based on country values selection.
Post Save Rules: Post Save rules are triggered after changes to an object have been saved. These rules are used when you want to send an alert message to the user. They are not used to set a field value.
Change Rules (onChange): They are used at the field level. Objects cannot be associated with change rules. Change rules are triggered when a value for a particular field is changed. You can use these rules to populate another field after the change. For example, you can populate the Country field with a certain value based on a change to the Position field.
Delete Rules: Deletion rules are triggered after an object record is deleted.
On Load Rules: On Load rules are UI specific rules that get executed once the UI is loaded. An example could be calculating total salary based on different fields available on given object.
UI Rules: These rules are applicable only for a UI built in the tool Configurable UI. These are UI specific rules to make certain field required, visible or hide based on certain condition. Such rules will not be applied when a user does the import.NoteWarning messages from the validate and save rules are shown before workflow confirmation messages from workflow rule execution.