- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-28-2017 05:46 AM
I am currently trying to set up a customized state flow for specific HR Cases regarding ServiceNow changes. We want to have different phases (request review, business requirements, functional requirements, etc.) in which at each phase the assigned to user can set the state to "Review" when they think it is complete and reviewers can move it back to the previous phase if it needs more work or approves the work and moves it forward to the next phase.
We are currently working with Helsinki and are not using workflows at this time. Is this going to be very complicated to set up using state flows? Or is there an easier way to accomplish this that doesn't involve adding a bunch of new State choices and State Flows?
Solved! Go to Solution.
- Labels:
-
HR Service Delivery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-28-2017 06:18 AM
The second parameter is the sys_id of the state flow record. (I know, I hate sys_ids in scripts too!)
I have attached a cheat sheet that is meant to augment the product documentation on state flows. I hope you find it helpful. Please let me know if there is any feedback.
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-28-2017 06:23 AM
Gotcha, I had never seen that before!
Thanks, I'll let you know if I have more questions as I encounter them (I'm sure I will).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-28-2017 07:27 AM
Is there a way of accessing the previous state of a case? For example, for each phase, the Assigned To user will move it to Review when they have completed work and a group of reviewers will determine if it Needs Work or Looks Good (these will be UI Actions in the form of buttons). If it needs work, it should move the state back to the previous state (whatever phase they were doing work for) and likewise, to determine what phase is next I will also need the previous state. Is there an easier way you can think of rather than having a separate review state for each phase?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-28-2017 07:52 AM
How you set up your state flows and manual (UI action) triggers is up to you. Yes, you can have a 'previous' that moves it back to another state in the flow. It's all in what fields you set. The cheat sheet helps with that. If not, let me know.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-28-2017 08:50 AM
I ended up just creating a previous state field and looking at that in some of the UI Actions.
I got my state flow set up (or I think it is) and when I went to test it as another employee, the new states I created weren't visible. For example, when the case entered the Business Requirements Phase it only appeared to be in the Ready state to the user I impersonated. When I was looking at the case as myself, it showed up in the proper state. Do I need to create a new ACL?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-28-2017 08:53 AM
ACLs will control the read/write access of the fields. They should not impact the values shown in the state.
