Sunday, 6 April 2014

Pleasantly surprised

A while back, I mentioned looking at address data.  While we mapped from PeopleSoft to Workday and made decisions to combine fields where we had to, we had a country where WD made the field required, while we would call it optional.  I spoke with our data entry expert in country to confirm it is not used and to confirm that it's not existing in local payroll.  I checked online as well and everything that I found aligned with this data being optional.

I put in a Brainstorm making this request to convert it to optional.  Three weeks later it had hardly any votes, but someone from WD responded to it and asked for the legal source, as their sources said that it was required.  I missed getting a notification at this point that someone had responded, so I did not respond.  However, the same WD employee then responded a few days after, that indeed it should be an optional data element based on new research, and that it was targeted for WD 21 to be updated.

On one hand, I have no idea how they can get to WD21 with no one else noticing this, except that we are not a pharmaceutical company, so maybe our global footprint differs from other big customers.

We had already programmed our conversion logic to stick 'unknown' in the field (no field validation), which was going to look ugly from a self-service standpoint.  Happy to be able to lose that logic and instead leave the field blank.

As a PSoft customer, our management made a strategic decision not to apply patches.  We don't run payroll out of PSoft in Europe, so we can do that.  Occasionally, when something is noticed by the users and it is deemed critical, we will extract that bit of code out of a project, and our developers will manually apply just that bit.  As you can imagine, whenever we would log a case with PSoft customer support, it would be instantly closed as you are not on the latest code line.

I realize this is a quick little fix by WD for something that should not have been wrong in the first place, but quite pleased at how this one has turned out.

No comments:

Post a Comment