How To Send Notification To Multiple Users

sOracle Workflow roles are stored in the database, in the Oracle Workflow directory service.The performer can be an item type attribute that dynamically returns a role.To send a single notification(FYI/Actionable) to multiple users we have to use Role attribute as performer of that notification.The attribute value must be the internal name of a role. 

Here we will discuss how can we send a single notification to multiple users.

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 theOrganization Leave Type from a list of values . If the leave gets rejected, don’t store any information in database.The approver should able to view/edit the person "Special Information Types" before approving the leave request.Before approving the sick leave request the approver must able to see the submitted medical document."

Now we will twist our original requirement- Instead of going to Supervisor for approval, all the leave request must go to the following identified people

• ROLE1_APPR (User name of the person)
• ROLE2_APPR (User name of the person)
• ROLE3_APPR (User name of the person)

To read the full document go to Shareapps4u 

How To Attach Document With Notification

Oracle Workflow also provide us a provision to attach document and help us to share information with the different stakeholders of business process (whereever is required) .

In a workflow process, we can attach documents generated by a PL/SQL procedure, which we call PL/SQL, PL/SQL CLOB, or PL/SQL BLOB documents.

Here we will discuss about the ways to attach PL/SQL BLOB and PL/SQL CLOB with the notification.

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 theOrganization Leave Type from a list of values . If the leave gets rejected, don’t store any information in database.The approver should able to view/edit the person "Special Information Types" before approving the leave request."

In addition to the above requirement:- When a Person applies for leave* he/she also submits the medical document. Approver should able to see the submitted medical document submitted by person.

* ==> Here we are considering only sick leave.

To read the full document go to Shareapps4u 

How to Restrict Agency from entering Duplicate Candidate

Agency personnel can Search for vacancies assigned to that agency, and view vacancy details such as the maximum number of applicants that can submit for a vacancy and current number of applicants.They can also create user accounts for candidate and apply for job on behalf of candidate.

Basic Requirement

Our basic requirement is as mentioned below:-

Oracle application doesn't restrict agency from entering duplicate candidate.Now our organization is landing up paying multiple times  for a single candidate,since there are multiple entry for a single candidate is found. Now our basic requirement is to restrict the agency from entering duplicate candidate.

The duplicate candidate can be identified by email address.

If agency personnel try to enter candidate with already existing email address then application should throw an error.

To read the full document go to Shareapps4u 

iRecruitment Data Migration - How To Migrate Resume

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 
 

How To Take Approver's Input- Launching Oracle Form from Workflow(from Approver's Notification)

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 - How to Change Field Name

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

How To Take Approver's Input- Making approver comments a mandatory Free Text field

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