SAP Knowledge Base Article - Public

2791863 - Q2 1905 Release - MDF and Business Rules related features and FAQ

Symptom

This Knowledge Base Article is to document all major enhancements that customers should be aware of in Q2 1905 release. Also provides one stop shop for all out MDF Framework and Rule related features and their details.

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

Environment

  • SAP SuccessFactors HCM Suite
  • Metadata frameowrk (MDF)

Reproducing the Issue

The documentation can also be found on the SAP Help Portal under SAP SuccessFactors Release Information, quick links under "What's New" section will provide the detailed release summary across application.

Important Links related to Q2 1905 documentation:

Release summary Information: Summary of All Product Features

Use cases for Q2 2019 SAP SuccessFactors features: Q2 2019 SAP SuccessFactors Testcases 

Q2 2019 SAP SuccessFactors: MDF Implementation Guide: Guide link

Resolution

Framework and Rules related Enhancements and Features:

Component Reference No. Feature Description Before Vs. After Additional Information
LOD-SF-MDF-RUL MDF-29519 Displayed wfconfig for Basic Rules In Q1 2019, 'wfConfig' was removed from Basic Rules Configuration UI. Although it was not an issue to execute rules with 'wfConfig', adding this to a rule was not possible. With Q2 2019, 'wfConfig' is made available in 'Basic Rules' based on MDF objects. However, SAP recommends you to use 'Rules for MDF Based Objects' or MDF Rules scenario for any Rules configuration for MDF objects.

Before: Prior to 1902, wfconfig was shown in Basic Rules.
In 1902, we implemented New Rules scenarios where the wfConfig property was not shown in Basic or New MDF Scenarios when creating a rule.

After: Starting from 1905
1.When creating or Editing Basic Rules for MDF Object, user should be able to see the wfconfig.

2.User should be able to set the wfconfig in Basic Rule and the Rule should be executed successfully.

3.When creating a new MDF Rule Scenario, the user should not be able to see wfconfig when creating/editing for any purpose except workflow.

2768151 - Triggering workflows on MDF object using Business rule.
LOD-SF-MDF-API MDF-28271 Supported navigation property for MDF user type audit field Previously, MDF OData API entities only contained two string-type properties for audit user fields createdBy and lastModifiedBy. Now we've added the corresponding navigation properties: createdByNav and lastModifiedByNav. You can use them to query the related user information of MDF entities. The new navigation properties are enabled for all MDF entities by default.

Before:For normal User type field, we already defined the navigation property linking to standard User entity.

For audit User type field "lastModifiedBy" and "createdBy", we only define the string property. No navigation property supported.

After: Expose navigation properties for two User type system fields - "lastModifiedBy" and "createdBy" in metadata for all entities by default.

https://help.sap.com/doc/f04408910b7a4e60bce0942cc2f2426d/1905/en-US/SAPSuccessFactorsQ22019TestCases.pdf
LOD-SF-MDF-RBP MDF-27940 Custom MDF objects will be RBP secured by default. SAP recommends that all MDF objects should be created as RBP secured. With Q2 2019, the default value for 'Secured' field is set to 'Yes' for all the custom objects. Secured is set to Yes for None, Basic, and Multiple Changes Per Day (MCPD) effective-dated objects and not for FROM_PARENT effective-dated object. If you try to change the value while creating or editing a custom object, a warning message is displayed asking you not to change the default value. As the new objects are RBP secured, you would also need to ensure that you grant necessary Role-based Permissions before you could access such custom object from Manage Data page.

Before: All the newly created custom MDF objects were by default Non- Secured. One had to explicitly make them secured by setting Secured = Yes in Security section of Object Definition.

After: Now whenever user makes a custom MDF object (excluding FROM_PARENT/ child object), the 'Secured' property by default will be set to Yes. So all the newly created custom MDF objects will be secured by default.

2794752 - Starting from b1905, custom MDF objects will be RBP secured by default.

LOD-SF-MDF-PKL MDF-27487 Large Picklist UI allows update of Header and Versions  It is possible to update the Picklist header information along with create or delete Picklist versions.

Before: For large picklists, we were not able to update the Header and the version from the UI. We used to do the updates by MDF Import, which was quite complex and chances of making a mistake were high.

After: Now, we will be able to update header info and also the picklist versions from the Picklist’s UI only.This will enable below capabilities for the large Picklists.

-Should be able to Insert new timeslice Picklist

-Should be able to Edit Picklist header

-Should be able to Delete a picklist timeslice.

2794750 - Q2 2019: How to update header and versions for the Large Picklist via the UI.

LOD-SF-MDF-XC MDF-26503 Improve Usability of Publish Extension UI on Extension Center  We have enhanced the Publish Extension popup dialog in the Extension Center to provide better user experience. Previously, when you published an extension, only Target Company and Target User fields were available and you had to type in the details, which was error prone. Now we've added Target Data Center and Target Instance fields. Together with Target Company, these three fields are available as dependent drop-down fields. You no longer have to type in the details except for Target User.

