Martin Millmore's Blog

Last Friday we released our latest round of functionality, IRC.E RUP1 (patch 5061111). This is a great new released that contains some new functionality that we know that many of you have been waiting for. This includes;

• Assessments
  Assessments integrates iRecruitment with iLearning to allow you to set up tests, either scored or non-scored, and to have a test be taken when a candidate registers, and when they apply for a vacancy. You can set up different tests on a vacancy by vacancy basis too. Managers can then see the results of the tests, and for example just see people who have passed a test.


• Vacancy Approvals
  Approvals in the vacancy process has not changed very much since it was first released, while the approvals in the new Offers functionality in IRC.E is significantly more advanced. We really wanted to bring the new advanced approvals functionality in to the vacancy area too, so in IRC.E RUP1 we re-wrote the vacancy approvals process to use the same common approvals code as Offers. This offers a number of advantages, such as;
  




• The Vacancy workflow is now just used for approvals, not navigation, making it less prone to change as we add new functionality. This means that if you create a copy, it is less likely to need to be updated in future.


• You can now add dynamic approvers and people to receive FYI notifications


• Comments are routed better


• We have set up the approval rules so that you can modify them more easily - you can add new rules within our seeded transaction, without modifying the seeded transaction


• More types of AME transaction are supported (e.g. position hierarchy).


• Allow my account to be searched
  For those of you who want to default the Allow My Account To Be Searched checkbox to Yes, we have added a profile option to do that


• Applicant Search
  On the applicants for vacancy screen, we have made a few enhancements to make it easier to use. We have added the options of viewing rejected and hired applicants as well as the existing default of active applicants. We have also changed the assignment status criteria on this page to be based on a poplist rather than free text, so you don't have to remember what the statuses were called. These changes also meant a change in the applicant details screen, where you can choose between displaying a list of their Active applications or All applications (i.e. rejected and hired too). Which of those you see depends on whether or not you drill down to see an active assignment (default is Active in this case) or a rejected or hired assignment (default is then All). Sounds complicated, but is obvious in practice.


• Online Help
  We have added online help to about 40 of the manager pages. This helps them understand the concepts and ideas, as well as the detailed steps in using iRecruitment. This requires patch 5348564.

As well as all of that, we have done a number of bug fixes and minor enhancements, to make this our best release yet. The whole team are really proud of what we have built here, so we hope you all download it and upgrade to it soon! Have a look on metalink for more details. The About Doc is note number 373827.1, and the new implementation guide is note number 373837.1. Both contain far more information than in this article, so please have a read.

For those of you who are confused by the name of the release, let me explain. We are no longer releasing mini-packs on 11i. Instead we are releasing rollup patches. They can contain a similar level of new functionality and bug fixes, but they are not a cumulative patch like the mini-packs were. This makes them smaller and more manageable, but means that they can only be applied on top of the last mini-pack. If you are not currently on IRC.E, when you apply IRC.E RUP1, you must either apply IRC.E first, or merge the two patches together and apply as one.