Skip navigation
All Places > Getting Started > Blog
1 2 3 Previous Next

Getting Started

458 posts
graham

Counting Records

Posted by graham Oct 12, 2018

I wanted to be able to do a Group Count on a set of items in a library (I actually wanted to save the values and counts to a list so that I could attach a chart control – but that’s another story).

There is no way of doing a Group By in the Query List task, so I had to come up with this.

Retrieve all my key values into a collection, then create a list of those unique key values

Iterate through the unique values and remove them from the original list – the number of items matching the key value is the number of items removed from the collection – the difference between the counts before and after the deletion.

In pseudocode, the process is this

QueryList : get all ‘key values’ in range into collection AllKeys

Collection: Remove duplicates from AllKeys into collection UniqueKeys

ForEach string Key in UniqueKeys

Collection: Count AllKeys into number Total

Collection: Remove by value Key from AllKeys

Collection: Count AllKeys into number Count

Math: Total Count into number KeyCount

{do something with Key and KeyCount}

EndLoop

There are many requirements where Approvers need to upload attachments on task form, which need to be uploaded on main item instead of task form.

I have achieved it using REST and JS.

 

Major Steps :

1. Create RichText Control on Text Form to show attachment and add attachment button.

2. Add JS which use REST API to add attachments

 

Requirement Result Screen :

 

On click of Show Attachment button, it loads attachments of Related item with add attachment link as shown below

on Add attachment it opens below screen and we can upload attachment by selecting file.

 

Solution

1. Drag a Task on workflow. Click on Edit Task form.

2. Add a Rich Text Control on form as shown in below screen

3. Edit Properties of Rich Text add below HTML in Rich text as shown below 

<input id="btnAttach" ="return checkSPLoad('');" style="width:180px;" type="button" value="Show Attachments" />

<div id="divAttachs"></div>

<div id="addAttachmentDiv" style="display:none;">Select a file<br />
      <strong>Name </strong>

      <input class="attachmentButton" id="attachmentButton" multiple="multiple" name="attachmentButton" ="attachFile(this);" type="file" />

</div>

<div class="nf-attachmentsLink" id="idAttachmentsLink" ="showAttch();" style="height:17px;display:none;">

      <img  />

        <a class="ms-addnew" href="#">Add Attachment</a>

</div>

 

4. Click On Save.

5. Select Form Setting in ribbon and add javascript.

6. Paste below script in custom javascript section.

var pollSP;  var hostweburl='';
var appweburl='';
var listname='ListName';//Include list name 
var itemid=ID;  //Include reference of ID of item.

