In this article you will learn about the Oracle Self Service HRMS workflow, and how this Workflow fits into Self Service Human Resource architecture. This knowledge is required for any technical or functional HRMS person to troubleshoot the common issues that might get reported during Self Service HRMS implementation. First and foremost thing to remember is that a Workflow with item type named HRSSA is instantiated whenever a screen in Self Service HRMS is invoked. If you open this workflow in workflow builder, you will notice that there exists one single "Runnable Workflow Process" for each Employee Self Service HRMS AOL Function. Therefore, there is a direct connection between the AOL Function and HRSSA workflow. Given that the AOL Function is attached to a menu item in SSHR, therefore it is safe to say that there exists a relationship between SSHR menu item and a process within this workflow. Effectively whenever an employee opens a screen in Self Service HRMS it then creates a new instance of the workflow process.Infactthe name/path of theOAFramework page that gets opened is configured within the HRSSA workflow itself. By reading this article, you will be able to understand these relationships. However you must read the preceding articlelinked here, to understand the context of this article.
As seen in the previous article, the custom AOL function named XXapps2fusion_SIT_COMPL_FUNC instantiates a Workflow process named HR_SIT_JSP_PRC
The relationship between the AOL Function and HRSSA workflow is explained in the picture as shown below.
If you recollect, theWFProcess name entered in our AOL definition for function XXapps2fusion_SIT_COMPL_FUNC was HR_SIT_JSP_PRC
This matches the short name of theWFProcess "Change Special Information" as shown below
In the previous article you learnt the steps to create a self service HRMS data entry screen using Special Information Types, i.e SIT. This screens leveragesOAFramework, however this was achieved without writing any program.
It must be noted that the data entered in this screen is applied to the base tables directly. This is because, by default, the data entered in Special Information Types is not routed via AME Approval. It is important to understand the HRMS Self Service Workflow concepts before we take a dive into AME integration with Self Service HRMS.
Therefore in this article, we will concentrate on the integration ofSelf Service HRMS workflowwith overallSelf Service processes in Oracle HRMS. Understanding of this workflow and HR_API_TRANSACTIONS is apre-requisite before proceeding with AMEconfigfor SSHR.
I will try to address the following questions in this context
1. What is the purpose of this workflow in Self Service HRMS
2. How does this workflow dictate the navigation of the user to a specificOAFramework page.
3. How does this workflow control whether AME will be invoked
Firstly, what is the purpose of this workflow in Self Service HRMS ?
There is a historic reason for usage of Workflow named HRSSA in Self Service HRMS. Self Service HRMS product development was done slightly ahead ofOAFramework. In the early days of Self Service HRMS,OAFramework did not exist in its current form, and therefore PL/SQLweb Cartridges were used for developing the initial set of pages in SSHR. Thereafter AK Developer was used to configure the components of the pages in SSHR. However, Self Service HRMS team was looking for a framework that could give State Management for the data in Web Application.OAFramework was not quite ready by then, therefore Oracle Workflow was hooked onto the Self Service HRMS screens to manage user sessions. Given that workflow instance is persistent in the database tables, therefore the HRMS team was able to leverage thepersistencyoffered by Oracle Workflow for managing the state of Web Pages in Self Service HRMS.
Thepowerpointpresentationin this linkwill give you a good idea about howOAFramework evolved ineBusinessSuite.
These screenshots below are from HRSSA Workflow as opened from Workflow Builder, forWFProcess named "Change Special Information". ThisWFProcess was attached to the AOL function definition inprevious article[Part2]
If you double click on activity "SIT 4.0" in the workflow builder[shown in above picture] and navigate to Node Attributes tab[shown in image below], you will notice that this Workflow Activity calls aJSPpage. The page in reality is anOAFramework page. The mapping between the "jsppage name" and the actual "OAFramework page" exists in$PER_TOP/mds/regionMap.xml. regionMap.xmlis used to map the legacy[pre-OAF] page name with theOAFramework page name. This mapping file is loaded to theMDStables during the patching/installationprocess.
The image below shows the contents of $PER_TOP/mds/regionMap.xml. This file contains the mapping between the "JSP page name in WF Activity" and the OA Framework Page name.
In this article, you learnt how the workflow is integrated within SSHR.
In the next article, we will see the integration points of this Workflow with AME.
All content and images shown on this site is for demo, presentation purposes only. This site is intended to exemplify a live website and does not make any claim of any kind to the validity of non-Shape5 content, images or posts published.
Photography is used for this demo only, and is not included with this template or any membership. You may not use these images for your own without purchase. Links to purchase from their copyright owners will be provided.