Nintex Worflow Size increased? Interesting find regarding Nintex Workflow exponential increase in file size

Thought of sharing an interesting fact which I discovered recently regarding how a Nintex workflow can swell in physical size. If this happening for your workflow better check the reasons mentioned in this post. Recently, in one of my project I faced an issue of a Nintex Workflow bringing down the server to its knees while running or even just saving it in Nintex WF designer, because of its sheer size. It grew to a whooping 6.5 MB in file size.

To know the size of your workflow just export the .nwf file and check the physical size of the saved file.

How it happened?
It is a standard approval workflow with 5 different task forms and around 150 fields in the list. While developing the task forms after 2 task forms the workflow size increased to 2.5 MB which is way above and beyond the ideal limit of a workflow size. I couldn't figure out myself that why was it happening. Tried to work around by reducing some fields from task forms but of no help. Raised this with Nintex support and finally got to know the issue.

The issue was the task forms targeted for other devices getting added while accidentally clicking on tablet/smart mobile layout button.

Reason for the dramatic increase in size

Increase in workflow size was due to accidentally clicking on the tablet and mobile layouts in the Request Approval action task form. Separate versions of task forms got added in background for tablets and mobile within the Approval action. In total there were 3 task forms added for desktop, tablet and mobile. Then this approval action got copied and pasted over and that is why the workflow increased in physical size.

There can be x number of reasons for having a Nintex workflow increase in physical size and accordingly different resolutions based on the reason. This is one of the case.

What is the resolution?
To resolve this issue all you need to do is to delete the extra task form layouts from the Approval Action Task Form. Select the layout where the green plus sign is not shown and you don't need that layout and select "Delete Layout". This will remove the extra task form created OOTB by Nintex and hence reduce the size of the workflow.

I hope that someone can save time and energy in figuring out the reason of increase in workflow size, if the .

Happy Workflow-ing!!

How to enable radio button custom validation in Nintex Form e.g. one selection among two groups of radio buttons

Recently I had to achieve custom validation for Radio button option selection among two groups of radio buttons on a Nintex Form and soon realized that radio button custom validation is not straight forward in Nintex. For example if there is a requirement to select only one option among two radio button groups or as soon as user selects one option in one group the second already selected option in other group gets cleared automatically.

So thought of writing a post that helps to explain the rendering of radio buttons and play around with radio buttons using JQuery on a Nintex Form.

Why it is not straight forward?
Individual radio button ids in a radio button group are defined dynamically hence difficult to capture event of a specific radio button.
Radio button group functionality is handled internally by Nintex code e.g. how to group radio buttons together in one group.

How are they rendered in a Nintex Form?
There are two ways to specify rendering of radio buttons in a Nintex Form.

1. Fixed: Rendered as Table format, in table format each radio button is rendered inside a new table row(TR).
2. Floating: Rendered as Div format, in div format each radio button is rendered inside a span tag.

To have more control client side on radio buttons I would recommend rendering them in Fixed mode that is table mode. It is also the default option in the form as well. Below screenshot shows the scenario having two groups of radio buttons giving laptop and mobile selection however, there can be only one asset type selected by the user at any given time. Since Nintex form is rendering them as separate groups independent of each other hence we need custom code to achieve this.

The first group of radio buttons shown above has rdbLaptopTypes as client id specified in the Nintex Form field and the second one has rdbMobileTypes as client id specified in the field. 


To achieve the above functionality here is the Jquery code:

$(document).ready(function(){
try
{

 var rdbLTypesCount = $('#'+ rdbLaptopTypes +'  tr').length;
 var rdbMTypesCount = $('#'+rdbMobileTypes+'  tr').length;

$('#'+rdbLaptopTypes).change(function(){                ResetRadioBtn(rdbMTypesCount, rdbMobileTypes); 
}); 

$('#'+rdbMobileTypes).change(function(){      ResetRadioBtn(rdbLTypesCount, rdbLaptopTypes); 
});

}
catch(err)
{
  if (window.console) console.log(err);
}
finally{ }
});

function ResetRadioBtn(rowCount, radioButtonName){
for(var i=0;i < rowCount; i++){
if($('#'+radioButtonName+'_'+i).is(':checked')){
$('#'+radioButtonName+'_'+i).prop('checked',false);
}
}
}