var file;
var contents;
var itmUrl='';  
function checkSPLoad(callType){
 NWF$('#btnAttach').hide();
    if (clientContext){ 
        window.clearInterval(pollSP); 
        hostweburl = decodeURIComponent(getQueryStringParameter("SPHostUrl"));
        appweburl = decodeURIComponent(getQueryStringParameter("SPAppWebUrl")); 
        var layoutsPath = "/_layouts/15/"; 
        var scriptbase = appweburl + layoutsPath; 
        itmUrl=hostweburl+"/Lists/"+listname+"/Attachments/"+itemid;
        if(callType=='Post')
        {
               NWF$.getScript(scriptbase + "SP.js", function () {
                            NWF$.getScript(scriptbase+ "SP.RequestExecutor.js", execCrossDomainRequest);
               });
        }   
      else
        {
                  NWF$.getScript(scriptbase + "SP.js",   function () {
                            NWF$.getScript(scriptbase+ "SP.RequestExecutor.js", execCrossDomainGetRequest);
               });
        }
    } 
 
    function execCrossDomainRequest() {  
        var contents2 = _arrayBufferToBase64(contents);
        var executor = new SP.RequestExecutor(appweburl);             
        var digest =     NWF$("#__REQUESTDIGEST").val();  
        executor.executeAsync(  
          {         
            url:appweburl +   
            "/_api/SP.AppContextSite(@target)/web/lists/getbytitle('"+listname+"')/items("+itemid+")/AttachmentFiles/add(FileName='"+file.name                   +"')?               @target='" +      hostweburl + "'",   
            method: "POST",   
            body: contents2 ,  
            binaryStringRequestBody: true,
            contentType: "application/json;odata=verbose",         
            headers: {            "X-RequestDigest": digest, "Accept": "application/json; odata=verbose"},                      
            success: function (data) {  
                   NWF$('#addAttachmentDiv').hide();
                   NWF$('#attachmentButton').val('');
                   execCrossDomainGetRequest();    NWF$('#idAttachmentsLink').show();
            },  
            error: function (err) {  
                var data=JSON.parse(err.body);
                ;
                   NWF$('#idAttachmentsLink').show(); 
                         NWF$('#addAttachmentDiv').hide();
                            NWF$('#attachmentButton').val('');    
            }   
        });                             
    }
   
 function execCrossDomainGetRequest() {  
       var executor = new SP.RequestExecutor(appweburl);             
        NWF$('#divAttachs').html("Loading...");
        executor.executeAsync(  
            {         
             url:     appweburl + "/_api/SP.AppContextSite(@target)/web/lists/getbytitle('"+listname+"')/items("+itemid+")/AttachmentFiles?@target='" +   
                         hostweburl + "'",   
             method: "GET",   
             headers: { "Accept": "application/json; odata=verbose" },                   
                success: function (data) { 
                    parseAttachment(data);
                             NWF$('#idAttachmentsLink').show();
                },  
   error: function (err) {  
    var data=JSON.parse(err.body);
     ; NWF$('#btnAttach').show(); 
    }   
   });                             
 }
}
function getQueryStringParameter(paramToRetrieve) {   
    var params =   
        document.URL.split("?")[1].split("&");     
    for (var i = 0; i < params.length; i = i + 1) {   
        var singleParam = params[i].split("=");   
        if (singleParam[0] == paramToRetrieve)   
            return singleParam[1];   
    }   
}
function showAttch()
{
 NWF$('#addAttachmentDiv').show();
 NWF$('#idAttachmentsLink').hide();

function parseAttachment(vdata)
{
 var html='';
 var data=JSON.parse(vdata.body);
 var items=data.d.results;
 for(i=0;i<items.length;i++)
 {
  html+='<a href="'+itmUrl+'//'+items[i].FileName+'" target="_blank">'+items[i].FileName+'</a><br>';
 }
 NWF$('#divAttachs').html(html);
}
function f"font-size: 12px;">    contents = event.target.result;
    checkSPLoad('Post');;
}
function attachFile(event) {
    var i = 0,
    files = event.files,
    len = files.length;
 if (files.length > 0) {
        file = files[0];
        fileName = file.name;
        var reader = new window.FileReader();
        reader. f"font-size: 12px;">        reader. = function(event) {
            console.error("File reading error " + event.target.error.code);
        };
        reader.readAsArrayBuffer(file);
    }      
    return false;
}
function _arrayBufferToBase64(buffer) {
    var binary = '';
    var bytes = new window.Uint8Array(buffer);
    var len = bytes.byteLength;
    for (var i = 0; i < len; i++) {
        binary += String.fromCharCode(bytes[i]);
    }
    return binary;
}


 Note : Update list name and id(Add reference from Item section) in top of script.

7. Save and close form.

 

Publish workflow and test.

 

Happy Nintexing.

Hello Everybody,

 

In calculated field have formula "userProfileLookup(Current User,"PreferredName")" is it possible to somehow transfer this information to field Single Line Textbox.

I already try to set this same connected field also make this solution Can't populate text control with calculated value 

but it doesn't collect any data to this field.

Is it some different solution for this ?

Dear all:

I have been very confused about this topic for months:

  • How to navigate from a parent form to child form and come back?
  • How to navigate from a child form to a new one child form keeping the parent link?
  • How to validate child form data before come back in both cases?

I think I have now a good approach to do it without javascript. 

 

How buttons work

First of all, I would like to describe how buttons are working under my understanding, in the case of validation and redirection:

Save and submit button / Save button:

Both buttons have redirection parameter. You can build the URL dynamically, using a list field value and run-time functions. You can't use calculated fields or control values, this is a very important point.

In the case of validation, both buttons can validate data, including list required fields and validation rules in the form.

 

Save and continue button:

Save and continue button hasn't redirection parameter. After saving data, the action is refresh page and you are in the same form again. 

In the case of validation, only list required fields are validated, NOT the rules in the form.

 

Cancel Button

You can redirect as Save and Submit button, Data will be not saved and of course, there is not any validation.

 

Keeping in mind that only Save & Submit button allow us the whole validation, and the limitations with redirection building (as far as I know), here is the solution:

 

Parent ID to new child form

 

To relationship parent and child, you need to pass the parent ID when you redirect to child form. I assume the parent element is previously saved (this is mandatory for my strategy), so parent ID exists in the ID field. The ID argument is included at the end of the URL string, something like that:

http://Mysite/Lists/MyChild/NewForm.aspx?ParentId=ID

 

NewForm.aspx?: To call a new child form

ParentID: the parameter name to pass in the query string

ID: The element property, in this case, the ID field

 

I use a button (Save and Submit) called "Nuevo Hijo" to do it in my Parent form, using the dynamic URL in the redirection (sorry in Spanish):

 

(As shown in the picture, the child list is included in the parent form)

 

I would like to remark that:

  • Data in the parent form will be saved and validated before navigation
  • The parent ID will be used to come back and to record it into child list element to make the relationship between parent and child.

 

Parent ID to an existing child form

 

