I'm a developer and want to integrate with ServiceNow. Im new to ServiceNow and I have probably a very simple question. I created a workflow in the worflow canvas and validated and published it. When I click the play button nothing happens. Here is the document I followed.
How do I know that the workflow is working? I can't see any animation too.
My current worflow is: Begin->workflow fires when incident state is New or Active. ->End . I created an incident and changed the states to these 2 values, but no luck.
Let me know how to make sure that workflow is working.
Thanks in advance!
Whenever a workflow executes, this is represented as a "Workflow Context." You can look at the status of current or past contexts by navigating to "Workflow" > "All Contexts" in the nav menu.
That menu link will take you to a list of Workflow contexts (table name: wf_context). You can locate your test executions by 2 columns, "Workflow version" and "Related record." The Related record column will have the Incident number that triggered the workflow, and the Workflow version column will have the name of the test workflow you are working on.
Once you open up that record, there's a lot of useful information in there for examining the details of the workflow execution. Among that info is a workflow log, activity history and transition history. As you continue developing your workflow these will provide useful debugging data points if you encounter obstacles.
Workflow is a fairly deep concept, so I recommend glancing at this article as well, once your feet or sufficiently wet.
Workflow Concepts
Related
I am trying to automate my project boards. I would like an action to trigger when someone opens a Pull Request and links it to a issue on the board, then the issue would be moved to "In Review".
I imagine once I trigger by a pull_request, this information would be seen on the given environment variables. But I dumped all of them and I could not find any reference to the issue I am linking and would like to move on the project board.
Can someone give me some light on what I could do to achieve this result?
First you can reference an issue in your commit message described in the documentation. Then you can set up built-in automations for the project board. If you then push something to your repository and create a merge request, the issue should be automatically linked and moved to the column "In Review".
The organization I am with has transitioned to Azure DevOps for source control and for Sprint Management. I am responsible for investigating moving the organization to Azure DevOps for testing off of another solution. There is one question I have received from multiple people after doing some demonstrations that I have not been able to get an answer on.
What I have been asked if the system can do, is that when a Bug is entered during a Test Execution, for it to automatically have the User Story that the script is related to be set as a parent.
For example:
If I have User Story 123, which has a Tested By relationship to Test Case Test1. Test Case Test1 is in Test Plan ABC, which was created with the Area Path of my team and Iteration of the current Iteration. If I create a Bug while executing Test1 (in a Test Suite in Test Plan ABC), it currently adds the Bug to the current Iteration, but under an Unparented story. We would like to see that bug automatically appear under User Story 123.
Is this possible? Thanks for any information regarding this.
I think you can use Create work item task behind your test task in your build/release pipeline.
In this task, you can set the work item link type and target work item.
And other conditions about the work item.
You can set the Control Options as below.
It means, only when the test task has failed, this task will run.
Hops this will help.
So, for anyone else searching, I was able to resolve my issue.
What ended up being the solution was using the Create Test Suite from Requirement option, within a Test Plan. This is a very useful method for our use, as once the Test Suite is setup, and Test Cases which are created with a Tested By/Test Relationship (User case should show Tested By in the Related Work section, the test case will show a Tests entry to the User story) will automatically be added into the Test Suite. Then, when testing, when you create a new Bug from within a Test Execution, will automatically be created with the User Story as a Parent to the Bug.
If I create a new project and select the Agile process, my user stories will be grouped in iterations Eg "MyProject/Iteration 1".
However, If I create the project using Basic process and after the project has been created, changes the process to Agile I can group my user stories by Sprint Eg "MyProject/Sprint 1".
The latter is what I want, however as the process was set to Agile when the project was created (not by me), I'm trying to figure out how to change it to use Sprints as default?
Side note:
I cannot create a new project as I lack privileges
I cannot create a new process as I lack privileges
I cannot change to another process because I've already created a bunch or user stories
Although I can create sprints manually, I want it to be default.
Thank you!
From this document, we can know that iteration and sprints represent the same concept in the agile process.
Define Iteration Paths (aka sprints) and configure team iterations
So if you want to visually use Spirits as the default, you can add a new iteration named Spirit in team configuration, or change the name of the existing iteration to the Spirit style. Then set it as Default iteration. As shown in the following figure:
Because your current project is already Aglie process, the initial display must be MyProject/Iteration 1. If you want to display like MyProject/Sprint 1, you have to modify it later.
There are two ways to change the display: changing the process or manually modifying it.According to your Side note, obviously neither is feasible.
If you really want Spirits as default in agile progress project without any manual modification,you could submit a feature request in our Develop Community site. Our PM and product team will kindly review your suggestion.
There is no way to do this without changing the Process of your project.
I use Query Result tiles in my dashboard to help teammates on multiple projects to quickly view the work that is assigned to them. We used to be able to click on a given task to open the detailed description of said task but now it no longer works. The tile only shows the associated user story and is no longer linking to the detailed view screen.
I have checked the queries used (simple work items and direct link query that shows all tasks assigned to a given user and its associated User Story) and reviewed the latest updates to Azure Devops but I can't find any changes that could affect the expected results.
Sorry about this issue you meet. This is caused by our server. There are some mistake occurred on our side, so that the work item which displayed on dashboards could not be clickable successfully now.
You can follow this ticket which report on Developer Community.
The fixed release has been deployed now, but haven't cover all regions. It may take some time to finish that. Please wait for this fix deploy finished. And if you still have this issue recently, you can vote and comment on Develop Community.
Our product engineers are still focusing on this issue and will help you investigate more.
Can I have guidence for TFS 2010 for the following areas:
What is the correct use of tfs and the properties that are exposed for each backlog item and task for recording of effort so that we report on progress using the burndown charts and can assess velocity.
It is not obvious to us what is the appropriate workflow for raising questions about functionality against tasks / user stories so that the person who needs to answer them can easily find those tasks / stories that have outstanding questions. And for when the question is answered how the person(s) who need to know the answer are alerted that the answer is there. Maybe tfs is not the right place to do this and we should be manually doing this?
Unless you customized something, the report features you are asking about will light up in the reports if you use the field in the Task work item named Remaining Work - update it regularly - daily if possible.
The database most of the default reports use (Tfs_Analysis) gets updated every 2 hours by default. Some of the reports only show a daily roll-up so depending on what you are looking for you might not see changes until the day after.
As for your 2nd question about how to communicate about missing information in user stories, etc.. you should read the Process Guidance for the template that was used to create your Team Project. I'm guessing you are using the MSF Agile 5.0 template, so do a search for that and "Process Guidance." The Process Guidance is basically the instructions for how to use the TFS work items and reports, etc... It can be found online (on MSDN) or by right-clicking on your team project in Team Explorer and choosing Process Guidance from the context menu. I'm answering this from my phone but can include a link to it later if you find this helpful.