Solution showcase: Learn how to use Nintex CE Platform
This section contains archived Nintex for Office 365 Knowledge Articles.
Recently active
TopicYou may experience current workflows are being suspended and no longer running to completion. This is due to numerous deleted association workflows that are ahead of the new running instance. InstructionsThis is a known issue with 2 possibility of the root cause:1. There are other workflow on the list (if any) to make sure that all the workflow has a Start Option from Workflow Setting (at lease one of the option checked). If all the workflows has the start option, then it related with Microsoft issue that lead us to possibility no 2. 2. Most likely the issue down to a problem with the workflow publishing location associated to the specific site library. Workflow definitions are normally stored in a hidden folder called "wfsvc". This issue creates another folder called "wfsvc1" and puts the workflow there - Microsoft should be able to move the workflows from the wfsvc1 hidden folder to the wfscv hidden folder then remove the wfsvs1 folder. In some cases republishing the workflow m
Topic When using the Exchange Online Create Calendar Item action, the item is not being created at the desired time on the calendar. The default value is Coordinated Universal Time (UTC). Instructions Open the configuration for the Exchange Online Create Calendar Item actionLocate the 'Time zone' settingSelect the desired time zone from the dropdown menu. Related Links https://help.nintex.com/en-US/office365/Designer/Actions/ExchangeOnlineCreateCalendarItem.htm
TopicConfiguring a control on a Nintex Responsive form as Appearance > Visible > "No" puts a "Hidden" message across the control in the Nintex Forms designer and causes the control to not populate it's default value or calculated data. InstructionsThe correct way to achieve the functionality of hiding a control that dynamically populates is to either use a hide rule on the control. Additional InformationThis functionality secures the metadata in the control from being changed in any way.Due to this functionality if you try to hide a control that populates dynamically like a Calculated value control or a single line of text control with a reference the data will not calculate.
TopicHow to do Task Delegation in the Nintex Workflow for Office 365? InstructionsUse the Task Escalation as the way to configure Task Delegation in the Nintex Workflow for Office 365. The functionality is available in the Assign a Task action and the Start a Task Process action, under section "Escalate or auto-complete" Related LinksHow to configure Escalate and auto-complete options on Office 365Task Escalation comes to Office 365Task Delegation Workaround in Nintex Workflow for Office 365 VideoTask Delegation Workaround in Nintex Workflow for Office 365 Archived blog.
QUESTIONWhat are the minimum permissions for Nintex Workflow and Nintex Forms for Office 365?ANSWERTo install Nintex Workflow for Office 365, the user account will need to have at least Site Collection Administrator permissions. To open the Nintex Workflow designer for Office 365, the user account will need to have at least:Full Control permissions for the list; Read permissions for the site; Read permissions for the site collection.To publish an Office 365 Nintex Workflow, the user account will need to have at least:Full Control permissions for the list; Design permissions for the site.To run an Office 365 Nintex Workflow, the user account will need to have at least:Contribute permissions for the list; Contribute permissions for the site. To install Nintex Forms for Office 365, the user account will need to have the following permissions:Site Collection Administrator.To open the Nintex Forms designer for Office 365, the user account will need to have the following permissions:Full Co
TopicWhen using the "Query List" action in Nintex Workflow for Office 365, with a Filter that is equal to a variable that has an empty string. The query will return 0 results even though there are some item(s) with an empty string value on one of the columns. InstructionsDesign the workflow as below:Use the "Conditional branch" action to check whether a variable is empty or not. If the variable is empty then use "Query List" with Filter = Is Null. If the variable is not empty then use "Query List" with Filter = "Variable".
TOPICHow to use utilize Nintex Forms for Office 365 and Nintex Mobile to add signatures to a form.INSTRUCTIONSFor using the Nintex Mobile App for capturing a signature, see Sign Your Name Across My Heart For extending the ability to sign forms from Nintex Mobile to the Nintex Forms for Office 365 App, See Extending Nintex Mobile Signature control to desktop/browserADDITIONAL INFORMATIONRELATED LINKS
TOPICHow to Get Actionable Messages to work.INSTRUCTIONSPrerequisiteThe recipient of the task must be an Office 365 customer with permissions for the SharePoint online site. Additionally, they must use one of the following supported versions of Microsoft Outlook: Outlook Web Access Outlook for 2016: Version 17.10 (Build 8201.1000) or higher If the Office 365 customer opens the email in a program that is not a supported version of Microsoft Outlook, they will receive a standard LazyApproval email and not an Actionable Message. Actionable Message configurationActionable Messages can be included in task emails sent by the actions Assign a task and Start a task process (LazyApproval must be enabled).Example configuration: Actionable MessagesIn this walkthrough, you’ll include an Actionable Message with the message body of your task emails. From the workflow designer, open the workflow you want. Drag and drop the Assign a task action to a drop zone in the design canvas. Double-click
Topic Creating connections in Office 365 for use in Nintex Workflows Instructions Shared Connection:Open the Nintex Workflow for Office 365 app Navigate to Site Contents > Nintex Workflow for Office 365 or directly from a your list by clicking the Nintex Workflow button in the ribbon. Select 'Connections' Click 'Create New Shared Connection' The drop-down menu will present many options for connection types. Reference the 'Connection types and Connector actions' section of Connections to identify which connection type is needed. Personal Connection:In the Nintex Workflow Designer, open the configuration for an action that utilizes a connection. In the ‘Connection’ drop-down menu, select ‘+ Create New Personal Connection’ Note: The instructions for both connection types are the same from this point forward. Enter the Connection Name and Tenant URL. Click ‘Connect’ Enter the credentials that the connection will use. The permissions requirements for each connection type are specified
QuestionMicrosoft is retiring Azure AD Graph on the 30th of June 2022, how will this affect Nintex Workflow. AnswerNintex Workflow uses the newer Microsoft Graph API so it is not affected by this retirement. Additional InformationThis also applies to Nintex Forms. Related Linkshttps://azure.microsoft.com/en-us/updates/update-your-apps-to-use-microsoft-graph-before-30-june-2022/
IssueThe following error message may occur when trying to save or publish Nintex for Office 365 workflows.‘Error Publishing workflow. The SharePoint admin has disabled the creation of new workflows. Existing workflows will continue to run.’ This error is caused by the tenant administrator when deactivating their SharePoint 2013 workflows on the tenant. This can be achieved via two ways: Classic SharePoint Admin center > Settings and checking ‘Block SharePoint 2013 workflows’ Through the SharePoint Online Management Shell executing the command:Set-SPOTenant -StopNew2013Workflows $TRUE Error Code ResolutionConfirm with the tenant administrator which method was used to block SharePoint 2013 Workflows and revert the change.For the Classic Admin Centre – Uncheck the Block SharePoint 2013 Workflows check boxFor the SPOTenant object – using the SharePoint Online Management Shell, execute the following command: Set-SPOTenant -StopNew2013Workflows $FALSE Additional InformationAt the time of
TopicInsert Image in Email Body for "Send An Email" action in Nintex Workflow for Office 365. Additional InformationTo be able to use an image in the email body for both Internal and External email services, the image has to be publicly accessible that does not require any credentials. An image stored under SharePoint Online tenancy or other media that required credentials to access cannot be used and it will only send either a blank email body or a symbol X as a replacement of the image that cannot be found. As a workaround, use the functionality of the email service "External email and attachments" and attach the image to the email rather than add the image in the email body. Related LinksHelp file : Send an Email
IssueAfter updating an Apple device to IOS 15, Nintex App Studio apps may stop loading.ResolutionRe-build the app in Nintex App Studio and download to the device again.Additional InformationNintex App Studio only started supporting IOS 15 as of the 1st of October 2021 so apps built prior to this date are not compatible.
TopicDoes Nintex support Multi-Geo in Office 365? Additional InformationWe DO support Nintex Workflow and Forms for Office 365 to be installed for the first time on a brand new Multi-Geo site collection. We DO NOT support Nintex Workflow and Forms for Office 365 where it has been installed or configured on existing site collections prior to migrating to a new Geo via Microsoft Multi-Geo PowerShell commands. Why don’t Nintex support the migration of site collections to new geo? There is an acknowledged defect within the Microsoft Multi-Geo migration process that causes an internal reference that the Nintex app and other provider-hosted SharePoint apps do not function correctly after migration.At the time of writing this, Microsoft has elected not to fix this defect due to COVID-related priorities and advise customers wishing to migrate in this manner to raise a DCR via their MS account manager.Nintex will continue to work with Microsoft to advocate for a change in this position. What c
TopicWhen a SharePoint choice column is updated to add or remove choices a published New Responsive Form with an existing choice control connected to the column does not update.InformationThis is expected behavior.The connected choice control is only updated in the form when the form is published. This is to ensure that the entries in the choice control are valid. If a choice is removed for instance it could make a rule invalid and therefore cause errors with the form.If a choice column is updated in SharePoint the New Responsive for has to be published again so it is updated.
QUESTIONWhat is the list of IP addresses that should be whitelisted for Nintex online services to work?ANSWERThere is no fixed list of IP addresses, Nintex online services are hosted on Microsoft Azure Cloud platform. For the list of IP ranges, see the Microsoft article Microsoft Azure Datacenter IP Ranges.ADDITIONAL INFORMATIONRELATED LINKS
ISSUEWhen using the “Wait for Event in List Item” action within a Site Workflow, if the item is updated with the Updated Item action the "Wait for Event" action never progresses. ERROR CODERESOLUTIONUse the Office 365 Update Items action instead of the out of the box Update Item action.ADDITIONAL INFORMATIONThe Update Item action does not trigger the item updated event receiver, which prevents events such as workflows starting on item update or the "Wait for Event" action from triggering. RELATED LINKS
TopicOpen Nintex Workflow for Office 365 Designer. Create a workflow variable. Drag and drop Task action. Open Nintex Task Form for Office 365 Designer and choose New Responsive Form. Utilize the Workflow variable by inserting the value from the Workflow Variable section. Additional InformationWorkflow variables are available to be inserted under the Formula section, however, if the workflow variable name as a space it will not works. Therefore as a best practice and to make sure it will always work, we recommend inserting the workflow variable from the Workflow variables section. Related Links
TopicConfiguring the Nintex List Forms Online Web Part on Office 365 InstructionsPublish a Nintex Form on a list (Classic or 'Old' Responsive Forms only). Navigate to your SharePoint site page and select 'Edit'. Insert > Web Part > Apps > Nintex List Forms Online. Click Add. Click drop-down arrow on web part > Edit Web Part. Configure the 'ListForms Settings' section. Click Apply. Save, Check In, and Publish your site page. Additional Information The Nintex List Forms Online Web Part is not currently compatible with New Responsive Forms. Some fields are marked with (*) suggesting that they are required, however, this is not always the case. For example, a 'New' form should not require an 'Item ID'. This is demonstrated in the examples below. Examples New Form Mode Display Form Mode
ISSUEThe userProfileLookup runtime function for Nintex Forms for Office 365 does not return any valueERROR CODERESOLUTIONSOLUTION 1:The User Profile Service may be using a different property name from the user property name being queried. Check the User Profile Service user property name by navigating to the SharePoint Admin center within Office 365 and click on User Profiles from the left menu, then click on Manage User Properties. Edit the property name and you will see under property settings a "Name" and "Display Name" field, make sure to use the "Name" field when performing the query. To get the "Name" of a user for example, use the syntax as shown below. userProfileLookup(Current User,"PreferredName") The below syntax will not return any result. userProfileLookup(Current User,"Name") SOLUTION 2:If the Current User is hard-coded with a value, make sure it has double quotes.For example:userProfileLookup("support@nintex.com","PreferredName") SOLUTION 3:Make sure that there is no oth
IssueWhen using Send an Email action with External email service and having a total size attachment of more than 20 MB, the workflow terminated with the following error: System.Activities.Statements.WorkflowTerminatedException: Total size of all attachments (x MB) exceeds the allowable limit of 20 MB.Error Code ResolutionReduce the total size of attachments up to 20MB. Additional InformationSend an Email (External service) with attachments has a limit for the total size of all attachments up to 20 MB. Related Links
QUESTIONWhat is the maximum size file to attach to the List item for Nintex Form for Office 365?ANSWERFor Classic and Responsive Form:Files attached to list items can be up to 250 MB in size. For New Responsive Form:The maximum size to allow adding to the form using Upload File control is 25MB per file and up to 10 items (250MB in total). ADDITIONAL INFORMATIONThe Nintex Form Office 365 file size attachment limit is following the SharePoint Online limitation. This size refers to this article SharePoint Online Limits.RELATED LINKShttps://help.nintex.com/en-US/Office365/Designer/FormControls/FileUpload.htmhttps://help.nintex.com/en-US/Office365/Forms/ResponsiveClassicForms/FormControls/ListAttachmentControl.htm
IssueEmails are not received from an Assign a Task or Start a task process action. ResolutionCheck if the 'Description' field in the Assign a Task configuration is using a variable. If so, confirm what the variable is populating; if the content in the variable exceeds the maximum length of the Description field, task notifications will not send. Related LinksAssign a Task Start a Task Process
IssueWhen publishing a Nintex workflow in O365 the following error appears " Error publishing workflow. NW-1007" ResolutionMake sure the conditional start conditions are valid.Make sure when comparing columns that they are of the same data type. for example, comparing a Single Lines of Text column to a choice column will cause this error. Error CodeError publishing workflow. NW-1007
TOPICHow to choose if a workflow will be published as a Production or Development workflow in Nintex Workflow for Office 365.INSTRUCTIONSSelect the publish icon from the ribbon of the Workflow designer. A dialog box appears with all the publishing options. Scroll down to the "Assigned use" section and select the radio button for either Production or Development.Additional Information1. By Default Nintex Workflows are published as Development workflows.2. When purchasing a subscription for Nintex Workflows for O365 the subscription will contain a number of allowed Production workflows and a number of allowed development workflows.3. The concept of product and development workflows differ for Nintex for O365 compared to Nintex on-premise Installations. For on-premise there is usually a Production and a Development environment. In O365 there is just one tenant and both production and development workflows co-exist.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.