In this case, you can not use a button. Instead of it, you select "Edit" from the menu of the selected element in the included Sharepoint list:

 

You can't pass the Parent ID using this method, but don't worry because you will have recorded it into child element previously.

 

Working into child form

 

Storing the Parent ID

The first thing to do into the new child form is to get the Parent ID from the URL string, using a calculated field:

 

 

  • Formula: you get the parent id value from the URL string using the fn-getquerystring function
  • Connected field: the field name into the child list to store the Parent ID
  • Formula calculation ONLY in the new mode. Because if you are editing the child you have the Parent ID  recorded yet and you will not send from Parent form again.

 

Save and Submit Button and return to the parent form

 

When you finish the edition of the new child, perhaps you want to come back to the Parent form. To do it, we use a save and submit button, including a dynamic redirection URL string as:

 

fn-if(Is New Mode,Site URL/Lists/MyParent/EditForm.aspx?ID=fn-GetQueryString(ParentId),Site URL/Lists/MyParent/EditForm.aspx?ID=Parent_Id)

 

First of all, there is a conditional function that defines if the form is in a new mode or not, checking the value of Is New Mode Function.

  • In case of a new mode,  you define the URL taking the Parent ID who is the URL passed from the Parent form fn-GetQueryString(ParentId)
  • In case of not a new mode, you define the URL taking the Parent ID from the Parent_Id field value (that you have stored using the calculated field when you was in new mode)

As you are using Save & Submit button, first of all, data validation happens, then saving and finally redirect to the parent form

 

Save and Submit Button and open a new child form (keeping the parent ID in the URL string)

 

If you want to open a new child form, you only need to change the destination URL in the previous formulae:

 

fn-if(Is New Mode,Site URL/Lists/MyChild/NewForm.aspx?ID=fn-GetQueryString(ParentId),Site URL/Lists/MyChild/NewForm.aspx?ID=Parent_Id)

 

You can repeat this action as much as you want in order to create multiple child elements and finally come back to the parent form.

 

That's all. Any comments are welcome, of course, this is only an approach, for sure will be better solutions.

 

Have a nice workflow day! 

This works with on-prem Nintex Workflow 2013

Problem:  Upon archiving a document I use workflow to update the date/time field of when the archive happened.  When user wants to un-archive the document, I need to clear the date field to display as empty (or null).

 

Resolution

  1. Create variable vDateArchivedDate as Date and Time with blank default date
  2. Use Convert value action input "1/1/0001" and store in variable vDateArchivedDate
  3. Use Set field value to update the date column with workflow data > vDateArchivedDate

Download

 

Changes

  • Not Applicable

 

Bug Fixes

 

Source Code

technunes

LAR, doce LAR

Posted by technunes Jul 9, 2018

If you are wondering what “lar, doce lar” means, this is the exact Portuguese translation for “home, sweet home”. Obviously, the context of this article has nothing to do with the pleasure of being returning home, but the he Lean, Automate and Robotize (LAR) approach can and should be just as sweet and can also avoid some painful experiences in the future.

Before we get deeper into the topic, bear in mind that LAR is the result of my own experiences around automating business processes, and it is not a known term in the community. While I do not have the ambition to push one more acronym into our work routine, I do hope, for the sake of security, efficiency and cost reduction, the approach gets implicitly adopted as a best practice.

There is of course a bunch of articles mentioning that the processes should be optimized before being automated, but with the hype around Robotic Process Automation (RPA), we need to revisit the subject as RPA can also offer a risk for your process automation initiative. After all, your competitive edge hinges not on whether you automate, but how you do it.

So, let’s get some definitions straight:

·        Lean (in a service context) is a process optimization methodology that focuses on improving the effectiveness and efficiency of a process by eliminating activities that do not add value to the customers and the product.

·        Automation of business processes is a technology-enabled approach that is performed to achieve digital transformation or to increase service quality or to improve service delivery or to contain costs.

·        Robotic Process Automation is a computer software or a “robot” to capture and interpret existing applications for processing a transaction, manipulating data, triggering responses and communicating with other digital systems.

An analogy that I like to use when comes to business processes is that a business process is like a road through the mountains and, due to people, systems and procedures, it is full of curves and ups and downs.

The goal of the process optimization is about creating a bridge that will connect the start to the end of the process in the most efficient way. 

In a complex scenario however, this business process can involve ERP systems, legacy systems, office tools and many more. Altogether, this can also offer some change management challenges.

In addition, business will depend on IT to build this bridge and what supposed to be simple, can turn up to be a very sophisticate project, leading to delays, huge implementation costs and frustrations.

As Mike Fitzmaurice would say: in the best of all possible worlds, we would be able to get the requester and the developers a mind meld, but life is not like star trek and mind meld is not real.

The RPA can solve this problem by keeping the process as it is, but let robots to drive the “cars”. Robots can at some level, respond to events just as humans would.