Before: While publishing an Extension on Extension Center, the fields like Target Data Center – dropdown, Target Environment and Target Company used to be text boxes.

After: Now, for better user experience, following fields are shown on publish extension center dialog like below:

Target Data Center – dropdown

Target Environment – dropdown

Target Company – dropdown

Target User - textbox

https://help.sap.com/doc/f04408910b7a4e60bce0942cc2f2426d/1905/en-US/SAPSuccessFactorsQ22019TestCases.pdf
LOD-SF-MDF-RBP MDF-27461 Updated the label for RBP permission One of the Role-based Permissions for Metadata Framework is renamed. Previously, the permission was named as 'Access to Non-RBP secured objects(Previously known as 'Read/Write Permission on Metadata Framework')'. In Q2 2019, the permission name is changed to 'Access to non-secured objects'.

Before: During b1902, we changed the RBP permission label and renamed it to "Access to Non-RBP secured objects (Previously known as 'Read/Write Permission on Metadata Framework')"

After: We are now removing the text in parantheis– (Previously known as 'Read/Write Permission on Metadata Framework)

The RBP permission now should be like “Access to non-secured objects” from 1905.

RBP.JPG
LOD-SF-MDF-RUL RUL-6159 Supported filtering of Rule functions You can now filter rule functions by entering a search term. For example, if you type "name", the list will be filtered to only display rule functions that contain that word.

Before: When typing an expression in the rule configuration, the matched keywords are highlighted. Currently, there is no filtering applied on functions based on the typed keyword.

After: We cannot filter the parameter section as we do not know all its child fields. However, we can filter the functions. E.g. when typing "name", the following functions will appear in the result:

Get Month Name()

Get Month Name short()

2794777 - Q2-2019: Filtering of Rule functions as per searched term.

LOD-SF-MDF-RUL RUL-392 Processing block before first condition/using variables in a rule We have enhanced the Rules Engine to allow you to create variables before configuring the rule details. A variable serves as a processing block before the first IF statement. You can store calculation results of complex or repeating tasks in a variable and call it in the IF and THEN statements. You can define any number of variables in a business rule. This helps to simplify rule definitions and improve the performance of rule execution.

Before: If an expression or function is to be used in rule multiple times, then it's better to define it as a variable and use this variable in the rule. Such operation was not available before 1905.

After: Now we have this feature where we can do the calculation in variable section. The result of the calculation shall be stored in a variable that can be used in further conditions (if/elseif/elseif)

https://help.sap.com/doc/f04408910b7a4e60bce0942cc2f2426d/1905/en-US/SAPSuccessFactorsQ22019TestCases.pdf
LOD-SF-MDF-RUL RUL-280 Provide possibility to go to application specific rule registration UI Previously, the rule assignment information provided only possibilities to view and change existing rule assignments. Now, you're able to see all possible assignment options and go to the target page to assign the rule. You can do this by clicking the rule assignment information icon and then the Assign Rule button on both the Business Rules Admin page and the Configure Business Rules page. Note that this functionality is only available if the rule is based on a rule scenario and the assignment link is provided by the target application.

Before: Users had no feature to navigate to application specific UI to register the rule or to verify/modify the registration of already registered rules.

After:Rule assignment information icons are available on the Business Rules Admin page and the rule detail page. You can click the icons to view where the rules are assigned, look at possible assignment options, and navigation to the target application to view, modify, and create new assignments.

https://help.sap.com/viewer/DRAFT/b37699fa8054409787a8321c9428aeca/1905/en-US/287c90b958994879b44d81c7ebddc92f.html
LOD-SF-MDF-RUL RUL-28 Rules Engine UI + Generic Check API should be able to detect fields that are read only Previously, the Rules Engine could not detect rules that set values to read-only fields. Now we have enhanced the Rules Engine so that it is able to detect such rules. When you open the rule, the read-only field is highlighted with an error message. This can help avoid setting unwanted values to read-only fields. Note that this only applies to system defined read-only fields, such as MDF Auto Number type fields. MDF fields that you define as read-only in Configure Object Definition are not affected.

Before: Rules Engine could not detect rules that set values to read-only system generated fields.

After:  If there is a system generated field set to read-only, it will not be possible to define a rule to set a value on such a field. Message will be like: Invalid: The field "..." is read-only and cannot be modified.

If such a rule is loaded in rules engine UI, there shall be checks to detect the issue and a message which informs the customer that he must correct the rule. The UI behavior will now render the corresponding field in red, possibility to delete the statement, save not allowed.

No use case available for this feature. Does not need to be tested by the customers. Hence test case also not provided in Q2 2019 SAP SuccessFactors Testcases 

Keywords

MDF-29519, MDF-28271, MDF-27940, MDF-27487, MDF-26503, MDF-27461, RUL-6159, RUL-392, RUL-280, RUL-28, 1905, Q2 2019, MDF features, MDF, Rule Engine, Q2 Release, 1905 Release, , KBA , LOD-SF-MDF , Metadata Framework , How To

Product

SAP SuccessFactors HCM Suite 1905