2646360 - [MDF] The behavior of effectiveStartDate field in custom MDF objects.

• The label set for the field effectiveStartDate does not appear on the PP3 (People Profile Page)/ UI.

• The label set in the UI screen for effectiveStartDate field does not take effect on the Profile.

• The field effectiveStartDate has been removed/hidden from the Object/ UI but is still being displayed on the Profile.

• Changing effeciveStartDate using business rule.
• Difference between mdfSystemeffectiveStartDate and effectiveStartDate field.

• SAP SuccessFactors HXM Suite

• Metadata frameowrk (MDF)

1) Create a effective dated custom MDF object. Also create a UI screen for that object.

  2) Configure that UI screen in PP3 as a Live Profile MDF Information portlet.

  3) Update the label of the field "effectiveStartDate" in the Object or in the UI.

  4) The field on the top still shows the label as "When would you like your changes to take effect?"

  The label of the field effectiveStartDate is hard coded and cannot be changed on MDF portlet on PP3.

The label of this field cannot be overridden over the PP3 portlet. No matter what label is configured in the UI screen or on the object definition, this field's label will always appear like: "When would you like your changes to take effect?" in PP3.

Important points to Note:

1) This field is only relevant to effective dated objects. If an object has effective Dating = None, then this field is obviously not usable. Due to this any rule on the effectiveStarteDate field (onChange rule) will not trigger for non-effective dated objects. There is no concept of historical records for such objects.

2) For effective dated MDF objects, this field is mandatory and hence it should not be set to Not Visible Or Read Only. Also, it is recommended not to secure this field using field level override either.

3) This field should not be removed from the object defintion. If you attemot to remove the field effectiveStartDate from an effectiveDated object, system automatically adds it back with name "mdfSystemeffectiveStartDate".

4) Fields "mdfSystemEffectiveStartDate" and "effectiveStartDate" are both the same. The difference in the NAME comes from the fact whether or not if the object was an effectiveDated object from the very begining. (when it was created):-

1. => If the object was created as an effective Dated object (Basic) at the time of creation - Then the field name is effectiveStartDate.
   
2. => If the object was created as non-effective Dated object (None) at the time of creation) - Then the field name is mdfSystemeffectiveStartDate.

5) A composite child object inherits the effectiveStartDate properties from parent object only. 

3202427 - Changing the value of effectiveStartDate field in an MDF object using Save rule.

Metadata Framework, mdfSystemeffectiveStartDate, effectiveStartDate, label, PP3, MDF, MDF UI, business rules, save rule, effective start date, , KBA , LOD-SF-MDF-UI , UI Config, Layout & Rules , LOD-SF-MDF-OBJ , Object Definition & Field Related Issues , Problem