This is all great, but more often than we think, a hybrid approach would be the most appropriate. While we all know that the integrations with an ERP system may bring the complexity of a project to high levels, and many legacy systems does not offer a proper API that can easy out a possible integration, there are parts of the process that can and should be optimized in a proper way. Nintex technologies empowers users to achieve just that, avoiding the IT bottle neck.

The RPA approach should not be considered the answer for everything and a more efficient approach would be the combination of the best of both worlds. For example, by replacing the excel spreadsheet with a proper digital form (mobile enabled) and avoiding the back-and-forth of emails through a proper workflow around a form. 

Lean and automating are very connected and they overlap in many levels because it often involves a process optimization in a digital format. The initiative of automating a process, like introducing a digital workflow, most likely show opportunities to enhance the process itself. In the same way, the initiative of enhancing a process will frequently result on some sort of automation adoption. The robotizing part is connected with the automation because it offers a mechanism of interaction with digital systems in an automatic way, but does not attempt to substantially change the AS-IS process. It is also important to notice that LAR is part of the continuous improvement process defined in Lean.

The fact that RPA does not attempt to change the AS-IS process, gives the idea that the Robotic Process Automation is always an easier, faster and more cost efficient than any other automation approach. This is however not always the case.

What if building the proper bridge did not require IT muscle? That’s where Nintex Technologies come in place.

The scenario below shows the process around receiving an offer, creating a P.O. and receiving an invoice.

·        The requester asks the supplier to send an offer.

·        The supplier sends an offer (email text, pdf, word, excel or even PowerPoint).

·        The offer is validated by the requester.

·        The offer is sent to the internal responsible to create the P.O.

·        The P.O. is created in SAP and sent to the supplier.

·        The supplier will then send the invoice.

This could eventually been addressed by EDI (electronic data interchange), B2B systems or API calls, but it is difficult to expect that all business partners from different sizes, regions and segments can easily adopt such approach. The Robotic Process Automation would then be good candidate to automate this process.

However the “Read document/ extract data” part of the process can be quite challenging because RPA tools does do magic. PDF is a business standard document format and it would be fair to demand the offers to be sent on this format. With that in mind, a robot can be configured to read the offer from the offer repository and using some intelligent OCR and text analysis, figure out who is the supplier, the total amount for the offer and basically transform all unstructured or semi-structured data into structure data. The problem here is that the PDF contained the offer can be formatted in several different ways and it is unlikely that the RPA tool would be able to get the data in a trustful way, unless it attempts to use a 3rd party product like Abbyy to achieve that, which would raise the complexity and the operational cost.

So, let’s revisit the process and apply LAR into it.

At the very start of the process, there is an exchange of email between the requester and the supplier in order to get the offer. The supplier sends an email with the offer attached. The offer document is in a semi-structured format and, as we have seen earlier, it implies some challenges to our automation with the RPA tool.

A way to optimize the process would be to eliminate the email exchange and establish a way to collect the structured data.

Using Nintex Workflow cloud, a business user can easily create an online responsive form to handle the offer submission and the workflow to handle the approval form.

The offer form can be divided into sections. While the Supplier and Offer sections collects the master data for the offer document, the Info and Signature sections support the overall process.

The workflow engine would consume this request and handle the approval of the offer. Additionally it is possible to connect to the cognitive services for text analysis and data classification. 

 

In our example, we capture the sentiment of the comment provided in the Info section. In case the comment is something positive like “20% discount is already applied”, the process will continue in one path of the workflow. If a negative message is provided, like “the offer is only valid until the end of this week”, then the process will follow another path in the workflow.

Using Nintex DocGen, a well formatted document is generated. This document can be the trigger for the RPA robot to start the P.O. process. Alternatively, the Robot can be called directly from the workflow as the orchestrator exposes a web API.

The overall architecture is represented on the image below:

 

 

A solution like the one described in this article is achieved with a no-code approach and can be delivered by business users in a matter of hours. RPA is an excellent technology but should not be considered the answer for all the automation initiatives.

LAR will support the creation of the proper bridges when is feasible and let the RPA do what RPA is good at – to take the robot out of people.

Even a short workflow can generate quite a few variables. When you assign a variable to tasks, the names are presented in alphabetical order. The variables list itself displays the order in which they were created. This makes it difficult to find a particular one to delete for example while refactoring or just coming up for a name for a new variable.

It was such an exercise that prompted me to write the attached script which sorts the variables into order, either by Name or Type and Name.

After exporting the workflow to the filesystem, the script edits the workflow and always writes it to Sorted.NWF – so that the original file is preserved should you need to revert to it.

Trying to use pure xml defeated me, so I used the brute-force method of extracting the WorkflowVariables section and converting it to an xml object, sorting it and pasting it back into the workflow file.

Usage:

Assume the script is in the same location as your downloaded .NWF file

.\Sort-WflowVariables.ps1 .\MyWorkflow.nwf

Will sort the variables in name order

While

.\Sort-WflowVariables.ps1 .\MyWorkflow.nwf -ByType

Will sort the variables first into their type and then into order of name

This can then be imported back into the designer where you will see the variables listed in the order requested.

As ever with scripts from the internet, please review its contents to ensure that you are happy to run it in your environment.

Share&Enjoy

Ever wondered how to display SQL table inside your Nintex Form? Indeed, there is the “SQL Request” action, but it only allows you to show data from database as a dropdown, list of options, etc… and always – just a single column.

However there is an easy solution for that. The approach I am using includes usage of the “FOR XML” command in a SELECT statement (source). It is available in SQL Server starting from version 2008. It returns data from a query using an XML format, concatenated in a single row, in a single column. Perfect format to parse it!

Step by step

1. First prepare your SELECT query. Mine is for example:

  1. SELECT TOP(1) (SELECT name, lastname, email, role
  2. FROM users
  3. RIGHT JOIN roles ON roles.Id = users.roleId
  4. ORDER BY lastname ASC
  5. FOR XML) as datatable FROM users

With such statement I am sure, that I will receive just a single row and column, that will return the data in a proper XML format. Each row will be built using the following structure:

  1. <name>value</name><lastname>value</lastname><email>value</email><role>value</role><name>value</name><lastname>value</lastname><email>value</email><role>value</role>...

Put the query in the “SQL Request” control inside your form:

SQL Request action Nintex Forms

Set the field not to be visible. It is not going to be used directly.

2. Now add a “Calculated Value” control. It will be used to get the output from the “SQL Request” and parse it into a valid table. I am using the following formula to achieve it:

  1. '<table class="dataTable"><thead><tr><th>Name</th><th>Lastname</th><th>Email</th><th>Role</th></tr></thead><tbody>'+replace(replace(replace(replace(SQL REQUEST CONTROL NAME, '</role><name>', '</td></tr><tr><td>'),'\<\/(?!td|tr)[a-zA-Z]+\>\<(?!td|tr)[a-zA-Z]+\>','</td><td>'), '</role>', '</td></tr>'), '<name>', '<tr><td>')+'</tbody></table>'

It simply creates a ready to use HTML table. It replaces ending and starting XML tags to starting and ending <tr><td> tags (to mark start and end of each row).

3. Next define a CSS styles for your table. I used the following page to create a set of CSS: https://divtable.com/table-styler/ 

Done!

The table is ready to be shown:

HTML table out of SQL table

I hope this can be find useful for you.

Hello!
 

In my job I’m doing lots of bits and pieces, tweaks enhancements etc to SharePoint solutions I've built using Nintex forms and workflows among other things. I thought to myself I should record the things I do in a central place rather than them getting lost in various emails, tickets, thoughts, phone calls etc.! I started with a simple excel spreadsheet but then thought, why not create a sharepoint list and basic form that I can quickly add to…

 

 

 

 

Why would I use it? To log things in case changes I make break later down the line, weekly meetings, to show what I'm doing \ done to my manager and for my Appraisal perhaps. It evolved a bit as well from my original idea. I added a status field allowing me to tag items as in progress, that I can complete or add comments to at a later date. The workflow updates the item with comments and closing date. It's also been shared with everyone and a simple page created to show todo and completed items.

 

 

 For reporting I've connected it to excel. My favourite simple and quick reporting method for all things SharePoint.

 

 


So this is a really simple solution using a basic list with a Nintex Form and Workflow attached. The buttons on the form control what the workflow will do.

List, Form and Workflow attached...

 

 

 

T

For a long time, we have been plagued by times in InfoPath forms jumping forward by an hour during daylight saving time after amending the metadata fields.

Investigation shows that the datetime value written back to the form contains a modifier telling SharePoint that the time is recorded as being GMT (and thus an hour needs to be added to make it ‘correct’ again).

Date field in InfoPath form

<my:StartDate>2018-05-23T00:00:00Z</my:StartDate>

The solution was to use Nintex to create a workflow that rewrites the date fields after change to remove the ‘Z’ character.

The workflow could either run on any change – or fine tune it to run only when one of the affected fields change value

The action is to

  • Retrieve the field value from the xml document
  • Test if it contains a ‘Z’
    • If it does, write it back without the ‘Z’

As it runs immediately after a change, it is worth starting the workflow with a ‘Commit pending changes’

The first step is to read the xml document associated with the current item, so insert a Query XML task – ensure the source is the Current Item; return the result as Text, to a temporary string variable

In the Output, set ‘Process using’ to XPath and click the XPath Builder button and navigate through your form’s xml to the field

When you reach it, select it and click the Apply button and something like this will be returned

 

Now test strTest in a Run If

