Integration Monitor for Workday®- Addressing Integration Management Challenges
By: Luke Switkowski on
• How many integrations do we have? • How often do my integrations break? • How often have they failed over time? • How do I keep an eye on day to day performance? • How do I ensure my integrations keep running? • How can we be more proactive when things fail? • Which integrations should I focus on enhancing? These are questions we at Kognitiv are asked constantly. They are great questions, and important ones, but the answers can often be elusive or complex, and sometimes there just isn’t a good answer at all. Workday® enables you to develop extensive and highly sophisticated integration environments, but monitoring and maintaining these systems on a daily basis can be challenging, and it only becomes more so…
Overview Are you contemplating activating Workday’s® Retroactive Processing functionality (“Retro”) and don’t know if Retro is right for your company? Have you been struck by the passion of current customers’ responses when you have asked them about Retro? Did you find customers that told you Retro was the greatest thing since sliced bread, applauding the hours (and sometimes days!) it saves them every payroll cycle. Have you found others that told you they hated Retro with a fiery passion, lamenting that they felt it takes them more time to use and maintain Retro than to do the work manually? If you are trying to figure out to whom you should listen, this blog post will provide you with…
Kognitiv Solution - Workday® to Fidelity® Demographic Integration
By: Luke Switkowski on
Many Workday® clients integrate their system with Fidelity® to manage Benefits, and one important part of the integration suite is the Fidelity® Demographic Integration, which is meant to send relevant data for eligible workers from Workday® to Fidelity®. However, the standard Template does not dynamically evaluate Workday® defined Benefits eligibility for a given worker, but instead uses either one-time eligibility detected during Onboarding, or enrollment into the 401k Plans themselves. So, in many cases, for Fidelity® to receive data on eligibility, Workday® must send data on enrollment. This can create scenarios in which the outbound file is incomplete, and as Worker 401k enrollment may be a prerequisite to be included on the file, there will inevitably be cases in which…
Bad data – it’s kinda like putting cheap oil in your brand new performance car…
By: Jen Kuzmick on
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. On every project, there is a high level of focus on design and execution of configurations, whether organizations, business processes, or security. And rightly so: those areas are routinely referred to as “pillars of Workday”. The problem is, there is often not nearly enough focus on data conversion and validation. It’s like outfitting your brand-new performance car with top of the line specifications: Upgrade that engine! Spring for the sport-tuned suspension! And why not, add the high-performance tires! Now… the lifeblood… the oil that with course through the…
System support should be simple. If a client has a system problem, they should contact their respective consultancy/support mechanism to get an answer. For such a basic interaction and engagement model, why are consulting companies asking clients to jump through hoops, commit to dollars spent, and charge varying rates for work and play the musical chair game with consultants? I think everyone knows what I mean! You call about an Integration issue on Monday and you speak with Suzie. You have an Integration problem on Tuesday and now you have to deal with Bobby. Very Frustrating! Here is what is unique about our On-Demand Support Model. Zero-dollar commitment for support access. Only pay for the time we spend on…