Workflow status canceled if item is not created by owners - sharepoint

i have a workflow in SharePoint 2013 that starts when item is created in a list.
if the item is created by an owner the workflow runs perfectly.
if the item is created by any other user, the workflow status will be canceled, and one of the owners should start it manually.
please help.
thanks

If this is a SharePoint designer workflow, attempt to use the impersonation step before running any of the steps of the workflow.

Related

Sharepoint 2013: Approval workflow option is not dispalyed

I am trying to a configure the Sharepoint 2010- Approval workflow to the list. I have activated the "Workflow" under site collection features. After enabling, under the "Add a workflow" in list > workflow setting, the template name is not displayed. Kindly help me to enable this approval workflow on Sharepoint 2013.
The issue was due to Microsoft workflow interruption. Check the global admin site in case if you received the message from Microsoft specifying the same.

SharePoint Designer Custom Workflow

I am creating a custom workflow in SP Designer 2013. I have a form that when submitted the workflow status goes to submitted. When a owner of the site goes in to edit the form or review it the workflow status should change to reviewed. If the owner goes in to the form and approves or denies it the status should change accordingly. All I am getting is the submitted status. Here is what I have:
Step 1:
If Continuous Improvement Ideas: Admin Approval is empty
set workflow status to submitted
else if continuous improvement ideas: admin approval equals denied
set workflow status to closed
else set workflow status to approved

how to associate an approval workflow to a custom list using sharepoint designer 2010

I have created an approval workflow in Sharepoint designer 2010. I have created a custom list. I am unable to attach workflow to a list. My "Associate to list" is not in active mode.
Please suggest me and how could I see the workflow result..
If it is a list workflow i.e., it has already been associated to another list, then you will not be able to attach it to another list.
If it is globally reusable workflow, the "associate to list" option would be active.

SharePoint OOTB workflows 'Failed on Start' when started on create but can be started manually

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.

MOSS: Approval Workflow: how to make the document readonly after it has been approved

I am new to MOSS development and while I'm learning it I have a problem waiting to be solved.
We are using the standard approval workflow in one of our test sites just to get the feel of the approval workflow. We have the standard approval workflow in place and working but what has become more desirable is to have the document set to readonly mode after its approval.
What should be my approach to configure/implement this feature?
Custom ItemUpdating event handler on the workflow task list - check the status of the task, and if it is Approved, get the Item object through the task workflow association and adjust permissions on the Item.
Or you start a second workflow - depending on the approval workflow outcome. Create a SharePoint Designer Workflow using the custom activities to set the item permissions.
To set the item permissions download the Useful Sharepoint Designer Custom Workflow Activities
The advantage of this approach is, that you do not need to write code to create an Eventhandler.

Resources