Within the Run If, add an Update XML task

You can copy/paste the field reference from the Query XML task

You then replace the node content with the item value for the field, replacing the ‘Z’ with a blank

Note that the FormatDate function returns the date/time in the same format as that stored within the xml.

Now repeat this for each affected field.

graham

Nintex Workflow – Fast Loops

Posted by graham Jun 12, 2018

Recently I needed to create a schedule of dates, one week apart. I created a loop and added 7 days in each iteration. I noticed it took a very long time, so I added a Log in History task in the loop and saw that each iteration was taking 5 minutes. I realized that this was down to ‘Safe Looping’.

This protective feature places some safety measures against the hazards of an infinite loop by adding a hidden delay..

I didn’t want to disable this option, mainly because of the maintenance overhead involved, so I looked for another option.

I realised that the Collection iteration (For Each) didn’t have any such restriction, so all I needed was to create a collection with the number of entries that I wanted to loop for.

The Regular Expression task with the Split operator is the easiest way to create a collection; it simply splits text based on a character. All I had to do was to create a string with the right number of delimiters.

This is where I got the idea for this article https://community.nintex.com/community/build-your-own/blog/2018/06/08/nintex-string-repeat.

Now, as n delimiters will create n+ 1 entries, we need to reduce the number of delimiters by 1

Initialising the string to a non-delimiter will ensure that the string is padded to length ‘Iterations’ containing n-1 delimiters.

Regular Expression

For each

 

We place the retrieved value in TempStr variable and ignore it.

Calculate date:

Here’s where we add the recurrent +7 days added on each loop

The final workflow

 

 

I set the Iterations variable to be a startup parameter and set it to 10

Here are the results from the history - as you can see, it all executed immediately

 

Time

Event

Message

11/05/2018 10:49

Workflow Comment

MyDate=18/05/2018 10:49

11/05/2018 10:49

Workflow Comment

MyDate=25/05/2018 10:49

11/05/2018 10:49

Workflow Comment

MyDate=01/06/2018 10:49

11/05/2018 10:49

Workflow Comment

MyDate=08/06/2018 10:49

11/05/2018 10:49

Workflow Comment

MyDate=15/06/2018 10:49

11/05/2018 10:49

Workflow Comment

MyDate=22/06/2018 10:49

11/05/2018 10:49

Workflow Comment

MyDate=29/06/2018 10:49

11/05/2018 10:49

Workflow Comment

MyDate=06/07/2018 10:49

11/05/2018 10:49

Workflow Comment

MyDate=13/07/2018 10:49

11/05/2018 10:49

Workflow Comment

MyDate=20/07/2018 10:49

 

 

graham

Nintex String-Repeat

Posted by graham Jun 8, 2018

I recently needed a String-Repeat function in a workflow. But it doesn’t exist.

Or does it?

Looking at the inline function specifications, I saw that the PadLeft function (and PadRight) adds a number of characters to a string, until the string length is the desired number of characters long.

If you needed just a specific number of characters (lets say ‘-‘ chars), then the following

fn-PadLeft(-,15,-)

 

Will result in a string of 15 ‘-‘ characters

Now, you cannot tell it to pad out with a string of more than 1 character (it actually returns the text of the function definition when you try), so you need to be a little more clever to give a string of 15 repetitions of ‘Graham’ for example

We create a string of 15 ‘-‘ characters then replace each ‘-‘ with the longer text that we want to repeat in a RegEx task.

graham

Workflow Approvals Dashboard

Posted by graham Jun 5, 2018

This article is not strictly Nintex, as it could apply to any workflow engine.

We manage our Change Control process using InfoPath forms and Nintex workflow.

For a management overview and reminder for when approval request emails are missed, we needed a dashboard page that would show all outstanding approvals and those assigned to the current user.

Two methods were identified to provide this functionality – the Nintex webparts and custom list views of the WorkflowTasks list.

This is a summary of our requirements

Requirement

Nintex Webpart

Custom Listview

Display the ID of the item being approved

N

N

Link the item being approved to open in the browser

Y

N

Group all approvals for each item

N

Y

Ability to Approve from the page

Y

Y

Ability to Delegate from the page

N

Y

 

Whilst the Nintex webpart allows the current user to respond to a task if s/he is the one to whom the task was assigned, the Terminate Workflow option is visible and could cause problems - and the Delegate user was not available at al.

Our first attempt to solve this was to add a column to the WorkflowTask list and have a workflow paste in the relevant information each time a task was created. Big mistake – we had no end of ‘Task is locked by a workflow’ errors and resulted in delays of hours before an approval could be given.

Returning to the List Views, because the views are grouped, we did not want the name of the grouping field to be repeated in each group, so we used the JScript found here -> http://bistesh.blogspot.co.uk/2014/04/sharepoint-20132010-remove-columns-name.html and added it to a CEWP. We used this code as a basis to edit the url of the Related Content to use the InfoPath form server.

