How to use SAP's metadata framework (MDF) to build custom business rules?

SAP SuccessFactors Using metadata framework （MDF） Objects and business rules do a lot of things . Business rules apply to many different situations , And there are a lot of documents about how to use them . Unfortunately , There is a clear lack of guidelines for customized solutions .

If an enterprise must use several connected business rules , How do they achieve their desired behavior from these rules ？

It is sad , The business rules have not been explained very clearly , This makes those enterprises who want to implement customized solutions feel that they must find out the truth through experiments . We will introduce how enterprises use MDF Some basic knowledge that you need to know when customizing solutions for business rules of objects .

 

Switch the scene context to “ be based on MDF The rules of the object ”

The basic scenario is not based on MDF Designed for the object of , So scenario “ be based on MDF The rules of the object ” It is more suitable for what we are trying to do . It provides many benefits for enterprises , These include ：

• Completely built into the expansion center
• Only functions suitable for specific purposes are covered
• Allows you to navigate from a business rule to the event that invokes it

Whenever an enterprise intends to use MDF Object time , Suggest they use these “ be based on MDF The rules of the object ”, Because this scenario is user-friendly and reliable .

 

Create new rules

Creating a new custom rule will display the fields that need to be edited to complete the rule settings .

 

The rules ID

Editable only if no object is selected .ID crucial , Because it is the way we import and export business rules and their allocation to object definitions . The rule name should contain the fixed facts about the rule , for example ：

• Abbreviation of implementation project
• Basic object code
• The purpose of the rule
• Save the code type of the business rule

therefore , for example , Effective rules ID It may be similar to COMPANY_Position_externalCode_Evaluate.

Rule name

The rule name can be changed at any time . Rule name and rule ID Always visible when represented in the configuration tool . Because the rule name is in the system UI Is visible and modifiable , So it is an ideal place to store variable data about rules . Projects such as ：

• Such as “ Be deleted ” or “ Be replaced ” Something like that .
• Any event that invokes the rule
• The order in which rules are executed
• The previous rule ID（ If there is a predecessor rule of this rule ）
• Variable IF Conditions and which fields to change .

Assign event sequence

In any event , The business rules added to the event are executed in the order of addition . Usually , If the rules are independent , This will not cause any problems . however , Some rules require the results of previous rules . In these cases , The order of execution is critical to ensure that there is no interruption . Linking rules together is not uncommon , But some configurations often happen more than others . When configuring these chains ,OnLoad- and Initialize-Purposed The rules can be complicated . supplier - Consumer chains should avoid implementing such chains .Evaluate-Purposed Rules often appear in consumers - In the supplier chain , And apply to OnChange and Save event .

Unfortunately , Workflow specific rules do not respect the allocation order in the object definition . They have a fixed position in the event . stay Sve Incident , First, execute workflow specific rules . On the delete event , Workflow specific rules run after everything else .

 

Sequencing events

Events are sorted according to the actions that occur on the object .

 

Tips for writing business rules

that , What should enterprises pay attention to when formulating custom business rules ？

• Business rules should be as simple as possible （KISS principle ）
• If there are complex conditions （IF sentence ）, They should be simplified as much as possible
• Avoid using logical combinations for a large number of parameters （AND sentence ）
• First of all, the most likely situation should be explained
• Any use of double counting or “ Magic ” All numerical things should be replaced by variables
• Business rules should never replace Association and field Standards .

At first glance , Building custom business rules can seem complicated . however , Once one understands how the backend is done , It is easier to master how to write successful rules . They should have a thoughtful name and ID, So that anyone who uses it can clearly describe the rules . They should also be as simple as possible , But don't be so simple as to accomplish nothing . It takes some practice to find a balance in formulating these rules , But it is worth having a leaner system to deal with complex conditions that may affect business efficiency and production .