This script enables custom validation by clearing off the other group selection made by the user and is independent of the number of radio buttons rendered in each group. This code can be enhanced/altered to achieve a number of functionalities with radio buttons i.e. enable/disable other group, display a specific message on a particular option selection etc.

Another very handy generic function to capture selected value of selected radio among the list of radio buttons rendered in table format is listed below:

function GetSelectedRadioValue(rdbRadio){
var cols = $('#'+rdbRadio+'  td').length;
var rows = $('#'+rdbRadio+'  tr').length;
var radioCount =  eval((rows != 0) ? rows : 1) * eval(eval((cols != 0) ? cols : 1) / rows);

for(var i=0; i <= radioCount; i++){
if($('#'+rdbRadio+'_'+i).is(':checked')){
return $('#'+rdbRadio+'_'+i).val();
}
}
return '';
}

var selectedRadioVal =  GetSelectedRadioValue(radioButtonId);

 Hope this piece of code gives help in dealing with radio buttons on client side in Nintex Forms.

Happy coding!

How to check if user is member of an SP Group in a Nintex Workflow

There is no direct method to determine that if current user who is triggering a Nintex workflow on a list item is member of a SharePoint Group or not. In one of my recent projects I needed that functionality to differentiate set of actions based on user's group membership.A common example is that if user is member of an HR group for purpose of approval.

Achieving this is easy in a Nintex Form by using the built in method "fn-IsMemberOfGroup". This function takes one argument that is the "Group Name" and returns true or false indicating the membership status of current user for given SP group.

Getting the same functionality in Nintex Workflow is not straight forward. It requires couple of actions to achieve the same result. Here is the solution of how this can be achieved in a Nintex Workflow.

1. In Nintex Workflow designer add couple of variables to the workflow

varUserGroupResults     Multiple lines of text
currentUser                     Person or Group
varUserGroupNames      Collection
varUserMemberOfGroup Yes/No

2. Next add "Call Web Service" action and in the action set the following details as shown in the screenshot. This service call calls the usergroup.asmx web service and calls GetGroupCollectionFromUser web method to get all groups to which the user has access to.

The resulting groups are stored in varUserGroupResults in XML format.

3. Now extract the group names as a collection using Query XML action. Add Query XML action to the workflow having following details

Now all the group names are in the collection and easy to iterate through.

4. Add "Collection Operation" action to the workflow to iterate through and compare the value with a group name you want to check against e.g. Approvers Group. If comparison returns true then user is part of that group else not.

The variable varUserMemberOfGroup is a boolean type which shows that whether current user is part of a specific SharePoint group or not.

There might be other ways of achieving the same result but just thought of sharing this as it took me a while to make this working.

Happy Work-flowing!!

Nintex task form - How to redirect user to site home page rather than workflow task list

In Nintex workflows when a flexi task is assigned to any individual or a group in a an email notification informing task assignment is sent to respective user/users that a task requires an action to be performed. When a user actions that task Approves or Rejects the task, be default user is redirected to task list. User lands in the task list all items view by default after action-ing the task.

This is not a desired flow in most of the scenarios. In order to redirect user to the home page of the site after the task action is done here is a quick workaround:

Open "Assign Flexi task" in the workflow for whichever task assignment it is required. In the "Task Notification" tab click on the textarea of the notification message and select Edit HTML source from the ribbon. replace

"{Common:ApprovalUrl}" with  "{Common:ApprovalUrl}&amp;source={Common:WebUrl}"

Now SharePoint will redirect user to the home page after the task item is actioned rather than the task list.

Happy Coding!

How to do email validation in a Nintex Form using JQuery

Custom validations can be achieved quite easily by writing client side code in JQuery in a Nintex Form. There can be a requirement to check all mandatory fields are filled in the form or an email provided is a valid email or a number entered by user is only numeric. SharePoint allows this OOTB by defining the type of field, required or not required attribute of field but those validations happen server side on a Nintex Form. Lot of times we need to have a client side validation to inform the user then and there regarding wrong input. For example if an email needs to be validated using JQuery here are the steps to achieve this in a Nintex Form.

