I'm having issues with my SP Online Workflow. Setting up a custom list for Time-off requests. Person puts in request, task is assigned to their manager, then manager either approves or denies request, then informs the requester of the outcome. That whole part works great.
I've added an option for the requester to cancel the request. If the request has already been approved by the manager then it sends an email to the Manager, HR, & requester saying the request was cancelled. This part works fine.
The part that I'm having issues with is if the request hasn't been approved/rejected by manager and requester cancels. It's not sending out the email to manager and changing the Workflow Status.
I have it configured exactly like the cancel workflow if it's been approved. What am I missing here? Any help would be greatly appreciated.
Here are some images of the entire workflow and the Workflow lookup in question:
Entire Workflow
Workflow Lookup in Question
Thanks
I think if one of your condition complete, it should just go the next stage in your case which is end of workflow. When you condition is satisfied, you don't need to go through all other if anymore.
If request cancel equal no
If outcome equal approved
Go to next stage
If outcome equal rejected
Go to next stage
Else
If taskStatus equal not started
Go to next stage
If taskStatus equal completed
Go to next stage
I switched not started and completed. Because logically speaking you should go not started first.
Related
I have a Web activity that performs a GET operation to an endpoint. I have set it up to do something On Failure (which works just fine) and another set of action upon Success. But this last part gets skipped entirely even though the output of the Web action is Succeeded.
Here is shown the succeeded status and my config
enter image description here
I tried removing and re-adding the On Success connector, but yielded no different results.
Based on your flow, it would never proceed ahead:
Because as per your logic to proceed to the Set run time, Web activity 1 AND Web activity 2 should be success but that can never be the case since web activity 2 can be a success only if web activity 1 has failed thereby not proceeding further.
The below blog explains how to handle this :
https://datasharkx.wordpress.com/2021/08/19/error-logging-and-the-art-of-avoiding-redundant-activities-in-azure-data-factory/
Both dependencies of set runtime status cannot end as succeeded. You need to use a combination of skipped/completed states: https://learn.microsoft.com/en-us/azure/data-factory/tutorial-pipeline-failure-error-handling
From the pipeline image , I think it should move on with success .
Can you please cross check what is status code of web activity and is it returning something back ? Is the status code be 2xx ? If I were you could have tried to check with the "Upon Completion" option and see it works .
I have made some basic approval workflows for custom records and things like estimates, but they have all been single approver or sequential. Does anyone have some advice on how I might achieve a parallel/asynchronous approval workflow?
I figured the workflow would add the approvers to a workflow variable list, send out an email to each approver and as the emails came back it would remove the people from another list awaiting approval. Once the list was empty it would transition to the next state. Seems like a simple concept but I can't get a workflow to add multiple items to a list...just set a static value which is 1 employee.
Thoughts?
Without more detail it's difficult to give detailed answers but something like the following is the idea:
You'll probably need a custom record that is linked as a child to the record to be approved.
Some workflow action scripts will likely be required to get this working.
When the main record enters the approval state a workflow action script will get the list of approvers and for each create a custom (approval) record linking the approver, approval status and record to be approved.
Another workflow will handle the single record approval of the new approvals record (e.g. sending out the original notice email, cancelling the workflow if the parent is rejected)
A scheduled transition on the main workflow will run searches to transition the main record when all approval records are approved or any approval record is rejected.
I am trying to create a workflow which pulls from a saved search.
The saved search has the criteria:
Awaiting Support Reply - is true
Stage - is any of Open, Escalated
The result I am getting are not as expected:
I post a ticket from my work account (it goes into the list).
A member of the service desk team (handle cases) responds and it disappears from the list.
I reply from my work account and it does not reappear in the list.
I have also tried this from an external email address in case its picking up my internal address as a member of staff or something weird?
Can anyone please advice? Does the person replying have to be a customer in the system for it to work?
It is based on the case status. Configure what you want it's value to be for each case status you have configured.
Setup -> Support -> Case Statuses
I have the need to create a workflow that will begin when a user submits an infopath form to a document library. Some fields will be extracted from this form to build the workflow.
Steps:
Notify the form submitter's manager and request that they approve or disapprove.
One or more other users will be notified and requested to approve or disapprove the submitted form. If any of them reject the form, the original requester should be notified and requested to re-submit the form.
I can make a workflow for step 1 and then check the value of that field in the task to see if it's either approved or disapproved before moving onto the next step or not.
The issue I'm having is how to check whether someone has rejected or approved in the 2nd step, since there could be multiple users.
Any help is greatly appreciated
After step 1, you can track the workflow in the "workflow Tasks" list, i.e., you can get who rejected it, when they did it and why they did it(if you have a notes/reason column).
If you/your company can afford to buy a third party tool like nintex/bamboo workflow conductor/k2, this approval process come out of the box. They are a bit expensive though
Seeing if anyone else has had this problem and a resolution to it.
I have a visual studio sequential workflow on a list (not a library) which does NOT use tasks, the approval process is done through the Approve/Reject OOTB buttons on the list item. The approval is a 2 stage approval, whereby if the 1st stage is completed (via clicking the Approve OOTB button), i reset the ModerationInformation.Status from Approved back to pending then send an email to the 2nd stage approver.
My problem is, when i set the the ModerationInformation.Status back to Pending from Approved so there is never an approved version, the Creator loses permissions to view the item, and i get the "cannot find item" error from SharePoint for the person who created the item. The 1st and 2nd level approvers and anyone with approve rights CAN still see the item.
Some more background information. the code i am using to update the moderationinformation is
I get the properties from the workflow event and get a hook into the listitem
properties.Item.ModerationInformation.Status = SPModerationStatusType.Pending;
properties.Item.Update();
can anyone help.
Try using properties.Item.SystemUpdate(); this prevents SHarePoint from triggering any attached EventReceivers etc. I've had the same thing happen also. IMHO this is related to the fact that the item goes into update mode, then SharePoint basically has taken control over the item (seeing as workflows are usually run as the System account) but still sends you back to the the return url (i.e. the EditItem page of the list).
Since SharePoint is probably still doing work on the item (and when you use item.Update() it goes through all events etc. etc.) you cannot open it anymore, because you are not the system account.
When SharePoint finishes (after sent the emails etc.) the item is accessible by users again.
Like I said, I had the same thing happen during long running (i.e. longer than 2 to 3 seconds) EventReceivers / Workflows.