Wednesday, 25 January 2017

HCM Cloud Release 12

HCM Cloud Release 12

We've been waiting for this release for some time now.   At least the documentation is now available and we can see what's new and what's changing.   I've held off writing this post until we had our pod upgraded, but in the interests of sharing information to the wider HCM Cloud Community, I've decided to make some comments now before we've got our hands on it.  Consequently, I won't be sharing any screenshots.   However, example screens can be seen on the various Oracle Cloud information portals.   I particularly recommend Customer Connect  and the Cloud Readiness pages.

One big area of impact is around security.   There are many enhancements to the security console.  More of this later.

Many other changes tidy up some of the HCM processes.

I'm not going to cover all changes, but here are a few of the more interesting ones:

New Hire Process

It will now be possible to add multiple managers and manage subordinates during the hire process.   Up to now, the hire was one process and then a second process was needed to update the new hire via the Person Management workarea.

Duplicate Person Check

This has now been made more configurable.   For example, you can now configure the rules which determine which set of data is checked to determine for duplication.  Before R12, you could only switch the standard duplicate check on or off.

Manager Changing Hours

In R12, when a manager uses the change hours process, they can optionally also change the salary.   This is useful because the salary is often impacted by changing hours.  Now it doesn't need to be 2 transactions or handed off to HR.

Applications Security

Now this is where I think the biggest changes are going to occur.

We've had the Security Console for several releases now.   Up to this point, it's bee useful for visualising the role structures and hierarchy and for (limited) creation and copying of roles.

From R12, it's going to include many new features.

Reference Role Model

It's always been good practice to use the 'out of the box' roles as a reference and if you needed to tailor them to your own requirements, for example removing or adding some seeded duty roles to a job role then you should make a custom copy.  However, this wasn't enforced because the seeded reference roles were not protected.

In R12, the seeded roles are locked down and cannot be edited.   This will force implementors to make custom roles and therefore avoid any potential conflicts if Oracle ever change the seeded roles.   It also allows the seeded roles to be used as a reference against your 'custom' changes.

N.B.   There are some pre-upgrade checks you will need to do to prepare for this!

User Account Maintenance

This is now going to be part of the Security Console.  So, administrators can use the Security Console to manage users rather than navigate to OIM.

Userid and Password Policies

Because the users can now be managed via the Security Console, the policies for their formats and validation is also being made available for configuration.  Previously, this would require a request to Cloud Services.   The policies look as if they will be somewhat limited in choice and it remains to be seen what will happen if a customer says "I want this format which is  not available - how do I enforce it?".

If you had previously submitted an SR to request a 'custom' policy, you should review whether this policy is still valid.   There is a document on MoS (My Oracle Support) to help (Doc Id 2023523.1) 

Role Visualisation

Staying with the Security Console enhancements, the visualisation of roles will be simplified.   I have yet to see how this works, but I welcome any simplification.   The idea of visualising roles was great, but as soon as you start having roles with dozens of subordinate roles the whole visualisation loses its appeal and looks very messy.

you will also be able to search for roles within a hierarchy to quickly locate where they are.  Very useful in a complex structure.

You will also be able to define custom notification templates for messages assocaited with user management.   I'm not sure yet if this extends to other notifications.

Active Directory

Integration between AD and OIM is often a requirement we see in implementation projects.  In R12 there will be a built in synchronization job, controlled via the Security Console.

New Security Profiles

Previously, you could use an Area of Responsibility (AOR) in a person security profile by including custom SQL code.   From R12, this is simplified and there is a new security profile type for AOR.   However, be careful with it as it may conflict with other person related security rules such as 'show me people with surnames beginning A-K'.

One neat feature which stood out to me is the ability to see the impact of the security profile you have just configured.   You will be able to see how many people (and who they are) who will be returned by the security profile.

You will also be able to include areas of responsibility in the Role Provisioning Rules configuration.

HCM Spreadsheet Loaders

By popular demand, spreadsheet loaders are back!   But, they are implemented as add-ons to Excel.  They will have somre 'configurability'.  At the time of writing, I've not had enough time to investigate this fully, so maybe another post soon with some more details is in order.


Conclusion

All said, this looks like a release full of useful enhancements.  But, when will it hit the streets??



Monday, 18 July 2016

Oracle Cloud HCM/ERP Release 11

Oracle Cloud HCM/ERP Release 11



It's been a busy few months recently.  Hence the lack of blog posts from me.

We were part of the Early Updaters programme for Release 11, and now that R11 is generally available, I think it's time for a brief review of the new release.  This post is solely about the look and feel.   I will post more information later about functionality.

The main enhancement, which is noticeable immediately, is that all screens are now in what we used to refer to as the "SUI" format (or Simplified User Interface).  Originally this format was designed for the 'casual' user, such as employees or line managers.  But its success seems to have prompted Oracle to redesign all screens in this format.

Here's an example of a frequently used screen in HCM - the Person Management screen.







As you can see, it's very similar to a pre-R11 employee SUI screen.  Clean, simple.

However, sometimes these innovations are spoiled by small details.   Users familiar with the older 'classic UI' screens will know that the tasks that can be performed on each workarea were shown on the left hand side of the screen.   It was immediately obvious what you could do in any given workarea.

On the SUI screens, the tasks are hidden (initially) in the 'panel draw' on the right hand side of the screen.  To see them, you must open the drawer.   Take a look at the screen when the panel draw is opened.





Now you can see the tasks!   I also find that some work areas default to a different landing page to the one displayed in R10.   Again, a simple point, but such issues can be annoying to a user.

On the ERP side of the product, before R11 many screens were in the 'classic UI' format.  Now, they are all SUI.   I think it's a great improvement and we are seeing good feedback from our R11 customers.

One final point.   The ERP and HCM development teams appear to have diverged in their use of certain new functionality.  For example, in ERP we see many screens using 'InfoTiles'.   An InfoTile is located (usually) at the top of the screen and can be used to show headine information and to filter the search results data.  It works very well and user feedback is extremely positive.  But, in HCM, this technique is not used.   Maybe it will come later.  But, consistency in a product is always a good thing, so I hope it does.