In Nintex Form designer drag the email field to the form from the list columns. In the control settings of the email field go to Advanced section and select "Store Client ID in JavaScript variable" as "Yes" and assign name as "txtEmail" as shown in below screenshot.

After specifying the control client JavaScript variable include the Form.js script file in the form Settings -> Advanced -> Custom JavaScript Includes

/SiteAssets/jquery-1.8.3.min.js

/SiteAssets/Form.js

Add a label control at the top of the form and set the properties of the control as shown in screenshot below. This label control will display the error message to the end user.

Set the button properties of the submit button of the form to following as shown in the screenshot so that the Validate function is called on the click of the button.

Form.js

function CheckEmailAddressIsValid(emailId) {

    var pattern = new RegExp(/^([\w-\.]+@([\w-]+\.)+[\w-]{2,4})?$/);

    return pattern.test(emailId);

};

function Validate()

{

if($('#'+txtTitle).val() == ''){

  $('.lblErrorMessage').text("Please provide title.");

  $('.lblErrorMessage').css('color', 'red');

  $('.lblErrorMessage').css('font-size', 'small');

  $('.lblErrorMessage').css('font-weight', 'bold');

  $('#'+txtTitle).css('background-color', '#FF9999');

           $('#'+txtTitle).focus();

  return false;

}

else

{

$('#'+txtTitle).css('background-color', '#FFFFFF');

}

var emailAddress = $('#'+txtEmail).val();

      if (emailAddress.trim() == '') 

      {

       $('.lblErrorMessage').text("Please provide email address.");

       $('.lblErrorMessage').css('color', 'red');

       $('.lblErrorMessage').css('font-size', 'small');

       $('.lblErrorMessage').css('font-weight', 'bold');

  

       $('#'+txtEmail).css('background-color', '#FF9999');

       $('#'+txtEmail).focus();

       return false;

   }

   else

   {

if (!CheckEmailAddressIsValid(emailAddress.trim())) {

$('.lblErrorMessage').text("Please provide a valid email address.");

$('.lblErrorMessage').css('color', 'red');

$('.lblErrorMessage').css('font-size', 'small');

$('.lblErrorMessage').css('font-weight', 'bold');

$('#'+txtEmail).css('background-color', '#FF9999');

$('#'+txtEmail).focus();

return false;

   }

  $('#'+txtEmail).css('background-color', '#FFFFFF');

   }

}

Here is the output of validation applied for email address on the Nintex Form

We can do any custom validation using this approach like numeric only, date validations or any other kind of validation.

Happy coding!

How to populate select options or dropdown in a Nintex Form 2010 using JQuery

Lot of times in Nintex SP projects there is requirement to populate select options from a non SharePoint data source. Nintex/SharePoint provide this functionality OOTB if the type of field in the list is a lookup field looking up data from another list. However, if the data source is external then it requires a bit of client side code to populate the select options. For example if a form requires Suburbs to be populated in a select option. Here is the sample code to make this working assuming that the suburb data is coming in JSON format from any data source. It can be a REST service.

There are couple of steps required to make this working.

1. In the Nintex Form designer for the given list add a choice form control on the form. In the control settings of the choice control select "Display Format" as "Drop down list". Set "Store Client ID in Javascript variable" to "Yes" and give name e.g. ddlSuburb as shown in below screenshot. This variable will hold the reference to the rendered control on the Nintex Form.

2. Include JQuery and custom script file in the Nintex Form by going to the Form settings -> Advanced -> Custom Javascript Includes section and include following files in the form, or set the actual location of the script files.

/SiteAssets/jquery-1.8.3.min.js

/SiteAssets/Form.js

Custom JQuery Code

Form.js

$(document).ready(function () {

try

{

var data = '[{"ID": "1","Name": "Test Suburb 1"},{"ID": "2","Name": "Test Suburb 2"},{"ID": "3","Name": "Test Suburb 3"},{"ID":"4","Name": "Test Suburb 4"},{"ID": "5","Name": "Test Suburb 5"}]';

var jsonData = JSON.parse(data);

var option = '<option value="">Select Suburb</option>';

$.each(jsonData, function (k, val){

option += '<option value="' + jsonData[k].ID + '">' + jsonData[k].Name + '</option>';

});

  $('#'+ddlSuburb).find('option').remove().end().append(option);

  $('#'+ddlSuburb).change(function() { 

  $('#' + txtSuburb).val($('#'+ddlSuburb + ' :selected').text());

  //alert("You selected: " + $('#' + txtSuburb).val());

 });

}

catch(err)

{

if (window.console) console.log(err);

}

finally

{

//do something

}

});

