Oracle iRecruitment integrates with Oracle HRMS to manage the entire workforce lifecycle.It automates every phase of the recruitment process.Most of the companies have their Recruitment solution.Now in most of the iRecruitment implementation we need to do the migration of Resume files from already existing system to newly configured (may be from iRecruitment perspective) oracle iRecruitment system.Here we will only discuss about how we can migrate resume from existing system to our oracle system.
Here we have considered that reader has a basic knowledge on Oracle iRecruitment functionality and aware of terminology(candidate,applicant,vacancy etc..).
Basic Requirement
Our basic requirement is to migrate Resume files and make it available through iRecruitment.
Pre-Requisite
Following are the pre-requisites for Resume migration
1) iRecruitment system is configured
2) Candidate and/or Applicant are already migrated and present in the system.
3) Resume files are already transfered from older system to our oracle database server(say database server path:- /usr/tmp ).The path may differ in your case.
4) The candidate/applicant resume mapping file(file that contains the candidate/applicant necessary details(any unique identifier) and corresponding file name. The mapping file is loaded in our migration stagging table.
To read the full document go to Shareapps4u
Oracle Workflow also provide us a provision to launch Oracle form/s from a notification.It helps the performer to see the details that is stored in core HR without explicitly login into system from another session.
We are now quite familiar with oracle workflow and already developed some of simple workflows. Now we will discuss here how can we give the user a provision to open a form from notification itself.
Basic Requirement
Our old requirement looks like "
when a person applies for a leave it should go his/her supervisor for approval.Approver must be able to provide his/her approval/rejection comments. The comments must be entered by the approver while rejecting the leave requisition.If he/she rejects the leave requisition without entering comments, then it should raise an application error.If he/she approves the requisition it should be optional.Approver must also be able to select the Organization Leave Type from a list of values . If the leave gets rejected, don’t store any information in database."
In addition to the above requirement:- The approver should able to view/edit the person "Special Information Types" before approving the leave request.
To read the full document go to Shareapps4u
Form Personalization feature allows us to alter the behavior of Forms-based screens, including changing properties, displaying messages etc.
For a single form-function(a form running in a particular context based on parameters passed to it defined at function level) we can specify one or more Rules. Each Rule consists of an Event, an optional Condition, the Scope for which it applies, and one or more Actions to perform.
Here we will discuss about how can we change the field display name.
Basic Requirement
Our basic requirement is to change name the 'Latest Start Date' field to 'ABCD' in people Screen. Remember this name change should only be applicable for persons who are using 'UK HRMS Manager'.
To read the full document go to Shareapps4u
We have already discussed how we can provide a free text field to approver. Now Our aim is to make the field mandatory.
Basic Requirement
Our old requirement looks like "
when a person applies for a leave it should go his/her supervisor for approval. Approver must be able to provide his/her comments for approval or rejection of the requisition(comments optional). Approver must also be able to select the Organization Leave Type from a list of values . If the leave gets rejected, don’t store any information in database."
Now our changed requirement will looks like
"
when a person applies for a leave it should go his/her supervisor for approval.Approver must be able to provide his/her approval/rejection comments. The comments must be entered by the approver while rejecting the leave requisition.If he/she rejects the leave requisition without entering comments, then it should raise an application error.If he/she approves the requisition it should be optional.Approver must also be able to select the Organization Leave Type from a list of values . If the leave gets rejected, don’t store any information in database."
Design Appraoch
Following interpretation can be drawn from the above requirement.
1) The comment field is mandatory while rejecting the leave request.
2) The comment field is remain as optional if he/she approves the requisition.
To read the full document go to Shareapps4u
Now we know how to put a place holder for approver comments.Now we will learn how we can provide a list of values, so that approver can select a possible values from the drop down.
Basic Requirement
Our new requirement looks like "
when a person applies for a leave, it should go his/her supervisor for approval. Approver must be able to provide his/her comments for approval or rejection of the requisition(comments is optional).and once it is approved save the information in database . If the leave gets rejected, don’t store any information in database."
Now we will change our requirement a bit. It is as mentioned below"
when a person applies for a leave it should go his/her supervisor for approval. Approver must be able to provide his/her comments for approval or rejection of the requisition(comments optional). Approver must also be able to select the Organization Leave Type from a list of values . If the leave gets rejected, don’t store any information in database."
The possible "Organization Leave Type" list of values are
1) Medical Leave
2) Personal Unpaid Leave
3) Personal Paid Leave
(Change requirement is in bold)
To read the full document go to Shareapps4u
We have already build a simple custom workflow. Now we will make our previous workflow more n more complex.
Basic Requirement
Our initial requirement was "
when a person applies for a leave it should go his/her supervisor for approval and once it is approved save the information in database . If the leave gets rejected, don’t store any information in database."
Now we will change our requirement a bit. It is as mentioned below"
when a person applies for a leave it should go his/her supervisor for approval. Approver must able be to provide his/her comments for approval or rejection of the requisition.Once it is approved save the information in database . If the leave gets rejected, don’t store any information in database."
(Change requirement is in bold)
To read the full document go to Shareapps4u
Now we are comfortable with ABC of workflow (refer our earlier post ABC of Workflow). As of now we know most of the workflow components and their uses.
Lets design a simple custom workflow process and step-by-step we will make it more complex.
To read the full document go to Shareapps4u
