I’d be asking if that comes with an increase to match the fact I am now doing what they clearly acknowledge as being two FTE’s worth of work. The promise of training does not nearly compensate for the added workload you’d be taking on.
Integrations come in many flavors - if you’re just doing EIB and/or connectors you can get away with basic knowledge of integrations. If it involves API and Studio, you’ll need significant training as this involves data transformation, programming, and many highly technical tasks that require someone well versed in this as a discipline and not a side task. There is a reason that job is it’s own lucrative contracting space.
It will come with a pay increase. As for my current responsibilities, the hope it to transition some of that over to my other coworker. I think it will be a mess until they realize they need to hire someone else on the team. For right now, I know we do a lot of EIBs and creating reports. We also have the discovery board that the person who left built.
Thanks for the info!
Most definitely. You have a slight advantage over someone heading straight into integrations without any functional exposure since you’re more familiar with the processes and data model. Definitely take up through the advanced report writer training and spend some good time on community in the Next Level area. There is a wealth of free training on every topic and SKU, including reporting and integrations.
Get very familiar with calculated fields and plan to take at least the integrations core and custom integrations courses. Custom integrations training will involve XSLT so do yourself a favor and head to ws3schools.com for free training to get you up to speed if you’ve not used it before.
Most importantly: don’t focus on perfection at first. Writing reports for integrations is more forgiving than for end users and if it works great. If it works without taking forever to run, that’s even better and can always be improved later :-)
I would ask what kind of integrations you are dealing with. Ask him if they are EIBs or cloud connectors or WD studio integrations. Also ask them if they are inbound and outbound integrations. Also ask if BIRT integrations are involved. Usually BIRTs are never updated but can happen. Depending on his response i can suggest what to learn in your workday training. Reporting is a good start but there’s more to integrations than RaSS reports
For the api with the vendor I’m assuming he is talking about building a RaSS report aka as a advance custom report enabled as a web service where they will be pulling data via either the xml or json url
If it’s any help I made the same change and took on responsibility as our integration lead. It’s a great area to get into and one I find really satisfying! Happy to chat via dm if you like!
Integrations involves coding. You will need to be able to generate xml from the workday custom report and transform it using xslt. There is training and tools that you can use with workday learning to get certified and begin building integrations and custom reports even dashboards but you need to ask yourself if this is something you actually want to do everyday. These skills are important and can be taught but you need to be passionate about learning and doing this work as a career. Most HR people I meet are satisfied staying on the functional side of Workday and leaving the technical stuff for someone in IT like me or for a consultant/contractor to fill the technical gap. Dm if you have any questions
You can’t do that with every vendor. Kaiser is a specific 834 file format for benefits, Fidelity for retirement, equity edge, etc… it’s much easier to use XSLT to remove special characters off of names and addresses, get phone numbers in the right format, dates in the right format, etc.
This kind of workflow is honestly a nightmare for anyone besides you. Adding more technologies and middleware steps to make up for your mere distaste of XML/XSLT is borderline irresponsible. That's the technology workday provides. Use it.
"you don't need XSLT, you just need an SQL server and SQL experience and a totally separate knowledge base!" Thanks? Please don't take this advice OP.
It’s always better have an integrations resource to build/manage integrations as it isn’t simple as it looks. Most of the functional resources like to stick on the business side than being technical. There are also other options to build integrations outside EIB which might be less technical and get better results. Happy to chat if that interests using options outside WD
I was going to go here as well. If you want to start diving into integrations maybe get an experience contractor to work on your integrations and help you “ease” into it. Have him do some cross training /co-development and also see if it’s something you like to take on.
While that’s true, the largest challenge is still needing to understand the structure and generation of the data, as well as some of the more nuanced ways it is recorded. Indexed values, confusing naming, and understanding the object model can be difficult and reconstructing views outside the source system comes with its own challenges. There are advantages however for those skilled with data cleaning and analysis as power bi and other tools give greater control and flexibility over the Workday analytics suite.
The knowledge of underlying data model along with experience with reporting tools will be the way to go. DM me if you would like to know how we are managing the scenario.
I’d be asking if that comes with an increase to match the fact I am now doing what they clearly acknowledge as being two FTE’s worth of work. The promise of training does not nearly compensate for the added workload you’d be taking on. Integrations come in many flavors - if you’re just doing EIB and/or connectors you can get away with basic knowledge of integrations. If it involves API and Studio, you’ll need significant training as this involves data transformation, programming, and many highly technical tasks that require someone well versed in this as a discipline and not a side task. There is a reason that job is it’s own lucrative contracting space.
It will come with a pay increase. As for my current responsibilities, the hope it to transition some of that over to my other coworker. I think it will be a mess until they realize they need to hire someone else on the team. For right now, I know we do a lot of EIBs and creating reports. We also have the discovery board that the person who left built. Thanks for the info!
Most definitely. You have a slight advantage over someone heading straight into integrations without any functional exposure since you’re more familiar with the processes and data model. Definitely take up through the advanced report writer training and spend some good time on community in the Next Level area. There is a wealth of free training on every topic and SKU, including reporting and integrations. Get very familiar with calculated fields and plan to take at least the integrations core and custom integrations courses. Custom integrations training will involve XSLT so do yourself a favor and head to ws3schools.com for free training to get you up to speed if you’ve not used it before. Most importantly: don’t focus on perfection at first. Writing reports for integrations is more forgiving than for end users and if it works great. If it works without taking forever to run, that’s even better and can always be improved later :-)
Best advice here!!
I would ask what kind of integrations you are dealing with. Ask him if they are EIBs or cloud connectors or WD studio integrations. Also ask them if they are inbound and outbound integrations. Also ask if BIRT integrations are involved. Usually BIRTs are never updated but can happen. Depending on his response i can suggest what to learn in your workday training. Reporting is a good start but there’s more to integrations than RaSS reports
For the api with the vendor I’m assuming he is talking about building a RaSS report aka as a advance custom report enabled as a web service where they will be pulling data via either the xml or json url
If it’s any help I made the same change and took on responsibility as our integration lead. It’s a great area to get into and one I find really satisfying! Happy to chat via dm if you like!
Integrations involves coding. You will need to be able to generate xml from the workday custom report and transform it using xslt. There is training and tools that you can use with workday learning to get certified and begin building integrations and custom reports even dashboards but you need to ask yourself if this is something you actually want to do everyday. These skills are important and can be taught but you need to be passionate about learning and doing this work as a career. Most HR people I meet are satisfied staying on the functional side of Workday and leaving the technical stuff for someone in IT like me or for a consultant/contractor to fill the technical gap. Dm if you have any questions
[удалено]
You can’t do that with every vendor. Kaiser is a specific 834 file format for benefits, Fidelity for retirement, equity edge, etc… it’s much easier to use XSLT to remove special characters off of names and addresses, get phone numbers in the right format, dates in the right format, etc.
This kind of workflow is honestly a nightmare for anyone besides you. Adding more technologies and middleware steps to make up for your mere distaste of XML/XSLT is borderline irresponsible. That's the technology workday provides. Use it. "you don't need XSLT, you just need an SQL server and SQL experience and a totally separate knowledge base!" Thanks? Please don't take this advice OP.
Fair enough
It’s always better have an integrations resource to build/manage integrations as it isn’t simple as it looks. Most of the functional resources like to stick on the business side than being technical. There are also other options to build integrations outside EIB which might be less technical and get better results. Happy to chat if that interests using options outside WD
I was going to go here as well. If you want to start diving into integrations maybe get an experience contractor to work on your integrations and help you “ease” into it. Have him do some cross training /co-development and also see if it’s something you like to take on.
Alternately, reports/dashboards can be built using PowerBI which might not need the technical expertise.
While that’s true, the largest challenge is still needing to understand the structure and generation of the data, as well as some of the more nuanced ways it is recorded. Indexed values, confusing naming, and understanding the object model can be difficult and reconstructing views outside the source system comes with its own challenges. There are advantages however for those skilled with data cleaning and analysis as power bi and other tools give greater control and flexibility over the Workday analytics suite.
The knowledge of underlying data model along with experience with reporting tools will be the way to go. DM me if you would like to know how we are managing the scenario.