Blog Posts
Follow our stories and insights
• How many integrations do we have? • How often do my integrations break? • How often have they failed over time?
Are you contemplating activating Workday’s® Retroactive Processing functionality (“Retro”) and don’t know if Retro is right for your company?
Many Workday® clients integrate their system with Fidelity® to manage Benefits, and one important part of the integration suite is the Fidelity® Demographic Integration
Bad data, lack of validation procedures, lack of attention to detail… as a veteran of over 50 Workday projects, it’s a theme I’ve seen repeated over and over again.
System support should be simple. If a client has a system problem, they should contact their respective consultancy/support mechanism to get an answer.
Something that has always chapped my ass, and has made the maintenance of roles in Workday harder than it needs to be, are redundant role assignments.
Over the past few months, we have had several people ask – ‘How do you do it?’ – with regard to Kognitiv, Workday, and our ability to acquire business.
Being a tenured member of the ERP community, I’ve done a lot of reporting in my day. A lot.
In my previous post “Business Process Booklet” I talked about regression testing business processes after making security changes. Today we talk reports.
It is safe to say I have been doing Workday security for quite some time. Over my years I have come across a few reports that no matter what project, client, size, or shape, I use, ALWAYS.
If you’ve ever had to configure business process definitions in Workday, you likely know what it’s like trying to accommodate a myriad of use cases and conditions with one configuration.
One of the things that became evident to us when getting involved in our first few Workday sales cycles was that the real selling is done by the Solution Architects and Lead Consultants, not the sales team.
I spent the better part of 5 years as a Workday implementation consultant, holding project roles as Data Conversion Lead, HCM Lead, Compensation Lead, Benefits Lead, Absence Lead, and Project Manager.
Formula 1 may not be everyone’s cup of tea when it comes to spectator sports. In fact, it wasn’t my cup of tea until a few years ago. I would say “Who watches that?
My colleague recently wrote about one of Workday’s lifesaver features. I decided to compliment that with a favorite of my own: Report Fields and Values.
One of the areas in Workday that can really take time and patience is security configuration.
I have spent my entire working life in the arena of Consulting. I have worked for massive consulting firms and tiny ones that were just trying to make a name for themselves.
When I started in the Workday Eco-system back in 2011 as a data conversion consultant at Meteorix, we would often talk about how to handle the security responsibilities on our go-lives.
• How many integrations do we have? • How often do my integrations break? • How often have they failed over time?
Are you contemplating activating Workday’s® Retroactive Processing functionality (“Retro”) and don’t know if Retro is right for your company?
Many Workday® clients integrate their system with Fidelity® to manage Benefits, and one important part of the integration suite is the Fidelity® Demographic Integration
Bad data, lack of validation procedures, lack of attention to detail… as a veteran of over 50 Workday projects, it’s a theme I’ve seen repeated over and over again.
System support should be simple. If a client has a system problem, they should contact their respective consultancy/support mechanism to get an answer.
Something that has always chapped my ass, and has made the maintenance of roles in Workday harder than it needs to be, are redundant role assignments.
Over the past few months, we have had several people ask – ‘How do you do it?’ – with regard to Kognitiv, Workday, and our ability to acquire business.
Being a tenured member of the ERP community, I’ve done a lot of reporting in my day. A lot.
In my previous post “Business Process Booklet” I talked about regression testing business processes after making security changes. Today we talk reports.
It is safe to say I have been doing Workday security for quite some time. Over my years I have come across a few reports that no matter what project, client, size, or shape, I use, ALWAYS.
If you’ve ever had to configure business process definitions in Workday, you likely know what it’s like trying to accommodate a myriad of use cases and conditions with one configuration.
One of the things that became evident to us when getting involved in our first few Workday sales cycles was that the real selling is done by the Solution Architects and Lead Consultants, not the sales team.
I spent the better part of 5 years as a Workday implementation consultant, holding project roles as Data Conversion Lead, HCM Lead, Compensation Lead, Benefits Lead, Absence Lead, and Project Manager.
Formula 1 may not be everyone’s cup of tea when it comes to spectator sports. In fact, it wasn’t my cup of tea until a few years ago. I would say “Who watches that?
My colleague recently wrote about one of Workday’s lifesaver features. I decided to compliment that with a favorite of my own: Report Fields and Values.
One of the areas in Workday that can really take time and patience is security configuration.
I have spent my entire working life in the arena of Consulting. I have worked for massive consulting firms and tiny ones that were just trying to make a name for themselves.
When I started in the Workday Eco-system back in 2011 as a data conversion consultant at Meteorix, we would often talk about how to handle the security responsibilities on our go-lives.
