Archive: Nintex for Office 365 Knowledge Articles

IssueWhen clicking a submit button that has a redirect URL configured, the following error may occur: Server Error in '/' Application. ________________________________ Runtime Error Description: An exception occurred while processing your request. Additionally, another exception occurred while executing the custom error page for the first exception. The request has been terminated.  ResolutionVerify the button configuration for 'redirect URL' value is in plain text and does not have a hyperlink URL. For example:Valid value: https://site_url/siteAInvalid value : https://site_url/siteA 

IssueList lookup() runtime function does not return any results on Nintex Mobile form. ResolutionThis is expected behavior.The List Lookup control is compatible with Nintex Mobile but the Lookup() runtime function is not compatible. 

IssueWhen receiving task email reminders that contains variables in the body of the email, the HTML code <href=> is displayed between the variables. ResolutionDelete, and then recreate the action in the workflow. Additional InformationThis issue occurs when content is copied and pasted from existing actions. 

IssueUsing Start A Task Process action with Nintex Workflow for Office 365, any users who is not assigned the Task is able to action the task if they have the required permission.  ResolutionThis is expected behavior for this action in Nintex Workflow for Office 365.  A SharePoint Designer with the same task action you will experience the same behavior as Nintex Workflow uses the same Workflow Manager engine as SharePoint. 

ISSUEWhen working with Nintex for Office 365, Nintex keeps creating new Nintex Task Outcomes content types with random numbers after the name.ERROR CODERESOLUTIONThe creation of additional task content types is expected behavior in Nintex for Office 365.ADDITIONAL INFORMATIONEach time that a new 'Custom Outcome' is applied to either a Start A Task Process or Assign A Task action, Nintex will create a new 'Nintex Task Outcome' content type with a GUID appended to the end, so that it can maintain the new 'Custom Outcome' associated with the workflow. For example: Nintex Task Outcomes 0e08932e-a343-4753-925f-220ed22be6cbRELATED LINKS

IssueWhen using a Send an Email action in a workflow created in Nintex Workflow for Office 365, 1.0.4.0, and changing the formatting of any “inserted reference” item, it will create many empty SPAN tags in the HTML. Resolution  Additional InformationThis is a known issue that is currently under investigation. 

IssueOnce a modified item form has been submitted, a child workflow starts before a parent workflow begins and displays the following message: A workflow is currently running. Please wait for it to complete. ResolutionManually terminate the running workflow instance and re-run the workflow.  

IssueWhen clicking on a task link from a mobile device the task may open up in a browser depending on associations on the device.If the task opens in a browser a SharePoint task form will be presented in either View or Edit mode regardless if a Nintex Responsive form has been added to the task or the appropriate layout has been added to a Nintex classic Form.  ResolutionThe SharePoint Task form showing is not a bug but a limitation. Additional InformationA workaround for this issue is to insert a custom link in the email notification.Click "Link" from the Insert tab ribbon and add a custom link as per the example below.fn-Replace("{Common:ApprovalUrl}", "Lists/Workflow%20Tasks", "_layouts/15/NintexForms/Mobile")&List=<TaskListId>Note: Change Workflow%20Tasks to your Task Name and <TaskListId> to your task list id GUID.The idea for this approach is to use Approval Url which is similar to <SiteURL>/Lists/Work

IssueWhen using "Office 365 upload file" action and the file name contains a special character such as {} ~, the following error may occur: Some parameters failed the validation check. - [InputDestinationFileName] : The file name is invalid. ResolutionThis issue has been fixed on the latest version of Nintex Workflow for Office 365.  

IssueWhen configuring the Document Generation action, the configuration indicates the document quota has been exceeded, even when no documents have been created. ResolutionContact Sales@Nintex.com. Have Sales verify that the 'Nintex for Office 365' asset and 'Nintex Document Generation' asset are active. If both assets are active, confirm that both assets are on the same contract. Even if both assets are created and live, if they're on separate Salesforce contracts, Document Generation for Office 365 will not work.   Additional InformationThis is caused by a mismatch in the licensing with the associated customer account.Looking at the JSON call that is made when the action configuration loads, you will see the following inside of developer tools: {"Total":0,"Used":0,"IsTrial":false,"SubscriptionStartDate":"0001-01-01T00:00:00","SubscriptionEndDate":"0001-01-01T00:00:00","OverUsage":0,"QuotaOverageAllowance":0,"ErrorType":400,"IsSuccess":false,"ErrorPayload":null,"Info":null,"Subscripti

IssueWhen running a workflow that includes a Send an Email action, the workflow will complete successfully, however emails are sent intermittently. ResolutionOpen a support ticket with Microsoft SharePoint support with the Workflow Instance ID of one affected workflow, along with the Start Time and Last Run Time from the Workflow Status page of the instance.  Additional InformationSharePoint Online handles the mail flow for internal emails, as such Nintex does not have any control of email delivery while workflows use the internal mail system of Office 365. 

When a task assignee attempts to respond to a task using LazyApproval, the response is not accepted.ConditionsCustom HTML is applied to Initial Task Notification in 'Assign a Task' HTML includes a <Title> element LazyApproval is enabled Additional InformationThis behavior is caused by the email client through which the response was sent. For example, Outlook in Office 365 ignores the <title> tag, however, the Outlook Desktop Application will include the <title> tag in your response, forcing LazyApproval to process and reject the contents of <title> as a response.  

