Skip navigation
All Places > Getting Started > Blog > Authors pandeyk

Getting Started

8 Posts authored by: pandeyk

We have two option to schedule workflows depending on the type of workflow that you need to schedule here i am going to explain you how to Schedule Site Workflow on SharePoint / Nintex 2010

 

  1. Click on Site
    Action  menu
  2. Click on Nintex
    Workflow 2010

Untitled.png

3) Click on Schedule site workflows option

Untitled.png

Now WorkflowSchedules.aspx page will appear 

Click on Add Schedule

Untitled.png

After clicking button you will get create a new workflow schedule for a site workflow window

 

Untitled.png

  • Select the workflow
  • Select a workflow for this schedule
  • Put Start time
  • Schedule End
  • Click on save

Untitled.png

Finally your workflow has scheduled and it’s appeared in schedule section like above image view .

 

Thanks

Kamal

Nintex Runtime error handling

Posted by pandeyk Feb 27, 2015

Nintex do have custom actions  available to handle the runtime error in workflows actions and its often choose which one to use based on whether or not they have error handling, It looks  like 32 of the actions have error handling with around 90 not having error handling .

 

We can also write appropriate  custom error message for most of the available actions in the workflows and it  could be anything based on actions

  1. e.g 

 

  • Server is busy or not responding due to network issue
  • Unauthorized users  credential. 
  • Runtime execution error date not responding

 

Importantly Nintex does not have error handling capability available its limitation of Nintex workflow product.  But I would suggest you use “system defined error and action name “

 

Action

Error details

Copy to file
  share  action

  • File cannot be
      copy because copy action not configured to missing variable name
  • Network name
      cannot be found." OR "Failed to copy item to a file share 

Users name and
  UAD action error

  • Multiple
      connections to a server or shared resource by the same user using more than
      one user name, are not allowed
  • Current credential
      being used by another resource

Convert a
  Document 

  • Error converting
      document. Conversion jobs did not complete. 1 jobs failed. 0 jobs
      cancelled"
  • Document
       conversion action not configured
  • Variable value
      null or missing

Inline Function
  error

  • Error retrieving
      context data. Error executing inline function.
  • Check that the
      correct arguments have been passed to the function”

 

database
  connection

  • System.Transactions.TransactionException:
      The operation is not valid for the state of the transaction
  • Network does not
      response connection error

 

We are expecting Nintex  product team will  come up with details perty soon for delivering such a great product and we are hoping Nintex will resolve  all bugs and limitations. and improve improved vesrion soon.

------------------------------------Check and  Increase Throttle Size -------------------------------------------------------------------------

PS C:\> stsadm -o getproperty -pn workflow-eventdelivery-throttle

<Property Exist="Yes" Value="15" />PS C:\>


PS C:\> stsadm -o setproperty -pn workflow-eventdelivery-throttle -pv "25"

Operation completed successfully.

 

------------------------------ Check and Increase Batch Size---------------------------------------------------------------------------

PS C:\>
PS C:\> stsadm -o getproperty -pn workitem-eventdelivery-batchsize

<Property Exist="Yes" Value="100" />PS C:\>


PS C:\> stsadm -o setproperty -pn workitem-eventdelivery-batchsize -pv "125"

Operation completed successfully.

 

PS C:\>
PS C:\> stsadm -o getproperty -pn workflow-eventdelivery-timeout

<Property Exist="Yes" Value="5" />PS C:\>


PS C:\> stsadm -o setproperty -pn workflow-eventdelivery-timeout -pv "10"

Operation completed successfully.

 

- ------------------------------------------Time Out----------------------------------------------------------------------

PS C:\> stsadm -o getproperty -pn job-workflow -url https:// Weburl

 

PS C:\> stsadm -o setproperty -pn job-workflow -pv "Every 10 minutes between 0 and 30" -url https://webapp/

 

PS C:\> stsadm -o setproperty -pn job-workflow -pv "Every 10 minutes between 0 and 30"

 

Operation completed successfully.

 

--------------------Workflow Timer Interval ------------------------------------------------------------------------------------------------------------------------

PS C:\> stsadm -o setproperty -pn job-workflow -pv "Every 10 minutes between 0 and 30" -url webapp/

 

PS C:\> stsadm -o setproperty -pn job-workflow -pv "Every 10 minutes between 0 and 30" -url https:// webapp:port

 

 

Hopefully is will resolve Nintex Workflow actions that may be affected

  • Flexi-task
  • State machine
  • Task Reminder
  • Set a variable

 

Good luck and Enjoye ...

 

  1. Open you newly created category.aspx page
  2. Open the two problematic webpart's property panel
  3. Change the view :
    1. for the proposed discussion webpart, set it to "Proposed discussion"
    2. for the other one, set it to "subject"
  4. From now, once you validate your page, you will have everything almost working, the only left problem is that you don't see the discussions according to the category of the page. let's continue.
  5. Open two instances of Sharepoint Designer 2013. One on the source site, and one on the target site. On both open category.aspx page
  6. On the target page, in all the xsltlistviewwebpart's parameterbinding, there is binding missing, you have to add it! 
  7. Almost at the end of page of your source page, locate the {CategoryID}, you will have to place it exactly at the same place on your target page.
  8. Save it.
  9. Test it & pray

Hey guys hiding the ribbon with Nintex Forms 2013  is easy  is simple and sweet.

 

  • Open Nintex form
  • Select Code

 

NWF$("#s4-ribbonrow").hide();

 

Enjoy !!!

A common scenario with workflow is that a task needs to be sent to somebody.. But how do you go about choosing who that somebody is, if they can change depending on the data being submitted? In reality you can store that information in the workflow, but this leaves you with the issue of having to edit and republish the workflow every time one of the approvers changes.

The best way to complete this function is to use a second list with your approver’s data and filter information coupled with the “Query List” action in Nintex Workflow. Now this isn’t the only thing you can use this method for. Below I’ll go through just a couple of examples and if you have any other ideas or things that’s you do let us all know in the comments J

Lookup Manager of Department.

Using the out of the box “Manager” function may not work especially if the initiator is 2 or 3 levels down, but requires the head of the department to sign off. For this, we can use the list to Store the department name with the manager for that depart. The workflow can simply query either AD or the user profile to assess what department the initiator is in to retrieve the right manager for the approval.

So above is the list of managers that we have to choose from, and their corresponding department.

Now you wouldn’t have both “Query LDAP” and “Query user Profile” you can pick either one. It could also be a case where you could use the “Execute SQL” or “Call Web service” action to retrieve the Department information from Human Resources system. Regardless of what method you use to get the initiators department, store this information to a variable. In this example I have stored it to ‘varDepartmentFromProfile‘. I have also created a second variable ‘varDepartmentFromMasterList‘.

Using the ‘Query List’ action, we can now go about getting the info.. First select the Master List (In this case it is called Department Managers), then expand the Filters and adjust the filters. To retrieve the appropriate manager, first select the column we want to filter on in the Master List (Department). Then use the operator ‘is equal to’ against the department value we pulled from LDAP/Profile/ External system etc.

At the bottom of the ‘Query List’ action select the Manager Field from the Master List as the information that we want and store this to the second variable we created ‘varDepartmentFromMasterList

Now that this is done, use the ‘varDepartmentFromMasterList‘ variable in the ‘Assignees’ field in whichever task action you are going to use.

Get Approval Manger based on Department and approval Limits

Expanding slightly on the above, add a third column to the Master List and call it ‘Approval Limit’

Now in the list you are running the workflow on, may have a total amount.. This could possibly be a requisition request, purchase order, Travel Approval form.. If I had entered into the list, let’s say a travel request for $6456.00 and I’m in the Marketing team. The Query list action will retrieve the user account ‘NW13-User04′. I can now go ahead and assign the task to that user as they have the appropriate approval limits to review my request J

 

Ok so you see where I’m going with this.. What other examples have you got? Let me know in the comments and I’ll attempt to build them out J

Nintex Workflow 2010 SDK

Posted by pandeyk Feb 21, 2015

The location has recently changed and can be found here: link to SDK. With that, you'll be able to build custom actions, inline functions, build SP deployments to publish workflows and custom actions.

To complete the upgrade from the previous version of Nintex, ensure that you still have a valid license; otherwise this upgrade will not be possible.

 

Navigate to “Add/Remove Programs” on the server hosting Nintex Workflow 2010 and remove it.

 

(This will not affect the programs functionality in SharePoint 2010)

 

Do not retract the solutions from the Solutions Management, as this will disrupt users that are currently using the product.

Once this has been done, run the new installation “setup.msi” for Nintex. When it prompts to add the solutions, select “Yes”. This will attempt to automatically upgrade the WSP’s that are currently installed on your solution.

 

Once the installation has been completed, it will show the solutions page, with the status of “Deploying (timestamp of when this was initialized)”

 

This is where I ran into an issue, although everything in the supplied upgrade document stated that this will show up as deployed after a while, it was not the case.

 

After about 25minutes, the 2 solution files were still showing as deploying, with the same timestamp as when the software installation finish. I cancelled both “deployments”, both these files now showed as deployed, but with no Last Operation Time in either.

 

How to fix this?

 

Reset IIS, Start -> Run -> iisreset

 

This will release any threads that are holding onto the WSP files.

 

Make sure that the SharePoint 2010 Administration service is running, Start -> Run -> services.msc

 

You will now need to manually upgrade the solutions files.

 

Start the SharePoint 2010 Management Shell as an Administrator.

Update-SPSolution –Identity nintexworkflow2010.wsp –LiteralPath “nintexworkflow2010.wsp” –GacDeployment 
Update-SPSolution –Identity nintexworkflow2010enterprisefeatures.wsp 
–LiteralPath “nintexworkflow2010enterprisefeatures.wsp” –GacDeployment

This will deploy your solutions correctly and add the needed DLL’s to the Global Assembly Cache.

 

 

You can also try below steps:

 

  1. Install the Nintex using Nintex setup
  2. Retract the deploy WSP
  3. Now use PowerShell scripts for installation of WSP
  4. Enable-SPFeature -Identity "NintexWorkflowAdmin" -Url "weburl"
  5. Install-SPSolution –Identity nintexworkflow2010.wsp –WebApplication "Weburl" -GACDeployment
  6. Repeat same steps for all web application you can also
    enable the features using Nintex admin section

Filter Blog

By date: By tag: