SharePoint Experts Blog

Author Archive

Call Rest Service via SharePoint Designer or Out of the box workflows vs Plumsail Actions Pack

Probably you are familiar that using SharePoint Designer you can consume SharePoint REST API.

The API is very flexible and allows you to manipulate items, lists and almost every aspect of SharePoint. On the Internet, you can find many articles describing how to use it and how to correctly configure the workflow.

In most cases this will be very simple use cases, I suppose this is because the complexity of the workflow increasing dramatically with number or required requests and processing data.

We are in Plumsail try to simplify things, that is why we added “Get Items by Query” workflow action.

 

Let’s have a look at the following article: Call HTTP Web Service Using SharePoint Designer 2013 (SPD)

A guy describes how to create a simple workflow which gets items from a list and log a Title of each item to the history list.

I reproduced the case and it takes almost half of an hour to create it.

Get Items via REST Service out of the box

 

After that, I installed Workflow Actions Pack and I created the same use case but using actions from Workflow Actions Pack. Of course, it took just 5 mins and the final workflow looks more clear for anyone who has to maintain it in the future.

Get Items via REST API SharePoint Workflow

 

Now let’s imagine that you need to implement more complex workflow, indeed in a production environment, I saw workflows which take 3-5 pages and it’s hard to understand their logic and I do not mention that consultant that creates it costs a lot of money.  Using Actions Pack you can save your time and your money. Moreover, Workflow Actions Pack allows you to get data from another site or even tenant, it opens new possibilities comparing with OOB workflows. 

As a conclusion, I would like to say: – “Do a smart investment!”. The product has a really good ROI.

 

Posted in: Products

Workflow Actions Pack Update v.2.9.0

We are glad to introduce a new version of the Workflow Actions Pack. Below you can see the list of the new features, which were added to Online version.

Send email with attachment

Send an email with attachment – we have made it as simple as it can be.

Send an Email with Attachments

In that case, to send emails will be used our SMTP server.

Together with that for advanced users, you can configure the action for your individual needs and requirements.  

Send an email with Attachments advanced properties

Another amazing feature it is AddItemAttachment. If the option was turned on and workflow works on the list item it will automatically add list item attachments to the email.

Moreover, if the workflow runs on a DocumentSet, it will add all documents from a DocumentSet to the email.

 

 

Copy/Move documents and document sets

We completely rethink the conception of the copy/move workflow actions.

So the basic idea it is minimalism.

As you may see, we added Copy Document Set workflow action, which also can copy all properties.

 

Posted in: Workflow Actions Pack

SharePoint 2013 Designer and Workflow Tips, Tricks & Traps

In this article, I want to share my experience working with SharePoint Workflows via SharePoint Designer. Sometimes it may be very painful, but I hope after reading the article you will not step on same rake.

Do not log Dictionary variable to Log to History

This is very common issue, your workflow just stuck in started state with following error:

Retrying last request. Next attempt scheduled in less than one minute. Details of last request: HTTP InternalServerError to https://plumsail.sharepoint.com/sites/Test/_api/web/lists(guid'04dc3f6a-968e-4ce0-a7cc-10949dfb15db')/Items Correlation Id: f54b9d7e-5242-1408-b066-5239a7b01c0a Instance Id: 967e7b1b-96cd-4fbf-b6d4-4df91199831b 

Invalid text value.

A text field contains invalid data. Please check the value and try again. 
Retry now

It occur because your data is too big. This workflow action can display limited number of symbols. Otherwise such error occurs. As a workaround, you can use Send E-Mail with Attachments (SMTP) instead of log to history.

If you send dictionary by email you can receive it’s structure in JSON format. It is very helpful to understand the structure.

Read more…

Posted in: Products, Workflow Actions Pack

How to Start SharePoint 2013 Workflows on Selected Items

This blog post appeared as an email response to one of our clients, he described very common use case where you have two libraries of documents, the first library where the users works with draft documents and the other library which is stored the final versions of documents. In this case, users want to be able to select finished documents and move it in one click.
Oblivious solution for this is to use a workflow that will move documents to the final document library. But there is one question how we can start the workflow on selected list items? When I was thinking about the answer to that question – I realized that is not as trivial as it seems, because list level workflow can be started only on singl document. How to start multiple workflows on selected documents? In the article, I will describe how you can implement such solution.

I divided this article into three main parts:

  • Get selected items via JavaScript;
  • Start SharePoint 2013 workflow from JavaScript;
  • Add custom button to the list ribbon

Before we start, I want to show what we will get in result. On the figure below you can see the custom button on the ribbon, which will launch a workflows on selected documents.


Read more…

Posted in: Products, Workflow Actions Pack

Deploy custom SharePoint 2013 workflows with site template

It is common scenario when you did some customizations, saved site as template and want to reuse it in SharePoint 2013. Such site templates can include workflows with custom workflow actions. Unfortunately if you save site with custom workflow actions as template and then try to create new site you can receive such annoying error:

Microsoft.Workflow.Client.ActivityNotFoundException:The activity named 'WorkflowXaml_988fe3c3_dc3e_47a9_8ff3_c912c82eb56d'from scope '/spo/216722f1-1dc0-4c6d-aafd-86b12ef60a14/1f87e1ae-da77-44d4-92d1-502507b5f2d4/34ceaf02-5217-46be-a307-e09dd93da230' was not found. HTTP headers received from the server -ActivityId:224e672a-4e00-44ed-8b55-894a059608c2.NodeId:.Scope:.ClientActivityId: f6cadd9c-c011-1000-aa42-85eedd28fc19.--->System.Net.WebException:The remote server returned an error

The reason of such behavior is related to incorrect processing of template by SharePoint 2013. I described it in detail in other my blog article. But this article is not about reasons of such behavior. We created small utility program TemplatePackageFix which fixes site templates with custom workflow actions and allows to reuse them as many times as you need.

We decided to implement such utility because some of our customers had questions about correct site template provisioning. Especially when custom site template included workflow actions from our product Workflow Actions PackRead more…

Posted in: Products, Workflow Actions Pack

Page 1 of 2 12