Skip to Content

A diligently designed RCM-Onboarding implementation project comes to a grinding halt when the GO(Generic Object) type fields like Division, Department configured in job requisition template are incapable of being mapped directly from RCM to the Onboarding Module.

Well, here is a tried and tested remedy with tricks on how to go a step further in achieving it comprehensively. Lets take an example of three GO fields : Division, Department and Location

Steps to configure the workaround:

Firstly configure the GO fields in the Job requisition template and provide the relevant field permissions for visibility. Below is an excerpt of the field definitions of GO fields.

 

<field-definition id="division_obj" type="object" required="false" custom="false" object-type="Division">
  <field-label><![CDATA[Division]]></field-label>
  <field-label lang="de_DE"><![CDATA[Division]]></field-label>
  <field-description><![CDATA[Division]]></field-description>
      </field-definition>
  <field-definition id="department_obj" type="object" required="false" custom="false" object-type="Department">
  <field-label><![CDATA[Department]]></field-label>
  <field-label lang="de_DE"><![CDATA[Department]]></field-label>
  <field-description><![CDATA[Department]]></field-description>
    </field-definition>
  <field-definition id="location_obj" type="object" required="false" custom="false" object-type="location">
  <field-label><![CDATA[Location]]></field-label>
  <field-label lang="de_DE"><![CDATA[Location]]></field-label>
  <field-description><![CDATA[Location]]></field-description>
      </field-definition>

Now that you have configured the GO fields, you should be well aware that these fields cannot be directly mapped to Onboarding module, so we create three new custom text fields corresponding to our GO fields above.

Please note that these are custom text fields, you can have your own naming convention, not necessarily as shown below and they should not be included in any of the field-permission section

 

<field-definition id="division_onb" type="text" required="false" custom="true">
  <field-label><![CDATA[Division ONB]]></field-label>
  <field-label lang="de_DE"><![CDATA[Division ONB]]></field-label>
  <field-description><![CDATA[Division]]></field-description>
  </field-definition>
  <field-definition id="department_onb" type="text" required="false" custom="true">
  <field-label><![CDATA[Department ONB]]></field-label>
  <field-label lang="de_DE"><![CDATA[Department ONB]]></field-label>
  <field-description><![CDATA[Department]]></field-description>
  </field-definition>
  <field-definition id="location_onb" type="text" required="false" custom="true">
  <field-label><![CDATA[Location ONB]]></field-label>
  <field-label lang="de_DE"><![CDATA[Location ONB]]></field-label>
  <field-description><![CDATA[Location]]></field-description>
  </field-definition>

 

Our job with the templates is done and we now move on to a very important functionality called as

‘Configure Business Rules’

to create a rule to copy the values from the GO fields to the custom text fields. The rule will include methods to copy the values of the GO fields to the custom text fields and at a particular event. Lets start by creating a rule

Go to ‘Configure Business Rules’–> ‘Create New Rule’–> Choose ‘Basic’ option and mention any rule name, leave ‘Rule Type’ blank and choose Base Object as either your Job Requisition template name or ‘Job Requisition(All)’ if you want to apply this rule to all of your Job requisition templates in the system.

 

Since we have selected ‘Job Requisition’ as our base object it means we can manipulate the fields in the job requisition template using rules. Lets use the rules to set the values of GO fields in our corresponding custom text fields.

Please note that this rule is not based on any condition, hence we check the option ‘Always True’. This is because we have a RCM-ONB integrated system and would like this rule to work all the time on the job requisition.

Now ‘Set’ the custom text field values as the GO field default value as shown in the screenshot. Note that this will copy only the name of the GO field value and not the external code.

To copy the external code as well we will have to improvise the rule and configure it as shown. Use the Format() function to copy the name and external code and copy it to the custom text field.

 

Now that the rule is created, the next step is to associate the rule to your requisition template at a particular event.

Go to ‘Manage rules in Recruiting’ –> Select you Job Requisition template–> You will have to either save the rule on ‘onChange’ or ‘OnSave’ event. It is recommended to have it ‘onSave’ event and add the rule in ‘Save Rules’ section and save it.

 

Now we are done with configuration changes in template, creation of business rules and association of the rule to the job requisition template. The one last thing remaining is to map the RCM custom text fields in ‘Setup Onboarding Integration’ to Onboarding module fields.

 

The mapping of custom text fields in ‘Setup Onboarding Integration’ is the final step of achieving the workaround of indirect integration of GO fields from RCM to Onboarding.

 

The idea of a indirect work-around related to the mapping of Generic Objects (GO) stems from the fact that the GO fields cannot be directly mapped in ‘Setup Onboarding Integration’. Hence we copy the GO field values in custom text fields using rules, then associate the rule to the Job requisition template and then map the custom text fields with Onboarding fields. This indirect work-around has benefits of having the Foundation data of Employee Central at RCM’s disposal and indirect mapping to overcome the shortcomings of Onboarding module with respect to GO fields.

 

 

 

 

 

To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

  1. Shyamu Raja Murthy

    Very good, Husain. This situation should change once ONB 2.0 is released. Until then, this is a good way of meeting this requirement.

    In my experience, the most common feature requested for around suite integration is the ability to transfer background elements from RCM to ONB and finally to EC (Not EP). I hope something is done about that soon.

    Cheers,                                                                            Shyamu

    (1) 

Leave a Reply