Output
Custom Jquery code result

In this scenario the suburb data is coming from external datasource in JSON format and is getting populated in a select option in a Nintex Form. When end user selects any option then it is populated in the hidden Textbox under the Dropdown control in the form. This selected value is then saved in the list upon submit.

To select the selected option when the Nintex Form is opened in the Edit mode a CalculateValue type control can be used to get the state of the form i.e. if it is edit mode, new mode or view mode and then option can be selected by writing couple of lines as follows

if($('#' + txtSuburb).val() !== "")

{

    $('#' + ddlSuburb + ' option').each(function() {

    this.selected = $(this).text() == $('#' + txtSuburb).val();

   });

}

In extension to this code we can set cascading select options using JQuery with Nintex to make forms more usable for end users.

Happy coding!

How to integrate Nintex Form with JSON REST service using Jquery

Problem/Requirement: In one of my SharePoint project there was requirement to integrate with ATO (ABN Service) web services to validate ABN number provided by the user to be correct and in active state. User should not be able to provide inactive or expired ABN. The validation required to be done client side, before the Nintex form is submitted and sent for approval. Once the form is submitted, a workflow kicks in and the item goes for approval.

Solution: As a solution to this requirement I developed a JSON REST service which acts as a wrapper between external ATO web service and internal SharePoint Nintex Form. This REST service queries the ATO service, get the response, parses the response into an object and then return the object in JSON format to the caller, which in this case is a Nintex Form. User gets instant validation result in an interactive manner that the whether the number provided is valid or not. The benefits of using this approach are light weight data calls, quick real-time validation and ease of parsing results in JQuery.

Steps:
1. Create a WCF JSON REST service for fetching or validating the data input more detail to create such service is here.
2. Create SharePoint custom list.
3. Access the list in SharePoint and open Nintex Form designer from the ribbon control
4. Add two label controls on the form. Set the "CSS class" value to 'lblMessage' and 'lblInstruction' respectively. These will display message to the user.
5. Include following scripts in the custom JavaScript includes in the form settings. Better to keep these files in Site Assets library to refer them easily on the forms.
      jquery-1.11.1.min.js
      FormScript.js
6. Add a button on the form and set the following properties of the control in Nintex Form.

JSON

{
    "ABN": "12345678910",
    "EffectiveFrom": "27/04/1900",
    "EffectiveTo": "1/01/0001",
    "IsValid": true,
    "Status": "Active",
}

FormScript.js

var ABNValidationServiceURL = "http://xxx-xxx-xxx/ABNValidate.svc";
var abn = $('#' + txtABNNumber).val();

function ValidateABN(){

//support cross domain ajax calls
jQuery.support.cors = true;

//URL of the JSON REST service
var url = ABNValidationServiceURL + "/IsValid/" + abn;


//query ATO service for ABN
$.getJSON(url, function (atoData, status) {
  if(status == "success"){
     if(atoData["Status"] != "null" &&  atoData["Status"] == "Active"){
$('.lblMessage').show().fadeOut(4000, "linear");;
$('.lblInstruction').css('color','green');
$('.lblInstruction').css('font-size', 'small');
$('.lblInstruction').text("Please continue filling the address and bank details.").fadeOut(4000, "linear");
}
else
{
   $('.lblMessage').show(); 
$('#' + txtABNNumber).css('border','1px solid red');
$('.lblMessage').css('color','red');
$('.lblMessage').text("Please provide a valid ABN number").fadeOut(4000, "linear");
}
}
});
}
OUTPUT:

This approach has couple of benefits:

1. Data is light weight so quite fast processing.
2. Adds more usability to the form since validation is quick and done client side.
3. Straight forward access of JSON data in JQuery and cleaner JS code.

This is just an example but there can be various other ways in which JQuery can be leveraged in conjunction with Nintex Forms to make the forms more interactive, user friendly and flexible. Hope this helps.

Cheers
Happy coding!