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
Related
Could you please let me know if there is a way to get an email alert if a schedule is created or a change is done to the existing schedule on Azure Data Factory Pipelines? This requirement is to monitor any schedule changes/ new schedule creations happening in the production environment and restrict them if done without proper approval in the project.
I tried using Azure log analytic workspace to achieve this requirement but the existing ADF log tables(ADFActivityRun, ADFPipelineRun, ADFTriggerRun) do not have any such information holding to write query (maybe am missing anything). Please let me know your views.
Many thanks in advance.
Thank you
For Roles and Permissions in ADF, you need Contributor role to create, edit, and delete data factories and child resources including datasets, linked services, pipelines, triggers, and integration runtimes.
You can create custom rule for a group where users can only monitor a data factory (or factories) but can't modify it.
You can refer this third-party tutorial on how to Create Azure Custom Reader Role for Data Factory and assign the role to a user whom you just want to give read permission.
For alerts, you can use Azure Monitor service to monitor and create alerts for your Azure Data Factory actions.
To get started, simply navigate to the Monitor tab in your data factory, select Alerts & Metrics, and then select New Alert Rule.
Give a name to your rule. Provide the severity to the alert. Add criteria to create a alert. There are plenty of scenarios available in the provided in-built criteria list. Then click on Configure notification.
The Configure notification allows you to choose options like Email, SMS, Azure notification and Voice call. You can choose multiple options as per your requirement.
I am working on Ax2012 workflow. I need to know about the table in data dictionary where all the information of configuration of the workflow stores. I know I have to trace many tables to get all the information i.e users , Final Approver , Comments , Description, User whom which workflow are assigned , Workflow Steps , Sequences of the workflowItems etc. I need to know tables from which I can get this Information.
I need all the information of the workflow.
Workflow Assigned to the users.
Comments when workflow Submitted
Comments when some accept the workflow
Workflow Descriptions
Workflow last Approval
User Who submit the workflow
All the paths in the workflow of the configuration
like
1st path(Start---->condition------>True Condition approval)
2nd path(Start---->condition------>false condition approval)
Thanks For helping me out.
Here is the Tutorial of getting all possible paths of workflow configuration
https://github.com/SohaibAnwaar/Ax-2012-Tutorials/tree/master/AX/july/18%20July
Tutorial of getting all the information related to the workflow in the form
https://github.com/SohaibAnwaar/Ax-2012-Tutorials/tree/master/AX/july/13%20july
Details of the Workflow
When creating a Purchase Order (PO) from a Sales Order (SO) in NetSuite, desire to only populate the PO->ItemList with Items from SO which are set to a specific Item->Location even when they share Preferred Vendor.
How can we achieve this? Thinking perhaps a Workflow can check the ItemList when the Create PO link is clicked on an Item.
Our solution ended up being to identify the items which were not to be added to the PO. Then we set the quantity to 0 and added a User Error message upon saving if they were still on the PO. This could be achieved via some scripting, though this was sufficient for our needs with this workflow process.
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.
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.