I took some time to dive into the new Job Service for version 8. You can grab me, John Perona, or Dave Wallace at Summit and ask what the Job Service is all about. We are publishing a How Do I video to the developers subscription and might add it to the Implementer’s and Admin’s subscription as well since there is a bit of configuration and monitoring involved if you want to do so. This is all on the backs of an awesome developer you all might have met before - Nathan Baulch. Great work and some great documentation too (which Lori is doing a great job getting into the help files).
I am as excited about the Job Service as I was about Process Orchestration. Are they the same? No. Can they do similar things? I suppose.
Job Service is easier to write for – no Windows Workflow Foundation stuff to worry about. You just have C# and a Job Service namespace to add in to your project. You then write some code around onExecute and you are set. Of course you can do a lot more and there is a configuration file and a portal to worry about, but they are easy to grasp. Just check out the video in the Developer's Subscription!
How does this relate to Summit?
In my partner session (P-0308) on Tuesday morning, we are going to talk about ROI. Really what we need to determine is what tools are there now that we might not be using, or that we can take advantage of? Anything that was added? Job Service certainly fits, but isn’t necessarily a top 3 item. Check out that session to discuss (this is not a Power Point show!) this and anything else new that we can use to reduce development time, increase customization capability, solve problems, and empower our users.