Issue When creating a Excel Spreadsheet, using a Create List Item action, the Excel spreadsheet does not open, and shows the error:"We are sorry, we could not open your workbook. It's possibly corrupt or using a file format that is not supported."  ResolutionThis is an underlying issue with the Sharepoint platform and also occurs with a Sharepoint Designer Workflow action: "Create List Item"As an alternative, use the O365 action “Office 365 Upload File" 

IssueNintex Workflows will run even when all Start Options are disabled. ResolutionWorkflows require at least one Start Option selected when being published.  Leave "Start manually" set to active and navigate to List Settings > Workflow Settings > Remove, Block, or Restore a Workflow, find the workflow you want to not run, and make sure the No New Instances radio button is selected for that workflow. Additional InformationThe workflow will not run the first time it is published when nothing is selected, however if a start option was selected on a previous published instance, turning off the start options will not prevent it from running. SharePoint Designer workflows cannot even be published without a start option. 

ISSUEWhen creating a save button in a task form, the button cannot be used without one of the task outcomes being selected.ERROR CODERESOLUTIONThis is expected behavior. As a workaround, try the following:Create an additional outcome (Incomplete or In Progress etc). Set the new outcome as the default value for the outcome control Create a hide / disable rule on the 'Save & Submit' button for when the outcome is equal to the value created earlier. For example: taskoutcome=="Incomplete" This would allow the save button to be used, but would prevent anyone from submitting the form until the outcome field has been set to one of the expected out of the box fieldsADDITIONAL INFORMATIONRELATED LINKSHow to ignore Decision validation when save button clicked in Flexi Task Nintex Form

IssueWhen using Send Email action, emails are not being delivered. ResolutionCheck the Clutter/Junk mailbox and mark the email as 'Not as Spam' Additional InformationIt would also be a good idea to add the following emails to the address book:no-reply@sharepointonline.comnoreply@workflownotification.com 

IssueWhen using the Assign a Task action, the workflow automatically suspends if a external email address is used. ResolutionThis is by design. Email recipients are restricted to those with email accounts in the Office 365 Tenancy. For more information, see Office 365 Assign a task action. 

ISSUEWhen browsing to Nintex Forms using Safari on Mac, the following prompt appears:Please enable cookies for your browser to use the FormERROR CODE‘Please enable cookies for your browser to use the Form’RESOLUTIONNavigate to Safari > Preferences. Click Privacy. Select "Allow from websites I visit" or "Always allow".ADDITIONAL INFORMATIONForms is using cookies for user authentication, this is part of the product and cannot be changed. The reason Safari (default behaviour on OS X and iOS) behaves differently than Chrome is because Safari defaulted to not accept all cookies, while Chrome does. As such this would be considered expected behavior. RELATED LINKSSafari 8 (Yosemite): Manage cookies and website data

ISSUEWhen creating a new workflow in Nintex Workflow for Office 365, a "For development use only" message appears in the background.ERROR CODERESOLUTIONThis is by design. Workflows will be marked as 'For development use only' until the workflow has been assigned to production on publishing. For more information, see How to Designate a Production or Development Workflow in O365.ADDITIONAL INFORMATIONRELATED LINKS

IssueCannot see the Nintex Workflow or Nintex Forms for Office 365 app within Site Contents even after adding the app to the tenant from the SharePoint Online store. ResolutionOpen Office 365 Admin panel Open SharePoint Online Administration Open the Apps menu Open Mange Licenses Select the drop-down arrow next to the Nintex Workflow for Office 365 or Nintex Forms for Office 365 section, and select Manage License Select the ACTIONS control drop down and select Recover License Select Continue and then Return to Site 

IssueWhen uploading a document to a document library in SharePoint Online that has a Nintex Form published, Internet Explorer presents a window that states "This content cannot be displayed in a frame". Resolution In Internet Explorer, please navigate to Settings (Cog in top right) > Internet Options > Security > Trusted Sites > Sites and add the following sites:*.office.com*.microsoftonline.comYou may need to close and reopen Internet Explorer for this to take affect. Error Code"This content cannot be displayed in a frame" Additional InformationThis appears to only occur when there is a SharePoint Column that is 'Required'. 

IssueAfter configuring the Send Email action, when selecting save the action errors with:Oops! Something went wrong. Email - dispose : TypeError: Object expected Error CodeOops! Something went wrong. Email - dispose : TypeError: Object expected ResolutionUse a browser other than Edge for workflow design, as it is not supported by Nintex for Office 365.  Related LinksNintex Workflow Supported Browsers 

IssueWhen tying to publish a workflow within Office 365, the designer presents the following error after selecting Publish:Error publishing workflow. System.Net.WebExeption: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. Error CodeError publishing workflow. System.Net.WebException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult) --- End of inner exception stack trace - ResolutionOption 1:If the site was recently migrated, please remigrate the site and that should resolve the issue.Option 2:If the site was not recently migrated, please contact M

ISSUEWhen a workflow contains an action(s) that utilize Connection Manager, the following error may occur: The username format is invalid.ERROR CODERESOLUTIONConfigure the Username field, in the Connection, with an email address instead of a display name. ADDITIONAL INFORMATIONRELATED LINKSHelp file - configure a connection manager

IssueNintex Workflow for Office 365 is does not load and shows a spinning circle.Furthermore from the Browser Developer Tools (F12)> Network tab, the following error may appear:Field type [field name] is not installed properly. Go to the list settings page to delete this field ResolutionVerify if the "Field type" mentioned on the error message exists and delete it as per error message advised. Contact Microsoft Support for guidance if you are unable to find or for any further details regarding the mentioned "Field type". Additional InformationThe field type mentioned does not belong to Nintex, therefore contacting Microsoft Support is recommended.