Requirement: 68 words forms being migrated to SharePoint 2013.
Nintex Version: 2013
Case: Each workflow is same.
Issue: Each workflow have emails which needs to send links of current list's display form, edit form or assign flexi tasks notifications. So, can we have one copy of workflow which dynamically sends URLs across lists?
Exploration: Tried re-usable workflow with send and get data. This didn't work as each instance of re-usable workflow have unique GUID. Am I missing anything?
Related
I have a solution in VS2012 with a SharePoint 2013 sandboxed project. I have created some custom workflows in 2013.
What I really need to do is to have an approval workflow to publish content, and send out an email when a new document is approved.
My first thought was to use the OOB approval 2010 workflow and use an event receiver on the list. When an item becomes approved, I would send out an email, but I'm unable to send emails programmatically in SharePoint online.
My second thought was to recreate the workflow in 2013, since I know I can send emails out that way, but it looks like the activities related to content approval were removed for 2013 workflows. I can try and do the approvals via rest calls, but my concern was that my workflow will fire every time the item in the list changes (even if it's not a publish), so I will have to check (in the workflow) if the item is being published or not. This will cause the workflow history for the items to become pretty useless as it will be filled with mostly white noise. Also, as far as I can tell, the checkbox when you create an association for "Start this workflow to approve publishing a major version of an item." does not apply to 2013 workflows.
I believe my best answer at this time would be to create a custom 2010 workflow, but I don't see how I can do that from inside VS2012. Can anyone help me (or maybe suggestion another alternative to achieving my goal?)
You can just turn on the old (2007) approval workflows. It sounds like those might work for you.
This article references how to do that, but in short it is under
Site Settings -> Site Collection Administration -> Site Collection Features -> enable the feature 'SharePoint 2007 Workflows'
Configuring SharePoint 2013 to use legacy workflows
I ended up using an OOB 2010 Workflow and modifying it with SharePoint Designer. Not really the solution I wanted (which was to package ALL of my customizations into a single WSP), but I've spent more time than I should have trying to get it to work.
I`m interested in adding SharePoint Workflow Modification programmatically from my workflow, without using forms.
What i'm trying to achieve - I want to add Workflow modification when user uploads new document version to document library. I have OnWorkflowItemChanged and from there i'm willing to add WF Modification.
Is this possible?
To clarify some things:
I`m writing a custom Workflow in Visual Studio.
What I want is to add items to (SPWorkflowModificationCollection) SPWorkflow.Modifications object. However there is no Add method, but the designed way to add items there is by using Workflow Modification forms.
In this case, i don't want user to use modification form, but i want to add workflow modifications (which will populate the collection AND triger OnWorkflowModified event).
I am not 100% sure what you mean by workflow modification. Do you want to modify the workflow itself from a workflow or just modify a document or item from a SharePoint Workflow?
Regardless, I'll give you the same answer to what was accepted as the answer to a similar question.
Workflow is one of the strong parts of SharePoint. Out-of-the box you or your users can build workflows using the free SharePoint Designer. Depending on your exact requirements this may be good enough.
If you need a more advanced workflow editor then you may want to consider Nintex Workflow or K2. Alternatively you can write your own workflows in Visual Studio or buy 3rd part Workflow Actions for SharePoint Designer.
I have included some useful links below:
Building workflows using SharePoint Designer
Creating workflows using Visual Studio
3rd Part Workflow actions to embed VB or C# directly into SharePoint Designer Workflows. Note that I have worked on this product so consider my recommendation biased ;-)
To preface, I am working with SharePoint Server 2010 Beta 2, Visual Studio 2010 Ultimate RC.
I have built a custom Content Type based on the Item type with a few custom site columns. I also have built a custom Sequential Workflow using Visual Studio 2010. This is a relatively simple workflow that creates a task, waits for the task to complete, sets the workflow to complete. I am able to deploy this workflow to the site collection through VS 2010 deploy (which is pretty nice, btw). The problem I have is that when I try to associate the custom Content Type with my custom workflow, that workflow is not listed in the workflow templates to choose from. There are only the OOTB SharePoint workflows to choose. The kicker is that if I create a list and associate a workflow to that list, my custom workflow is in the workflow template list. This makes sense since at the start of building a custom workflow in VS2010, one of the first questions is whether the workflow is a Site or a List workflow and I selected List. Is the issue that List workflows are not allowed to be associated with Content Types?!?
Thanks.
In your workflow's elements.xml, look for AssociationCategories and change it to ContentType like so:
<AssociationCategories>ContentType</AssociationCategories>
Big thanks to my co-worker, Yves for pointing this out :)
Does anyone know if it is possible to Lookup list data from a different site when creating a workflow with Sharepoint Designer 2007? The Define Workflow Lookup dialog only allows you to pick from lists in the current Sharepoint site you are creating the workflow in.
Ideally I'd like to be able to pick from a list in the parent site, or a site from a given URL (eg. http://myserver/mysite)
You cannot do that with OOTB activities. However you can build a custom SharePoint designer activity to do the task you need. We usually create just a call web service activity and then we call a SharePoint we service we need.
Take a look at this CodePlex project for some custom SharePoint Designer activities.
SPDActivities on CodePlex are very useful. However, if your exact requirements are not covered by any of those activies then you may want to consider embedding c# or vb.net code directly into the SharePoint Designer Workflow (Without resorting to Visual Studio).
I wrote a blog article about how to do it exactly at the following location:
http://www.muhimbi.com/blog/2009/12/embed-c-or-vb-code-directly-in.html
We are customizing workflow approval form to display the associated list item fields. This will help the approver to verify the list item, he is approving.
The approval form will have to be one of 2 flavors.. this is assuming that you are using Windows Workflow Foundation...
InfoPath workflow form and Windows Workflow Foundation - These are the forms that are normally used for MOSS (not WSS) workflows. In order to provide list data you will need to send the list information up to the task form using the ItemMetadata.xml and SPWorflowTaskProperties.ExtendedProperties[]. If you didn't want to send that info you can try to use VSTA in the form and retrieve said information programmatically into InfoPath.
ASPX Form - Not too many people have created custom task forms (your approval form is really a task form). This form needs to be deployed to the _Layouts directory and is quite difficult to create. I recommend searching Robert Shelton's blog as he has a great example of how to create a SharePoint aspx task form.
Ulysses