- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on ‎04-21-2016 10:44 AM
Session ID:
18BB14
Presenter(s):
- Arun Bali - ServiceNow Architect
Company(s):
Lawrence Berkeley National Laboratory
Abstract:
Dynamic data driven workflow has been adopted by many organizations to prevent maintaining multiple workflows for multiple catalog items. It also enables non-ServiceNow admins to manage and edit workflows.
In this session, Lawrence Berkeley National Lab will walk through a dynamic workflow that fulfills complex business process for all catalog items. They will demonstrate sequential and concurrent approvals and tasks for dynamic workflow with use of conditional tasks,conditional approvals and filtered variables that push dynamic workflows to the next level.
Date and Time:
Wednesday, May 18, 2016 @11:10 AM - 12:00 PM
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Was this recorded anywhere? Thanks
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi James,
Here's the link where you can find the presentation slide deck: Pushing Dynamic Workflow to the Next Level with Conditional Approvals and Tasks
Let me know if this works for you.
Thanks!
LaRel
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
I cannot view file. i get this message
Access to this place or content is restricted. If you think this is a mistake, please contact your administrator or the person who directed you here.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi Tod,
Sorry you were unable to see the content - I've attached the deck directly to this document post. Let me know if you're still having any troubles and I'll email it to you.
Thanks!
LaRel
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Yes, thank you.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
I'm curious if anyone has put this into active practice. I'm not sure how this workflow would handle multiple levels of tasks. For example, if we were to create 4 concurrent tasks and we wanted to spin tasks off of those individual concurrent tasks how would that be accomplished? example:
This model works fine:
task A (order 10) ----|
task B (order 10) ----|--------> Task E (order 20)
task C (order 10) ----|
task D (order 10) ----|
This model doesn't work from what I see:
task A (order 10) -------------> Task D (order ?)
task B (order 10) ----|
task C (order 10) ----|--------> Task E (order ?)
task D (order 10) ----|
Thanks