I have a requirement where i need to get approvals from multiple users and workflow can be proceeded to the next step when all the users have approved. I wanted to know how we can achieve or design a single workflow model to achieve the requirement
You can add a separate participant step for each approver/approverGroup. Afte r approval from one approver/approverGroup, next step would send approval request to next one.
Once all are done, you can proceed further.
OR
Complex one [Not recommended]
You can create your custom process step to send notifcation to all approvers and in the next operation, proceed only when each one of them has approved[keep that record on seprate node of each workflow instance ]
Related
Quite a novice to using two Forms in K2 for Approval,Like an Originator and an approver, one sends the request, and the other Approves the request and sends to the second party who in turn verifies the information and upon update sends a notification to the Originator. I wanted to know how i can go about something like this Like where do i start? So far I have been able to have it linked to one of the Approvers , but in this case there are 2 of them like this chain
Originator -> First Reviewer (Approver) - > Second approver.
How do i go about something like this?
there are different ways to accomplish this:
You might do it by adding 2 user tasks one after another - so that 2nd task is opened after 1st one is approved.
You might use single task with multiple recipient groups, configure task to require 2 responses, and then configure custom voting rule to achieve desired result.
Approach 1 would be easier to implement.
You have to create two tasks one after another, the control goes to second task if the first one is approved. After the approval of second task you can add a email notification.
I'm new to ServiceNow and followed this tutorial Workflow for Servicenow Incidents to create a simple workflow for an approval request.
The steps that I took on studio of my developer instance:
Created an application "ServiceNowApp"
Created a table "Order"
Created a field "Status"
Created a workflow as described on tutorial
My intention is to trigger the workflow by the creation of a new record on Order table and change the Status field based on the decision of the responsable user.
Any advice is welcome to accomplish the goal
Thank you
When you create the Order table, make sure it extends the Task table. This will allow you to add an approval to it.
Based on that post you should be able to follow things as you build it out in the same manner, just select your Order table.
You can do it using core activities Approval - User and Set Values in your workflow.
(Your Order table doesn't need to extend Task table.)
Approval - User creates an approval record for the responsible user and the user can open the record to approve/reject it in the My Approvals menu.
Set Values sets Status field to any value.
Your workflow would look like below:
You can add the trigger conditions on the workflow itself while creating the workflow.
You can also choose the table and then choose any status field you want to act on the requests.
Below is the snapshot which might help you understand the concept.
Let me know if you need any help.
Regards,
Ishaan
I was just checking for the feasibility for workflows on Incidents and found this post.
It seems it is possible to have workflows on incidents.
I just need to know is there any proper way to do it..I am kind of new bee to Servicenow. anyone share the experience and how can I achieve this.
For instance, a simple approval workflow on the Incident..
Thanks in advance Chitra
A few basic changes can get this going, since the Incident table has the Approval fields and such associated to it.
Alter the Incident form
Go to an Incident
Configure (Fuji) or Personalize (Eureka) the following
Form Layout > Add the Approval field
Related Lists > Add the Approvers list
Create workflow for approval
Next you want a workflow to run when an Incident is created.
Go to the Workflow Editor
Create a new workflow with the following
Name: Incident - Approval
Table: Incident [incident]
Activity pinning: Set by activity
If condition matches: Run the workflow
Condition: Leave blank
Leaving the Condition blank will cause it to run on creation of an Incident.
Fill out workflow
Add the following activities
Approval Action
Name: Set Requested
Action: Mark task as requested
Approval Group
Name: Wait for Approval
Groups: Select the group who will approve all Incidents, such as the Help Desk. Important: This group must have group members or this will automatically be approved.
Leave the rest as default
Approval Action
Name: Incident Approved
Action: Mark task approved
After creating this, connect the Approved node from the Wait for Approval action you just made to this activity. Also connect the Always node to the End Activity
Approval Action
Name: Incident Rejected
Action: Mark task rejected
Like above, connect the Rejected node from the Wait for Approval action you just made to this activity and connect the Always node to the End Activity
Test the workflow
Finally you can test this by Publishing this workflow and creating an Incident.
Publish your workflow
Create a new Incident and open it
Note the Approval field should say Approval requested
Under the Approvals Related List, you should see a list of all users inside of the group you set within the Wait for Approval Activity
If any user in this list Approves it, the Approval field will change to Approved
If any user in this list Rejects it, the Approval field will change to Rejected
I've put in a sample picture below, but this is a very basic workflow. It can get more complex as your needs change or are different. Hopefully this gets you on your way to a start.
Let me explain the scenario. I want to start a workflow instance which will create a request approval process. There are different levels and each level has approvers and specific time is assigned for each level. An approver should approve within the given time to complete process or he/she may be alert again to approve once the assigned time of the level is over.
A user may request something by starting a approval process this would intiate a workflow which will create a workflow instance for the specific request. when the process starts it will inform the respective approvers in first level to approve the request made by a user. if a approver failed to approve within the given level time the approver will be alerted to approve the request and it should pause the workflow and wait for it. if he managed to approve the request the process should moved to the next level and continue with the same process until the number of levels are over.
Can i do this using windows workflow foundation. I read and understood that invoking a workflow, bookmarks can be used for this. i need to how can i manged the background timer for each level and alert the users. im stucked at that point please help me.
if there is a better solution please feel free to talk :).
Yes you can achieve this by using a Pick activity which has a timer (delay) activity and your custom approval activity inside. Pick activity will choose only one PickBranch to complete when ever either of the contained activity is completed. That said if the timer activity is triggered, the custom approval activity will be cancelled then. And you can choose to do what ever you what to do afterward such as sending emails to notify the involved approvers that the task was expired. WF has a lot of potential but it seems this technology has been left in the corner by its vendor for a while...
I need to create a multilevel Approval Workflow for following scenario:
Workflow starts once item is created employee (Say in a ProductList) for certain Amount.
Manager Approves the workflow.
If Amount is < $5000, email goes to Employee as approved.
If Amount is > $5000, further approval is required. Item goes for further approval to VP and then CEO.
I am getting many examples on workflow, most of the examples are sending just an email based on condition. I need sending for further approval based on condition.
Create a list with the following columns
a. Product Name (Text box)
b. Price(Text box)
c. Mgr approval (choice)
d. Final approval(Choice)
Hide column c & d using JavaScript when user enter the value
a Create a workflow in item created for sending mail to manager
Show the column c using JavaScript or the manager
Create another workflow for send mail to final approval on item edited event after checking following conditions
a. Amount >5000
b. Mgrapproval (c) status is approved
Show the column d using JavaScript for the final approval
You can use simple JavaScript if the mgrapprover and final approver does not change. If these values are dynamic it is better to create a webpart for generating JavaScript by checking the login user group.
I would do the following:
Create a list with your approval items in it
Create an approval request as you have done
Check whether the amount >= 5000
If it is ask for approval from the VP and CEO (follow the same steps as you do for step 1 but this time using VP and CEO prefixes for your variables and collection tasks).
If possible, I'd also reference external lists for the amount to check at, and for the VP and CEO names - so that you dont have to redeploy the workflows when the amount changes or the VP/CEO change.
Theres a good write up of a similar multiple approval SP workflow scenario here
As an Aside, you might not want to send the emails with the task url, I'd suggest coding the actual edit page urls into the email so that users (i.e. Managers, VP and CEO) dont have to view the task, then click edit item, then approve, by viewing the Edit screen you can get the url and input your Workflow TaskItemID into the url directly which will give the end user a better overall experience. Only one button click to approve/reject instead of multiple clicks to just get to the screen.
I did this kind of thing by having a workflow like yours on the first list and when a certain condition is fullfilled(like >5000$), I move the item in another list where another workflow process it for approval like you need to. It may seem like your multiplicating workflow, but I usually prefer to have more pretty simple workflow than one workflow that does a lot of things.