I'm wanting to create an intake form that will create a new work item on a Azure DevOps board. Right now I've got a Microsoft Forms form create and have lightly tweaked the pre-made Power Automate script that is provided for this purpose.
Right now when somebody submits the form a new work item is created with a few text variables from the form incorporated into it and an email is sent to the requestor letting them know the form was submitted.
There's a few features that I want to incorporate but haven't figured out yet:
Provide a way for the requestor to attach files to the form and have them appear as attachments in the ADO work item. Such as if there is already some documentation for what is being requested that the implementing team would benefit from having.
Include the work item ID from ADO in the email confirmation that is sent back to the requestor.
Provide a way for the requestor to check on the status of the work item after they have submitted the request.
Can these things be done using Microsoft Forms > Power Automate > Azure DevOps? If not does anybody have a better solution for creating an intake process that ultimately creates a new item in ADO? Thanks!
Related
We have a travel request application. where a user submit a request which should go into 2 stages of approval process before it gets Final Approval.
Now we did the following:-
Create a SharePoint list which contain those fields; Title, Description, StareDate, EndDate, FirstApproval (the requestor direct manager), SecondApproval (the requester regional approval), Statues (system-generated with those options; open, first-approved, second-approved, Final-Approved).
Power Apps, which send emails to the first-approval and the second-approval users , and show-hide the Approved & Reject buttons based on the item status.
Power Automate,to set item-level permissions, so for example when the item needs first-approval only the approval's direct manager can edit the item, while all stakeholders can read-only.
now the process is not 100% secure, as a requestor using API call or using SharePoint built-in forms, can easily create a new request and define its status as Final-Approved. so in other words the requestor can bypass the Power Apps business logic. so how we can secure our process? so if an item has a status = "Final-Approved", then we can 100% sure that it actually went through the 2 approvals users?
One Approach i am thinking of, is as follow:-
To create additional SharePoint list >> which stores the ItemID + ItemStatus.
Grant all users Read-Only on this new list while grant the service account Contribute.
Update this new list from Power automate Only. so for example only if the submitter's direct manager did the approval, to change the status inside the new list to First-Approved, and so on.. Also only if the submitter's regional manager approve the request + there is already an approval from the direct manager to change the status from First-Approved to Second-Approval.. so what ever the status is inside the new lit i can be sure that it has not been hacked, as end-user will have read-only on this new list.. can anyone advice please?
Thanks
I believe this question is not unique to you, many SharePoint developers need to make specific configurations or use some artifices to ensure a certain process developed in SharePoint.
Using exclusive/custom permission control into List and uses the PowerAutomate layer to conntrol List Item permission only to approver will secures some update from Rest API, for example.
If you want to block New Insert items and/or block Update items by PowerApps, you can substitute the instruction into "OnEdit" and/or "OnNew" events using ResetForm(SharePointForm1);; RequestHide();; with this instructions in these events block some user to create or update SharePoint Items.
Into SharePoint list settings, in advanced settings, you can disable attachments, disable comments in list item, disable search, disable quick edit, disable launch form in dialog.
I think that's all.
I have an Azure DevOps porject where we are collaborating internally with Azure-Boards.
We have some tasks/bugs that we share with external users i.e. vendors who do not have access to our Azure-Boards/project. We do not want them in there either.
Right now people are copy/pasting stuff from work items to email and then sending them to intended person. I am looking for something that can allow us to export work item content in an email client or just allow us to share one work item only via email.
Any tips or suggestions will be appreciated.
Thanks a lot.
Based on my test, we could not email a work item to an external user account from Azure DevOps directly.
For your requirement, you could select the work items to be sent out in "Query" and then in Query" select "Export to CSV", you can download the excel of the work items and email the CSV excel to the intended person.
Hope it's helpful to you.
I'm using the SharePoint Three-State workflow for a complete and then validate scenario on an InfoPath form. A web service creates the instance of the InfoPath form in the library. The idea is that the workflow will get a particular user to complete the form and then gets a manager to approve it. Simple stuff really.
The workflow fails to start unfortunately. The log shows an argument exception when it tries to start the workflow. Strangely it runs fine when manually started so that rules out the association data being incorrect. I've also tried this with other OOTB workflows such as Approval. I've thought it might also be the creation of the item through the web service but then it all works in my development environment.
I'm hoping someone might be able to contribute what I'm forgetting to check.
What identity is your workflow attempting to start under? If it is the SharePoint System Account, that account cannot start declarative workflows, as documented in this SharePoint Designer Blog post on MSDN.
This same problem impacted one of our workflows, where a web part programmatically created a list item and our workflow was set to trigger on item create and update actions. Manually creating items or manually running the workflow worked because it happened under our personal credentials.
Our solution was to simply create a service account in AD that the web part could impersonate. Once the list items were no longer being created under the System Account, the workflow worked as expected.
If you are receiving an argument error, I would check that the workflow is not referencing a field that would not be populated at the time of creating the list/library item. If you reference something like the ID field or a calculated column this field would not be available.
I have created one custom list.
whenever user add entry to it then email should be triggerd to the manager and the user who has added new entry.
I am using Sharepoint 2007.
Please help.How to do this?
There is more than one way to send that email.
I'd recommend to create a EventReceiver or a workflow.
See How to: Create an Event Handler Feature, Sharepoint Workflow Development (2 part question) and Good online sources to learn Sharepoint Development?
You can override the item added event to capture the information about the item being added and use SMTP mail to send the mail to multiple users.Also, you can use the SPUtility.SendEmail function provided by Sharepoint.
I am new to sharepoint. I am using sharepoint 2007. I have a following requirement.
1) Custom list has various fields ... Requestor, Application Name, Reason, etc..
2) When person fill out the form (custom list). It will send a notification to Approvers for review and based on Request action : Approved --> It will send an e-mail notification to specific group.
I have a setup a document approval workflow on custom list. Workflow works fine but I don't know how to send an e-mail notification based on workflow status : Approved. I have tried to create a another workflow using Sharepoint Designer 2007 but didn't work.
I would like to know whether it is possible without doing any programmatic way ? I would appreciate your reply.
Thanks in advance.
This is more like a SharePoint Designer Workflow, which responds to actions and rules.
You can get an introduction here
follow the steps ,these are the main steps you can have a try:
Create workflow attach to the list and start it manually & auto
start it when a new item is created & auto start it when an item is
modified.
Add Collect data from a User action. Click data and add a choice field (named it approval, give two choices: approve, reject)
in the custom task wizard. Output to Variable:collect
Add a new step, Conditions: if Variable:collect equals to Approve Actions: Send email to Created by
Collect (main manager) data from a user. Output to Variable:collect1(similar with step 2) Conditions: if
Variable:collect1 equals to Reject Actions: Send email to
Created By.
Add new step similar with step 3. Send approve email to Created By when Variable:collect1 equals to Approve or send reject
email when Varible:collect1 equals to Reject.
here is one of bolg which also you can refer
http://www.gandhipritesh.com/2009/07/create-custom-approval-workflow-using.html