It also amends the standard message:

'There are no items to show in this view of the "Workflow Tasks" list. To add a new item, click "New".'

To show

'You have no outstanding approvals'

 

We wanted to be able to show the ID of the related content.

Research indicated that SP 2013 held a field called WorkflowItemId – a Content Query webpart (CQWP) was created using the debugging style to retrieve a field of this name and found it existed in SharePoint 2010 and was populated with the ID value.

Debugging XSLT

<xsl:template name="debugCustomStyle" match="Row[@Style='dCustomStyle']" mode="itemstyle">

<!-- shows all the fields supplied and their names  -->

<xsl:for-each select="@*">

F:

<xsl:value-of select="name()" />

=

<xsl:value-of select="." />

+

<br />

</xsl:for-each>

<xsl:call-template name="repeatstr">

<xsl:with-param name="num" select="20" />

<xsl:with-param name="str" select="'-'" />

</xsl:call-template>

<br />

<!-- shows all the nodes supplied and their names  -->

<xsl:for-each select="//*">

F:

<xsl:value-of select="name()" />

=

<xsl:value-of select="." />

+

<br />

</xsl:for-each>

<xsl:call-template name="repeatstr">

<xsl:with-param name="num" select="50" />

<xsl:with-param name="str" select="'='" />

</xsl:call-template>

<br />

</xsl:template>

 

The Property CommonViewFields of the webpart source was set to include all the wanted fields (it is imperative that the case matches the definition, otherwise it will not be recognised).

<property name="CommonViewFields" type="string">Title;WorkflowName;WorkflowLink;AssignedTo;Related Content;WorkflowListId;WorkflowItemId</property>

The next thing was to show it in the view – this field is not selectable as it is hidden. The answer was to export the ListView webpart (see Export a List Webpart at the end) and edit the embedded view

<property name="XmlDefinition" type="string">&lt;View Name="{CE1736B1-205B-42D4-99B6-AE5D5F723D18}" MobileView="TRUE" Type="HTML" Hidden="TRUE" TabularView="FALSE" DisplayName="" Url="[redacted]" Level="255" BaseViewID="1" ContentTypeID="0x" ImageUrl="/_layouts/images/issues.png"&gt;&lt;Query&gt;&lt;GroupBy Collapse="FALSE" GroupLimit="30"&gt;&lt;FieldRef Name="WorkflowItemId"/&gt;&lt;/GroupBy&gt;&lt;OrderBy&gt;&lt;FieldRef Name="WorkflowItemId" Ascending="FALSE"/&gt;&lt;FieldRef Name="AssignedTo"/&gt;&lt;/OrderBy&gt;&lt;Where&gt;&lt;Eq&gt;&lt;FieldRef Name="WorkflowOutcome"/&gt;&lt;Value Type="Text"&gt;Pending&lt;/Value&gt;&lt;/Eq&gt;&lt;/Where&gt;&lt;/Query&gt;&lt;ViewFields&gt;&lt;FieldRef Name="WorkflowItemId"/&gt;&lt;FieldRef Name="WorkflowLink"/&gt;&lt;FieldRef Name="WorkflowName"/&gt;&lt;FieldRef Name="Created"/&gt;&lt;FieldRef Name="AssignedTo"/&gt;&lt;FieldRef Name="LinkTitle"/&gt;&lt;/ViewFields&gt;&lt;RowLimit Paged="TRUE"&gt;30&lt;/RowLimit&gt;&lt;Aggregations Value="Off"/&gt;&lt;ViewStyle ID="17"/&gt;&lt;Toolbar Type="None"/&gt;&lt;/View&gt;</property>

 

When html un-encoded and reformatted, it looks like this

<View Name="{CE1736B1-205B-42D4-99B6-AE5D5F723D18}" MobileView="TRUE" Type="HTML" Hidden="TRUE" TabularView="FALSE" DisplayName="" Url="[redacted]" Level="255" BaseViewID="1" ContentTypeID="0x" ImageUrl="/_layouts/images/issues.png">

   <Query>

     <GroupBy Collapse="FALSE" GroupLimit="30">

         <FieldRef Name="WorkflowItemId" />

     </GroupBy>

     <OrderBy>

         <FieldRef Name="WorkflowItemId" Ascending="FALSE" />

         <FieldRef Name="AssignedTo" />

     </OrderBy>

     <Where>

         <Eq>

           <FieldRef Name="WorkflowOutcome" />

           <Value Type="Text">Pending</Value>

         </Eq>

     </Where>

   </Query>

   <ViewFields>

     <FieldRef Name="WorkflowItemId" />

     <FieldRef Name="WorkflowLink" />

     <FieldRef Name="WorkflowName" />

     <FieldRef Name="Created" />

     <FieldRef Name="AssignedTo" />

     <FieldRef Name="LinkTitle" />

   </ViewFields>

   <RowLimit Paged="TRUE">30</RowLimit>

   <Aggregations Value="Off" />

   <ViewStyle ID="17" />

   <Toolbar Type="None" />

