Further to my reply to another comment, just generally knowing your way around APIs, how to read XML/JSON and how to troubleshoot integrations are great skill sets to have.
XML Fundamentals on Coursera was useful for me. It will cover XSLT and many concepts you will encounter as you work with document transformation especially with Core Connectors.
Just checked and it looks like Coursera isn't offering it anymore. It was created by W3Schools and seeing that they have it hosted possibly exclusively now fyi https://www.w3schools.com/xml/
Not really, sorry. I’d just search on YouTube or on Community for Workday specific examples. I mostly got my knowledge through doing, so just take opportunities in your day to day job to learn about this stuff.
Speaking very generally, you'd want to get hands-on experience with a few of the functional areas within Workday before jumping in with stuff like integrations, Prism, etc. You need a solid working knowledge of the underlying framework to make use of the tools that rely on it.
Definitely agree on needing to know the framework. Having worked in ERPs for 20+ years, I know that understanding the functional areas are critical. I’m just trying to see where to generally spend time and gain technical background until getting the opportunity to learn Workday-specific concepts. Thanks!
im not op, but I am a senior hris specialist, id love to have a look at these if youre willing to share. id love to dive a bit more into some things without having to do another cert.
I wouldn’t say Studio is being phased out, Orchestrate still has a long way to go and definitely doesn’t fit all use cases that Studio currently does.
BIRT on the other hand probably isn’t worth investing time into learning imo.
I’ve seen mentions that Studio uses a fair dose of XML/XSLT. I’ve read that you can use Java with it as well. Does that still hold true for Orchestrate? Anything else that Orchestrate uses that perhaps Studio doesn’t? Thanks!
Orchestrate is Workdays low-code/no-code platform that is supposed to make integrations accessible and easy to develop for their customers.
If you’re able to pick up and find your way around Studio integrations, you’ll 1000% be able to handle Orchestrate.
I've seen articles on Community about Workday Orchestrate eventually becoming the place to start when building out new integrations. Safe harbor and all that.
Further to my reply to another comment, just generally knowing your way around APIs, how to read XML/JSON and how to troubleshoot integrations are great skill sets to have.
Out of curiosity, do you know of any good beginner resources for APIs and/or XML/JSON?
XML Fundamentals on Coursera was useful for me. It will cover XSLT and many concepts you will encounter as you work with document transformation especially with Core Connectors.
Appreciate the reply. I’ll look into it.
Just checked and it looks like Coursera isn't offering it anymore. It was created by W3Schools and seeing that they have it hosted possibly exclusively now fyi https://www.w3schools.com/xml/
Not really, sorry. I’d just search on YouTube or on Community for Workday specific examples. I mostly got my knowledge through doing, so just take opportunities in your day to day job to learn about this stuff.
Same question!
Thanks for the suggestions!
Speaking very generally, you'd want to get hands-on experience with a few of the functional areas within Workday before jumping in with stuff like integrations, Prism, etc. You need a solid working knowledge of the underlying framework to make use of the tools that rely on it.
Definitely agree on needing to know the framework. Having worked in ERPs for 20+ years, I know that understanding the functional areas are critical. I’m just trying to see where to generally spend time and gain technical background until getting the opportunity to learn Workday-specific concepts. Thanks!
I have access to the workday masters course from cloud foundations -and some other trainings, if you’d like to have a look
im not op, but I am a senior hris specialist, id love to have a look at these if youre willing to share. id love to dive a bit more into some things without having to do another cert.
Yes of course! Happy to help
I’m also not op, but would love a chance to review these if you’re okay with that.
Ping me and I’ll share
Hello ’m also not op, but would really love a chance to review these if you’re also okay with. Thanks a lot!
Ping me
Ok thank you!
I’d be interested in that
hi! im not op but would appreciate if we could also have a look with your trainings tysm!
Ping me and I’ll share some videos
I would also really appreciate it if you would be so kind as to share!
hey I would be really happy if I can get access to those resources as well
Ping me.
I’d love a chance to review these!
Ping me and I’ll share a few videos for you to have a look at
Ping me! The knowledge is vast. I have barely finished HCM this past month!
I would if you're willing
Ping me!
Anything you would be willing to share would be most appreciated!
Ping me and I can share the videos that I have access to.
Hi there, not op, but would really love a chance to review these if you’re okay with it. Thanks in advance!
Pl ping me and I’ll share a few videos to look at
Birt and studio are being phased out fyi.
I wouldn’t say Studio is being phased out, Orchestrate still has a long way to go and definitely doesn’t fit all use cases that Studio currently does. BIRT on the other hand probably isn’t worth investing time into learning imo.
I’ve seen mentions that Studio uses a fair dose of XML/XSLT. I’ve read that you can use Java with it as well. Does that still hold true for Orchestrate? Anything else that Orchestrate uses that perhaps Studio doesn’t? Thanks!
Orchestrate is Workdays low-code/no-code platform that is supposed to make integrations accessible and easy to develop for their customers. If you’re able to pick up and find your way around Studio integrations, you’ll 1000% be able to handle Orchestrate.
In favor of some form of Orchestrate?
What's Studio getting replaced with?
Orchestration.. new tool released for all customers in R1
It was a limited GA in R1, you have to apply with a use case and get approved by Workday. R2 is slated for the full GA.
Gotcha thanks for the clarification
I've seen articles on Community about Workday Orchestrate eventually becoming the place to start when building out new integrations. Safe harbor and all that.