Workflow 2013 Breaking Role Inheritance On Workflow Task list

When breaking role inheritance on the out of the box Workflow Task List (2013), a custom workflow is suspended when assigning a task
(System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary. ).
As soon as task list is inheriting permissions again, the workflow is able to assign tasks. (Similar issue: http://social.msdn.microsoft.com/Forums/en-US/8c60da76-8299-436c-8528-802fa5a594c3/2013-workflow-with-unique-permissions-on-task-list-ends-up-suspended).
I have not found a solution to this issue so far.

Same problem. Any solution found?
in2brain

Similar Messages

Need 2 metadata fields from item I am running a approval workflow on to show up on the task list

I have document library "A" that contains many documents with 6 columns of metadata. I have a simple approval workflow for the library that works as it should in functionality. My users would like it if 2 fields of metadata from the items in library
"A" would show up in the Task list so they could track the tasks by the 2 fields. Can anyone point me in the right direction here to make this happen? Working in SP2010 with Designer 2010 and IP 2010.
Thanks

Hi Ross,
According to your description, my understanding is that you want to display two managed metadata fields in the associated tasks created in the approval workflow.
I recommend to edit the approval workflow in SharePoint Designer and new two task fields to display the two managed metadata fields.
Here are the detailed steps:
Open the approval workflow in SharePoint Designer and click Approval in Start Approval Process step.
Click New to create two task form fields in single line of text type.
Click Change the behavior of a single task under Customization.
In Before a Task is Assigned step, select Set Task Field under Task Behavior Actions and then set the newly created task form fields to get the values in the managed metadata fields of current item.
Please refer to the picture below(create a task form field called Managed Metadata for example and mm is the managed metadata column in the list):
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Workflow 2013 change user executing the workflow

In a new workflow 2013, I would like to have the entire or part of the workflow to run under the id of a user that is not executing the workflow. The id of the user would have higher permissions than the user that is actually running the workflow and
would have at least 'edit' permissions. I would like to run the workflow under a different user so that the person that is executing the workflow will have permissions on the custom list that they submitted to the workflow set to view only. Thus
once the permissions on the custom list are set to view only, the workflow would need to run as another user.
Thus can you tell me and/or point me to a link that will display how to execute a workflow 2013 with a different user that did not start the workflow? Basically the workflow would be run by a user that did not start the workflow.

Hi scampsman,
As dmadelung said, Impersonation step is unavailable in SharePoint 2013 workflow, you can create a workflow using SharePoint 2010 platform, and use Impersonation step in this 2010 workflow.
If you want to use the function in SharePoint 2013 workflow, you can use "Start a List Workflow" to trigger the SharePoint 2010 workflow in SharePoint 2013 workflow.
More information about How to trigger a SharePoint 2010 workflow from a SharePoint 2013 workflow, please refer to the link:
http://blogs.msdn.com/b/sharepointdesigner/archive/2012/08/18/how-to-trigger-a-sharepoint-2010-workflow-from-a-sharepoint-2013-workflow.aspx
Best Regards,
Wendy
Wendy Li
TechNet Community Support

Simple 2013 Workflow to break permissions inheritance on a Document Library File?

Anybody got an example of this? Suspect SPD 2013 can't do it and that it must be using VS 2012.
Want a simple solution of a Doc library where users drop files in, but then, users can only View, Edit, Replace and Delete files they created.
============================
Thank You
cyberpine.com

When using a 2010 Workflow you need to add an impersonation step to get the Replace permissions Action. I just tried it with an SPD workflow in my copy of SPO (which has been upgraded to 2013) and it works fine. 2013 workflows don't have an impersonation
step, so there is no replace permissions action. The actions/steps are greyed out unless you've selected an appropriate slot in the designer. Could that be what is happening?
Although there are API available on the SharePoint server to change list item permissions you can only use that in code running on the server, which you can't do in SPO. You wouldn't be able to use this in Azure or another provider. You could
use them in a custom web service created for an OnPrem 2013 environment. For SPO you can only use client side code or web services that already exist. As I mentioned previously the permissions web service doesn't go down to the item permissions
level. I'm also not aware of any CSOM that can change permissions on list items at this point either.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Task Expiry in Workflow 2013 is not available

Hi,
I'm using Designer Workflow 2013, in that i need to Start a Task process. In that there is no option for Task Expiry i can find only Due Date.
In Workflow 2010 there is an option for Task Expiry so if the task is not responded within specified amount of time i can able to perform some operation then it will continue with the workflow. But in Workflow 2013 there is no option for Task Expiry.
Any help will be highly appreciated.
Thanks,
Ahamed

Hi Ahamed,
I still recommend to use SharePoint 2010 workflow instead.
If you want to use 2013 workflow, I recommend to create another workflow and use retention policy to start the workflow when the due date expires.
The workflow can be created like the image below(as only due date needs to be changed, we can update the due date and send notification with the task URL to the user):
Thanks,
Victoria
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Victoria Xia
TechNet Community Support

Workflow 2013 run weekly

I have a workflow 2013 that is started by a custom list when the user hits the submit button. I need to have the workflow run on a weekly basis. The timeframe is based upon the start and end dates that the user originally entered into the custom list.
Thus is there a way to have the workflow run on a weekly basis? Is there some kind of a background workflow 2013 process that can be executed to run the workflow on a weekly basis? In the original workflow, is time a command that will tell the workflow to
run on a weekly basis?
Basically can you tell me how to have a workflow 2013 run on a weekly basis based upon start and end dates?

Hi,
Please refer to the following article.
https://bhandariasb.wordpress.com/2013/06/03/start-workflow-from-custom-timer-job/
or alternate option is you can create a PowerShell Script and use the windows scheduler to schedule the execution of PowerShell script
http://www.thesysadminhimself.com/2013/09/sharepoint-start-workflow-all-items-powershell.html
Please
don't forget to mark it as answered, if your problem resolved or helpful.

Is it possible to maintain a common Task list in a Site?

Hi All,
I have a site call HR ePortal with more than 1 SharePoint-Hosted Apps. These apps having list and workflow. Can I maintain a Common Task List in HR ePortal Site for all Apps? If this is possible where I have to maintain the each Apps List, inside the
Apps solution or should create each Apps list in the site.
If I maintain the Task List in site , is it possible to create workflow with that Task List using visual studio 2012?
Thank you.
S.Shangar

HI,
Yes, you can maintain common task list for apps and it is better to put the apps list in the site and you can access these easily from the app code.
Regarding workflow, yes you can create workflows using visual studio with the common task list.
BR
varinder

Integration between Custom list and task list

Is it advisable to provide solutions for the integration between custom list and tasks list in SharePoint?
I am working on a scenario where the data has to be segregated between multiple lists and there will be transactions among these lists using workflow. Some of the capabilities in Tasks list like due date notifications, calendar, tracking are needed
on the transaction. Since these lists are based out of different content types, is it advisable to choose these lists for solutions?
When we have to make few updates through workflow from custom list to tasks, will there be any problem in the transactions as it is two different content type?
Vijayaragavan, MCTS

Since SPLists and SharePoint workflows don't provide inherent
support for transactions, you have to handle rollback operations yourself.
The easiest way to simulate a transaction is to read in the state of any list item you are changing prior to executing an update, and then write that state back should you detect a failure. It's not a perfect solution, since a sufficiently severe error might
prevent your rollback updates as well. That's the price you pay for not having the data store support transactions.
That being said, while it's true many clients will ask for business critical data to be stored in SPLists, I would argue that it's your job to convince them that it's not a good idea, and that transactional databases accessed over webservices are a much safer
SP compatible way to store important data - from
stackoverflow
[custom.development]

[Workflow 2013] No tasks created (Only the first task)

Hello
I ve created a Sharepoint Workflow 2013 (so using workllow manager) with visual studio 2013 that contains some simple and composite tasks.
On my development environment, all tasks are created and the workflow is well executed and terminated.
On the production server, ONLY the first task is created and there is no errors thrown by the workflow (his status is in progress)
Have you any idea to fix the issue ? Otherwise how can i troobleshoot the behavior ?
Thanks in advance
Anouar
sharepoint 2010

Jarrod B. ha scritto:
> Hi rossi,In any DAQmx application, you can only run one analog input task at a time on one device.
Here is that DAQmxErrChk prints out (only Indoor_Temp, the first task
runs properly); any hint how about I can get the value from each voltage
channel of the same task? I can't use DAQmxReadAnalogScalarF64?
Status Code: -50103
DAQmx Error: The specified resource is reserved. The operation could not
be completed as specified.
Task Name: Relative_Humidity
Status Code: -50103
[Temp.int.: 20 C] [Temp.est.:
-925596313493178310000000000000000000000000000000
DAQmx Error: The specified resource is reserved. The operation could not
be completed as specified.
Task Name: Outdoor_Temp

Role Assignment to Workflow Tasks

Hi Experts,
Any hints on below requirement please :
Details:
1. For a role in transaction PFCG, I don't see the Workflow tab
2. For the same role in transaction SUIM, I can see the Workflow tab and the tasks assigned.
3. Now, I have a list of workflow tasks and I need to assign Role X, Role Y to all of them
What is the correct and best way out to do this
- Role-Task Assignment ::: Is it enough if I add all the workflow tasks in SUIM transaction(workflow tab) for both roles X,Y
or
- Task-Role Assignment ::: Can I assign both Roles X,Y in pftc transaction for each of the workflow tasks
or
- Both need to be done
Thanks in advance ...
~Ali~

Hi Ali,
Answers for your questions:
1. Transfer Missing Elements: YES
With this step, new elements will create in the task container based on the method container elements and creates the binding b/w them. It is better to choose YES and after that, if you dont require the binding, you can delete it for respective elements.
2. YES, we need to follow the same procedure.
3. Basically production system is having the mandatory configurations like RFC destinations and Classify tasks are general, probably no other activities are required.
4. For this, I am also waiting for other folks reply.
Regards,
Murali Krishna.

Item level permission on workflow task List using sharepoint designer 2013

Hello All,
I have created a custom approval workflow. Workflow create a Task in Tasks List. Now suppose A task is assign to user1.
User2 should not able to edit\approve\reject the item.
How to give item level permission using SharePoint designer in SharePoint 2013 workflow.
SharePoint 2013 workflow doesn't have impersonation steps also.
Please suggest how to give permission on task list based on assigned To field.

In order to change permissions on a list item you'd need a sharepoint 2010 workflow according to http://msdn.microsoft.com/en-us/library/jj728659.aspx
Unfortunately this functionality is not available in SharePoint 2013 workflows :-(
The impersonation step still exists, but it is now called "App Step" in the SharePoint Designer 2013 Ribbon. This step is disabled, though, until you activate a web site feature called "Workflows can use app permissions"

Workflow 2013 task list

In a workflow 2013 there is a workflow task list that I would like to ask the following questions about:
1. When I want to access the task list, I do not know where to look for it? Thus can you tell me how to locate the task list? My worklfow 2013 does have stage names.
2. Sometimes when I am testing, I get email messages saying a task you been assigned to a particular person (which includes test accounts). How these email messages being generated? Thus would you show me what I need to look at find find what generates these
email messages?

Hi Wendy,
I assume you are using SharePoint workflow on 2013 platform based on Workflow Manager.
Since 2013 workflow can only be designed in SharePoint Designer, then if we access workflow settings page in Designer, we can open associated task list and history list.
After publishing feature is enabled, you will find a task list named Workflow Task which is the task list of 2013 workflow by default. You can access it via
http://sitename/WorkflowTasks/AllItems.aspx .
With Task action, workflow mechanism will send email notification to task participants, and another email notification will be sent along which you can customized it in workflow design. Here are the references for task action in workflow 2013:
https://msdn.microsoft.com/en-us/library/office/dn551366.aspx
https://msdn.microsoft.com/en-us/library/office/jj614606.aspx
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected] .
Rebecca Tu
TechNet Community Support

Workflows 2013 and SQL Report Services: Configure on Independent Servers or Existing App Servers?

Currently, my SharePoint 2013 Farm has Workflows 2013 and SQL Report Services installed on app servers, along with other applications. Workflows 2013 isn't working correctly (installed prior to my coming on board with the organization), I'm assuming it
is a configuration issue, but rather than re-configure, I've read that is recommended to be a standalone server. It was also recommended by a MSFT rep that our report services have its own independent server. Currently, Report Services is also installed on
an app server that runs other applications on the farm.
Has anyone had any experience with installing Workflows 2013 and/or SQL Report Services on independent vs. existing application servers?
Additionally, my existing application servers have 24 GB of RAM (I believe the recommendation for SharePoint production environments is 12 GB), should I plan for the potentially new servers (Workflows and Report Services) to also have 24 GB of RAM? Not really
sure if it will be needed if they have dedicated tasks.
Thanks for any input you can provide!

It entirely depends on load. WFM will work just fine installed on servers in the SharePoint farm. SSRS preferably should go on the end-user facing servers for better performance.
The questions you're asking are all "it depends" :)
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Related Item link is broken in DispForm.aspx for a task in Workflow Tasks list if file name contains " ' " (single quote)

Description:
We have created a custom workflow in Microsoft Visual Studio 2013 and SharePoint 2013. This Workflow is associated with a Document library.
This Workflow starts as soon as any new item is created OR updated in Document library and creates a Task in Workflow Tasks list.
Related Item link is not working in following scenario -
Upload a file that contains “ ' “
in its name, in a document library
Navigate to Workflow Tasks list
Open View Item form (DispForm.aspx ) of Task Created by workflow then click on link in Related Item fields
OUPUT:
Related Item link truncates after “ ' “
Eg.
Original Link: http://<Site URL>/Documents/te'st.txt
Related Item Field: http://<Site URL>/Documents/te
Is this known bug in SharePoint 2013 OR any hotfix available to fix it.

Hi,
As I tested per your description, I can reproduce the issue as well.
From what I have found out, it seems SharePoint resolve single quote into different code in different place. During the test, if I set Task Name to Document Name, single quote will be resolved to ' , if I set some field to Document encoded URL, single
quote will be resolved to %27 . For now, I haven't found out any article talking about this issue.
As workaround, we may find out a way to change the Related Item field. However, it is OOB field in workflow task (SharePoint 2013) content type, and this content type cannot be modified in form.
I'd suggest you add new column to get document url and place in the form in Task content type settings.
Regards,
Rebecca Tu
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Workflow 2013 is not removed from library after retract

Hello.
I created a test workflow 2013 in VS 2013, while adding this workflow to the project I selected document library for it and also selected pre-created tasks and history lists.
I deployed the worklow from VS project menu, then started it manually in the library, worflow completed successfully.
After it I called "Retract" from VS project menu, it completed without errors, but teh workflow stayed in library. Then I deployed it again, went to the library workflow settings, removed the workflow, retracted it again using VS project menu.
But, now when I go to library - workflow setings - add workflow, I still can see there my workflow option (though the solution is retracted and feature is removed from site collection).
What should I do to remove it?

OK, here are the log entries for solution deploy and retract:
Updating SPPersistedObject SPFeatureDefinition Name=FeatureDefinition/15/90531efa-67c7-45e6-8272-a061cc856924. Version: -1 Ensure: False, HashCode: 21145693, Id: 643508a2-1da2-4b52-99d5-1855c34bbee6, Stack: at Microsoft.SharePoint.Administration.SPPersistedChildCollection`1.Add(T newObj, Boolean ensure) at Microsoft.SharePoint.Administration.SPFeatureDefinitionCollection.AddCore(SPFeatureDefinition featdef, SPSite site, String solutionHash, Boolean fForce, Boolean fDoValidation, String pathToFeatureAndElementManifestXsdFile) at Microsoft.SharePoint.Administration.SPFeatureDefinitionCollection.AddInternal(String relativePathToFeatureManifest, Int32 compatibilityLevel, String pathToFeatureAndElementManifestXsdFile, Guid solutionId, String solutionHash, SPSite site, Boolean force, Boolean fDoValidation, SPFeatureDefinitionContext featureDefinitionContext) at Microsoft.SharePoint.Administration.SPSolutionPackage.AddFeatureDefinitions(SPFeatureDefinitionCollection featdefCollection, SPFeatureDefinitionContext context, Boolean force, SPSite site, SPWeb web, Int32 compatibilityLevel) at Microsoft.SharePoint.Administration.SPUserCodeSolutionPackage.AddFeatureDefinitions(SPSite site, SPWeb web, Boolean force, SPUserSolution solution) at Microsoft.SharePoint.SPUserSolutionCollection.<>c__DisplayClass7.<AddOrUpgrade>b__6() at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode) at Microsoft.SharePoint.SPUserSolutionCollection.AddOrUpgrade(SPUserCodeSolutionPackage solutionPackage, Int32 solutionGalleryItemId, SPUserSolution existingSolution) at Microsoft.SharePoint.SPUserSolutionCollection.AddOrUpgrade(SPListItem item, SPUserSolution existingSolution) at Microsoft.SharePoint.SPUserSolutionCollection.Add(Int32 solutionGalleryItemId) at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) at System.Delegate.DynamicInvokeImpl(Object[] args) at Microsoft.VisualStudio.SharePoint.Commands.SharePointCommand.Execute(SharePointContext sharePointContext, CommandFlags flags, Byte[] serializedParameter, ISharePointCommandLogger logger) at Microsoft.VisualStudio.SharePoint.Commands.CommandManager.ExecuteCommand(SharePointContext sharePointContext, String commandId, CommandFlags flags, Byte[] messageBody) at Microsoft.VisualStudio.SharePoint.Commands.RemoteCommandService.ExecuteCommand(String commandId, CommandFlags flags, Byte[] messageBody)
Feature Installation: Installing Feature 'TestWorkflows_Feature1' (ID: '90531efa-67c7-45e6-8272-a061cc856924') into the farm.
Entering monitored scope (Feature Installation: Installing Feature 'TestWorkflows_Feature1' (ID: '90531efa-67c7-45e6-8272-a061cc856924') into the farm.). Parent No
Feature Installation: Calling FeatureInstalled method for Feature 'TestWorkflows_Feature1' (ID: '90531efa-67c7-45e6-8272-a061cc856924', Compatibility Level: 15).
Leaving Monitored Scope (Feature Installation: Installing Feature 'TestWorkflows_Feature1' (ID: '90531efa-67c7-45e6-8272-a061cc856924') into the farm.). Execution Time=0.163841146451115
Feature Activation: Activating Feature 'TestWorkflows_Feature1' (ID: '90531efa-67c7-45e6-8272-a061cc856924') at URL http://devsrv.
Calling 'FeatureActivated' method of SPFeatureReceiver for Feature 'TestWorkflows_Feature1' (ID: '90531efa-67c7-45e6-8272-a061cc856924').
Feature Activation: Feature 'TestWorkflows_Feature1' (ID: '90531efa-67c7-45e6-8272-a061cc856924') was activated at URL http://devsrv.
Leaving Monitored Scope (Feature Activation: Activating Feature 'TestWorkflows_Feature1' (ID: '90531efa-67c7-45e6-8272-a061cc856924') at URL http://devsrv.). Execution Time=1961.3532869094
Feature Deactivation: Deactivating Feature 'TestWorkflows_Feature1' (ID: '90531efa-67c7-45e6-8272-a061cc856924') at URL http://devsrv.
Calling 'FeatureDeactivating' method of SPFeatureReceiver for Feature 'TestWorkflows_Feature1' (ID: '90531efa-67c7-45e6-8272-a061cc856924').
Feature Deactivation: Feature 'TestWorkflows_Feature1' (ID: '90531efa-67c7-45e6-8272-a061cc856924') was deactivated at URL http://devsrv.
Feature Uninstallation: Uninstalling Feature 'TestWorkflows_Feature1' (ID: '90531efa-67c7-45e6-8272-a061cc856924') from the farm.
Entering monitored scope (Feature Uninstallation: Uninstalling Feature 'TestWorkflows_Feature1' (ID: '90531efa-67c7-45e6-8272-a061cc856924') from the farm.). Parent No
Feature Installation: Calling FeatureUninstalling method for Feature 'TestWorkflows_Feature1' (ID: '90531efa-67c7-45e6-8272-a061cc856924', Compatibility Level: 15).
Leaving Monitored Scope (Feature Uninstallation: Uninstalling Feature 'TestWorkflows_Feature1' (ID: '90531efa-67c7-45e6-8272-a061cc856924') from the farm.). Execution Time=0.0583684084232099
Deleting the SPPersistedObject, SPFeatureDefinition Name=FeatureDefinition/15/90531efa-67c7-45e6-8272-a061cc856924.
Looks OK.

Workflow 2013 Breaking Role Inheritance On Workflow Task list

Similar Messages

Maybe you are looking for