</View>

 

This makes it a lot easier to read, understand and amend – this will need to be re-edited to remove unnecessary whitespace and carriage returns, then html encoded (or the tag can be set up to be a CDATA entry).

I recommend that you use the field Status as a substitute field, then find/replace it with WorkflowItemId – this should prevent errors when editing the encoded xml.

So the new field WorkflowItemId is added to the view fields and used as the Group By value.

After the webpart(s) have been re-uploaded, if you Edit Webpart and Edit current view, the fields will appear in their correct locations.

The My Approvals – with no assigned approvals

All Approvals

The full jscript is shown here

_spBodyOnLoadFunctionNames.push("HideHeaders");

 function HideHeaders() {   

    var elem;   

    var elements = getElementsByClassName(document, "td", "ms-gb");

    for (var i = 0; i &lt; elements.length; i++) {

        elem = elements[i];

        elem.childNodes[0].childNodes[1].nodeValue = "";

        elem.childNodes[1].nodeValue = elem.childNodes[1].nodeValue.replace(':', '');

        elem.childNodes[2].href="/_layouts/formserver.aspx?xmllocation=" + elem.childNodes[2].href + "&openin=browser";

        elem.childNodes[2].target="_blank";

   }

   

    elements = getElementsByClassName(document, "td", "ms-vb2");

    for (var i = 0; i &lt; elements.length; i++) {

        elem = elements[i];

        if (elem.childNodes[0].nodeName == 'A') {

            elem.childNodes[0].href="/_layouts/formserver.aspx?xmllocation=" + elem.childNodes[0].href + "&openin=browser";

            elem.childNodes[0].target="_blank";

       }

   }

   

    elements = getElementsByClassName(document, "td", "ms-vb");

    for (var i = 0; i &lt; elements.length; i++) {

        elem = elements[i];

         if (elem.childNodes[0].nodeValue == 'There are no items to show in this view of the "Workflow Tasks" list. To add a new item, click "New".') {

            elem.childNodes[0].nodeValue='You have no outstanding approvals';

       }

   }

}

 

/*

Written by Jonathan Snook, http://www.snook.ca/jonathan

Add-ons by Robert Nyman, http://www.robertnyman.com

*/

function getElementsByClassName(oElm, strTagName, strClassName) {

    var arrElements = (strTagName == "*" && oElm.all) ? oElm.all : oElm.getElementsByTagName(strTagName);

    var arrReturnElements = new Array();

    strClassName = strClassName.replace(/\-/g, "\\-");

    var oRegExp = new RegExp("(^|\\s)" + strClassName + "(\\s|$)");

    var oElement;

    for (var i = 0; i &lt; arrElements.length; i++) {

        oElement = arrElements[i];

        if (oRegExp.test(oElement.className)) {

            arrReturnElements.push(oElement);

       }

   }

    return (arrReturnElements)

}

 

 

Export a List Webpart

You want to export the list webpart to your pc, to upload on a different site/page or edit it, but the export webpart option is not available.

 

This is where we get funky …. Still in edit page mode, in the browser toolbar, click Tools | F12 Developer tools. Now select the area on the page holding the webpart

 

Search for the text allowExport within the html

See the =false after it, double-click on it and change that to true

Now the Export option is available on the webpart

 

Save it to the pc, then you can edit it and Add webpart and upload the saved one

How to add Save as Draft button functionality and users can modify their own items? 

  1. Please follow this post for Save as Draft button functionality, thanks Dan Stoll for wonderful post.
  2. Under Version settings, set "Content Approval" to Yes and set "Draft Item Security" to "Only users who can approve items (and the author of the item) ". This would help us to hide own draft item from others.  
  3. Under Advanced Settings Set Item Level permissions to "Create items and edit items that were created by the user".
  4. Now Build you Nintex Form by adding two Calculated fields and Save as Draft button.
  5. Set 1st Calculated field Value 
  6. Set 2nd Calculated field Value to  [if IE 9]  [endif] 
    userProfileLookup(Current User, "PreferredName") 
  7. You many hide both these fields under banner by using "bring to front" functionality.
  8. Add Set as Draft button
  9. Add rule and set on 'Save as Draft' and 'Save and Submit' buttons and set following condition - 
  10. Save these changes and publish it. 
  11. Create the workflow for the list.
  12. Add 'Set a Condition' action and set condition 'If Draft field value is equal to Yes' 
  13. If action value is NO add 'Set Approval Status' action to Approved.
  14. Add End Workflow action.
  15. Save these changes and publish it. 

Filter Blog

By date: By tag: