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

Getting Started

43 Posts authored by: fhunth Champion

Sometimes when you use an Action Set to execute and/or group some actions, it appears when part of the main flow.

 

 

 

It happens that when you have actions nested inside others, you'll have the possibility to mark them to run as the workflow owner only from the principal one.

 

Only actions at the root path of the workflow will have the Run as Workflow Owner option.  If you have an action in any branch, this option will not be available.

Last mission May Mission - Quick Top Tip!  has left tons of useful information.

I get this from Cassy Freeman and converted it on a fast reading help with samples for the parseLookup function.

 

 

 

 

 

 

 

 

Sometimes I needed to cancel all workflow on a specific list.
The following powershell script will help you to do this.


#Site URL
$web = Get-SPWeb "http://urlforsite.com";
$web.AllowUnsafeUpdates = $true;
#List Name
$list = $web.Lists["ListName"];
# Iterate through all Items in List and all Workflows on Items.        
foreach ($item in $list.Items)
{
foreach ($wf in $item.Workflows)
{
#Cancel Workflows       
[Microsoft.SharePoint.Workflow.SPWorkflowManager]::CancelWorkflow($wf);     
}
}
$web.Dispose();

Web Service Reference

The following section provides an overview, and describes the service operations and data types, of the Workflow web service included with Nintex Workflow 2013.

The Workflow web service provides administrative functionality for Nintex Workflow 2013. You can perform many of the functions normally managed for NintexWorkflow 2013 through SharePoint Central Administration and the Workflow designer, including:

  • Exporting, saving, and publishing workflows

  • Starting and terminating workflows

  • Scheduling workflows

  • Retrieving information about running workflow tasks

  • Processing and delegating task responses for workflow tasks, including Flexi task tasks.

  • Retrieving workflow history for workflows

Service endpoint

The following URL represents the service endpoint for the Workflow web service, where <site> represents the SharePoint site used to establish context for the service operations provided by the endpoint.

http://<site>/_vti_bin/NintexWorkflow/Workflow.asmx

The value specified for <site> is important, in that it both defines and limits the execution context of the service operations for the Workflow web service. For example, if you want to export a site workflow associated with the SharePoint site collection, you must specify the root URL of the site collection in <site>.

Invoking service operations

You can use any invocation method supported by Simple Object Access Protocol (SOAP) 1.2 to invoke the service operations provided by the Workflow web service. For example, you can generate a Windows Communication Foundation (WCF) client in Visual Studio, which in turn can be used to create a WCF client channel and communicate with the service operations provided by the Workflow web service, or you can add a service reference to the service endpoint for the Workflow web service in a Visual Studio project, which automatically generates a WCF client that you can use to access the Workflow web service.

A detailed discussion of SOAP invocation and WCF client implementation is beyond the scope of this document. However you can find a code sample and basic implementation of a WCF client that communicates with the Nintex Workflow endpoints, at Export and publish a workflow with the Nintex Workflow SOAP Web Service.

For more information about WCF client implementation in Visual Studio, see Windows Communication Foundation Services and WCF Data Services in Visual Studio, on Microsoft Developer Network.

Service operation examples

The examples provided for each service operation represent the SOAP envelope for each request and response, in its native XML structure, for the purposes of readability.

Service operations

AddLongTermDelegationRule

AddWorkflowSchedule

AddWorkflowScheduleOnListItem

CheckGlobalReuseStatus

CheckInForms

DelegateAllTasks

DelegateTask

DeleteLongTermDelegationRule

DeleteSnippet

DeleteWorkflow

ExportWorkflow

FixWorkflowsInSiteFromTemplate

GetFolders

GetItemsPendingMyApproval

GetListContentTypes

GetOutcomesForFlexiTask

GetRunningWorkflowTasks

GetRunningWorkflowTasksCollection

GetRunningWorkflowTasksForCurrentUser

GetRunningWorkflowTasksForCurrentUserForListItem

GetRunningWorkflowTasksForListItem

GetTaskDetailsUsingStub

GetTaskStubsForCurrentUser

GetWorkflowHistory

GetWorkflowHistoryForListItem

GetWorkflowXoml

HideTaskForApprover

HideWorkflow

ProcessFlexiTaskResponse

ProcessFlexiTaskResponse2

ProcessTaskResponse

ProcessTaskResponse2

ProcessTaskResponse3

ProcessTaskResponseUsingToken

PublishFromNWF

PublishFromNWFNoOverwrite

PublishFromNWFSkipValidation

PublishFromNWFSkipValidationNoOverwrite

PublishFromNWFXml

PublishFromNWFXmlNoOverwrite

PublishFromNWFXmlSkipValidation

PublishFromNWFXmlSkipValidationNoOverwrite

PublishWorkflow

QueryForMessages

RemoveWorkflowSchedule

RemoveWorkflowScheduleOnListItem

SaveFromNWF

SaveFromNWFNoOverwrite

SaveFromNWFXml

SaveFromNWFNoOverwrite

SaveSnippet

SaveTemplate

SaveTemplate2

SaveWorkflow

SnippetExists

StartSiteWorkflow

StartWorkflow

StartWorkflowOnListItem

TemplateExists

TerminateWorkflow

TerminateWorkflowByName

TerminateWorkflowByNameForListItem

WorkflowExists

WorkflowFormProductSelected

Data types

ContentType

Folder

ItemsPendingApproval

ProcessTaskResponseResult

WorkflowTaskDetail

 

If you are looking to disable the Nintex Mobile App option from the drop down as shown below, you can

 

 


example.jpg

    do the following:
    • Navigate to your SharePoint CA
    • Click on Nintex Forms Management
    • Select Manage Live Mobile Access
    • From this page disable "Disable Live Mobile Access" option
    • Press OK

    This will remove Nintex Mobile Apps option from the menu.

    This list is based on information published on http://help.nintex.com/en-US/nintex2016 

     

    External Data Column control

    The External Data Column control enables users to add data from external content types to standard SharePoint lists. Just like an external list, the external data column can display data from any configured external content type.

     

    Change Content Type control

    The Change Content Type control enables users to change the content type for a list item in a SharePoint list where there are multiple content types on that list. The control populates itself based on the context of the list. At runtime it relies on the form being run in edit full desktop mode and hence will not work when running in mobile mode.

     

    Web Request control

    Enterprise Edition for Nintex Forms 2016 is required for this feature.

    The Web Request control allows you to look up data using external web services. Use this control to populate form fields using data managed in business applications and cloud services. Call REST APIs by specifying the service URL, request method (GET or POST), and authentication type, or create SOAP envelopes using the POST method. 

    List Item control

    The List Item control can be used to display an item from a SharePoint list. 

     

    SQL Request control

    Enterprise Edition for Nintex Forms 2016 is required for this feature.

    The SQL Request control allows you to look up values from SQL databases. Use this control to populate drop-down lists and other display formats in your forms. Retrieve data from SQL databases by specifying server, database, authentication, stored procedure, and optionally stored procedure parameters for dynamic filtering. Using the values retrieved from the SQL database, the SQL Request control selects the value and display fields. The value field is stored in the specified column (see the control field “Value field”) while the display field is displayed on the form (see the control field “Display field”).

    Page Break Guide control

    Enterprise Edition for Nintex Forms 2016 is required for this feature.

    Supported for use in Desktop layouts only.

    The Page Break Guide control allows you to decide where a form will have page breaks when rendered using Print to PDF. Use this control to force a form to break at certain points when being printed.

    Managed Metadata control

    Managed Metadata is a hierarchical collection of managed terms that must be defined within SharePoint prior to use in Nintex Forms. For more information on managed metadata refer to http://technet.microsoft.com/en-us/library/ee424402.aspx.

    The Managed Metadata control retrieves these managed terms from your SharePoint environment. Once a data selection has been configured, users can select values from a list of set terms, allowing for more accurate selections.  

    Rich Text control

    Use Rich Text to display formatted text, pictures, hyperlinks and tables on a form. 

     

    Workflow Diagram control

    The Workflow Diagram control can be used to display a Nintex workflow on a form.

     

    Recurrence control

    The Recurrence control allows a user to make the calendar item a repeating event. A user can edit the reoccurrence pattern when filling in the form.

     

    Button control

    The Button control can be used to initiate an action, such as submitting a form or initiating a custom JavaScript.

     

    List View control

    The List View control can be used to display a SharePoint List and optionally specify the list view to display.

    fhunth

    Inline versus runtime functions

    Posted by fhunth Champion Nov 25, 2016

    Sometimes we remember about inline functions and runtime and use them on different parts of the design of our Nintex Forms, but we don't get the expected result by us, and sometimes it's simply because we haven't considered when they are executed.

     

    The difference is that Inline functions are run when the form is loaded., although the Runtime Functions will run while you have the form open, changing a control 's value, so filling a text field will cause the Runtime function to evaluate again.

     

    This is a simple reminder for me and you.

    Exporting all forms on the site

    This is an useful feature that sometimes saves your work.

    Currently on Nintex Forms for Office 365 has not the feature to browse your past version and you cannot rollback a change. That 's when this feature ( exporting all forms ) is useful because you can use it daily and have all version saved.

     

    You can export all forms on the site to a local .zip file. The file contains a separate .nfp file for each list that includes a form. Each .nfp file includes all configured device layouts for the form.

    Exporting all forms on the site is useful for backing up forms, copying forms from one server to another, and using forms in other SharePoint lists.

    To export all forms on the site

    Note: You must be a site owner to access this functionality.

    1. On the Site Contents page for your site, click the Nintex Forms for Office 365 app.
    2. On the upper right of the Nintex Forms for Office 365 page, click Nintex Forms Admin and then select Export All Forms on Site.
    3. Follow browser prompts to open or save the .zip file.

    Related information on Nintex Help

    Importing and exporting forms

     

    Just follow the next steps.

     

    • Open Nintex form
    • Select Code

     

    NWF$(".nCAF-library-ribbon").hide();

     

     

     

    Currently in Nintex Forms for Office 365 you cannot open old form versions as you can on the on-premise version.

    While we wait for this feature I want to share how me and my team work with forms while we are sharing it.

    We opened on the designer the same form with different users (User1 and User2) and made changes and then User1 published changes and then User2 published the other changes.

    Finally we saw that the last published form is the current version without the User1 's changes.

    Although we imagined that result, the Nintex designer does not show any message for the form opened at the same time or that another user made changes.

     

    With that said, we decided to implement a simple idea that is helping us without losing changes of another designer/developer/user on the form design.

     

    The simple idea is:

     

    - Add a label on the right upper corner of the form

    -When the form is opened by an user, we set the convention to edit that label and set it with something like this: "I am User1 and started editing the form at 3.00 PM, please donot make changes" and save the form.

     

    So if another user edits it , he/she will see that label, and will not save/publish the form.

    The "dateDiffDays" function will only return the difference between two dates as a positive integer. It is only designed to return the difference between two dates, not determine if one date falls before or after another.

     

    To have the date difference display in this way, you will need to use a combination of some calculated values and a Form variable. Essentially you need to compile a string, which simply adds the "-" symbol in front of any difference value when Date A is less than Date B.

     

    Try it doing the following:

     

    1 - Add two Date/Time controls to the Form, Date A and Date B

    2 - Add a calculated value control and set it to calculate the difference between the above: dateDiffDays(DateA,DateB) - Be sure to give this control a name so it can be referenced later, I simply called mine "Difference."

    3 - Add a second calculated value control and set it to the following formula: If(greaterThanOrEqual(DateB,DateA),' ','-') - This will generate a negative symbol when the second date is an earlier date to the first date. Name the control (I named mine "Tag")

    4 - Add a Form Variable, set it to type "String" set all recalculate options to "Yes" and then use the following formula: trim(Tag+Difference)

    5 - Add a third calculated value control and just set it to log the Form variable.

     

    When you preview the Form and enter some dates you should see the third calculated value control log what appears to be a negative number. Note you can hide the other calculated value controls so they aren't visible to the end user.

     

    It's important to note that the above will not actually log a negative integer, just give the appearance of one. So if an actual negative integer is needed the conversion would need to be done by a workflow when the user saves the list Item or submits the task (depending on the type of Form.)

     

    With some work you may also find you can do this conversion entirely within a variable, however I believe using the calculated value controls is probably a better option as it gives you an opportunity to have a look each step in the process should anything go wrong.

     

    Hopefully that's helpful.

    Workflow Designer

    Print

     

    Zoom to view

     

    Reporting and Management

    User-based workflow tracking

     

    Summary statistics, reports, and charts

     

    Individual workflow history & verbose logging

     

    Log in the history list

     

    User access control

     

    Workflow change approval

     

    Logic and Flow

    Action set

     

    Filter, switch action

     

    User interaction

    Delegate workflow task

     

    Approval, review, and multi-outcome tasks

     

    Email based natural language approval

     

    String operations

     

    Site, Libraries and Lists

    Create/delete sites and site collections

     

    Check In/Check Out/Cancel Check Out on items

     

    Create list

     

    Set approval status

     

    Customization & Re-Use

    Content Types, User defined actions

     

    Custom context data

     

    Export to Visual Studio

     

     

    This list is an extract from http://www.nintex.com/workflow-platform/technical-specs-workflow

    Home » Nintex » New Task list for Nintex Workflow tasks

    New Task list for Nintex Workflow tasks

    Some Nintex workflow actions create tasks on the SharePoint site, for example both the Assign Flexi task and Request Approval actions create tasks. These tasks are by default created on the sites ‘Workflow Tasks’ list. If you would like all the tasks for a specific workflow to have it’s own tasks list, you can setup the Nintex Workflow to create it’s own Task list.

    Even Lazy Approval Flexi Tasks still create actual tasks on the site, the task list can be a great resource to review active tasks (i.e. tasks that have not been completed) or to review who approved which task and when.

    1. Open the existing workflow, click on the Workflow Settings option.
    Workflow-New-Task-List-15-1
    2. Scroll down to the Task list section, select Create new… from the dropdown. Enter a name for the new task list for this workflows tasks.
    Workflow-New-Task-List-15-2
    3. Save the workflow settings, publish the workflow.

    Many users use the Lazy Approval Settings when they are designing a workflow.

    Many of us don't know that when a user that receives an email that can be answered by replying it, and this user has set as Out of office, a loop of infinite emails begins.

     

    To solve this issue is simple. Just go to Sharepoint Central Administration, navigate to the Nintex Workflow Management / Lazy Approval Settings and add a phrase to ignore. Ignore the phrase "Out of office"

     

    Filter Blog

    By date: By tag: