1 Answer

With the creation of the custom process in SF-Onboarding, you should also identify your use case for the custom process i.e what field you will use to trigger the process. Refer the Onboarding guide section: "How to Import a New Hire to a Custom Process" with steps to add this field.

In your scenario, if the customer is using a crossboarding for internal hires, use the below sample code in your new hire XML.

Sample code:

<xsl:when test="./ID='InternalHire'">

<xsl:if test="./Value = 'false'">

<xsl:call-template name="item">

<xsl:with-param name="key">Process</xsl:with-param>

<xsl:with-param name="value">Onboarding</xsl:with-param>

</xsl:call-template>

</xsl:if>

<xsl:if test="./Value = 'true'">

<xsl:call-template name="item">

<xsl:with-param name="key">Process</xsl:with-param>

<xsl:with-param name="value">CustomProcess (enter the name of the process that you have created)</xsl:with-param>

Thanks for the clarification, like you, mentioned in your answer - I'm already using a field in requisition 'Onboarding type' to filter the process for the other four processes I have, but for Crossboarding do I need to use the same field in requisition by adding some picklist values (or) I can create another field, lets say internal hire=yes/no. so that I can use that field to add it in the same code you have sent. In this case, there will be first field filtering all the processes and second to filter for Crossboarding....Is it possible?

Please look at the code I have used - could you please tell if this is right? Thanks in advance