Archive: Nintex for Office 365 Knowledge Articles

QuestionIs there a way to enable verbose logging for a workflow in the Office 365 version? AnswerVerbose logging is only available on On-Prem. For Office365 the logs are all based online by either Microsoft or Nintex. It is not possible to share the logs as they contain logs for all O365 users. To check the log for a specific issue, a case will need to be opened with Nintex Support, ensuring that the URL of the Workflow Status page, for the affected workflow is provided.  

QuestionIs it possible to customise the error message related to the KB article: Error "Item does not exist. It may have been deleted by another user." When Accessing Task Form AnswerNo, It is not possible to customise this error message.   Additional InformationThe error message is generated by the SharePoint Online engine and Nintex does not have any control to override the error message. 

QuestionWhy do some items that are created or modified a Nintex Workflow for Office 365, shown as the "SharePoint App" account instead of the workflow initiator.  AnswerThe action is used to create or update the list item is under an 'Action Set' with elevated permissions. All the workflow actions under 'Action Set' with elevated permissions will be run under the SharePoint App account. Related LinksHelp file: Action Set 

QuestionWhen using the People Picker control in Nintex Forms for Office 365, the People Picker may display users that are no longer within the company.  AnswerEnsure that these user accounts have been removed from the Admin Centers > SharePoint > User Profiles > Manage User Profiles. 

QuestionWhy the schedule workflows in Nintex Workflow for Office 365 does not change automatically? AnswerNintex Scheduling Service converts all date/time values into UTC absolute time. This means that the schedule will not automatically adjust for Daylight Savings. The Workflow will always run based on the UTC value.  Related LinksScheduling Worklfow In The Cloud https://community.nintex.com/blogs/NintexProductBlog/2017/12/19/scheduling-workflows-in-the-cloud-nwc-office365 

QuestionHow long does it take for Nintex workflow deletion to be reflected in the Subscription overview page (SOP)? AnswerWays of deleting Nintex workflows in SharePoint onlineThrough the Nintex Gallery view (recommended) By deleting the associated list (List workflow) By deleting the Site or Site Collection that the workflow is on.Which workflows affect the Subscription overview page (SOP)?Nintex workflows and not SharePoint online workflows i.e. workflows created with SPD and not Nintex and Nintex workflows that are not limited action workflows.When does the SOP reflect the deleting of a workflow?Note: if a workflow is not a Nintex workflow or it is a limited action Nintex workflow then this will not affect the Nintex SOP at all. These workflows, when published, are not counted as subscription workflows and therefore do not contribute to the workflow counts on the SOP.The following table summarises the timing: Method of deletion When reflected on the SOP Using the Nintex gallery

QuestionWhere can a Trial of Nintex Workflow App for Office 365 be installed? AnswerThe Nintex Workflow App will need to be stored within the SharePoint tenant of Office 365.There is no other test or pre-production environement outside of your tenancy. 

QuestionIs it possible to update Nintex O365 App using PowerShell script? AnswerDue to Microsoft limitation this is not possible, since store apps have licensing implications, so they cannot be just installed using a PowerShell script. Additional InformationFurthermore more this questions can be read in the following Microsoft blog. 

QuestionWhen trying to import on-prem forms (XML) into Forms for O365, the following error will appear:'Please select a Nintex Forms export file to import' AnswerYou cannot import an on-prem Form XML file into Forms for O365. The release notes page for Nintex Forms O365 has been recently updated to address this matter. 10th March 2016Changed the Form file type from XML to NFPExporting from the designer is now an NFP packageExport all forms will now include NFP filesXML files exported from Nintex Forms for Office 365 are still supported in import. Exported forms from Nintex Forms for SharePoint are not supported. 

QuestionHow can you capture the Lazy Approval token in the subject line as a variable? AnswerCurrently it is not possible to capture the Lazy Approval token. 

QuestionCan you add buttons to a form for a mobile device? AnswerIt is not possible to add a button to a form for a mobile device. 

QuestionWhat is the process of notifying the customer of an expiring O365 license?AnswerAs a subscription expiry approaches, a number of communications, prompts, and warnings are displayed as outlined below:60 days prior to your subscription expiryThe primary contact is notified that the subscription is due to expire in 60 days.30 days to your subscription expiryAll registered contacts are notified that the subscription is due to expire in 30 days.Nintex Workflow for Office 365: Visual prompts are added to the Nintex Workflow designer. Workflow history records are added stating that the subscription is due to expire. Nintex continues to notify all registered contacts of the upcoming expiry at regular intervals over the 30 day period.At subscription expiry:Once a subscription has expired, you will no longer be able to save or publish workflows through the Nintex Workflow designer or forms through the Nintex Forms designer. Any existing workflows that are published will enter a suspended

QuestionDoes Nintex support Commvault for migration and backup processes?  AnswerThe Commvault site mentions that alerts and workflows are not supported. If you want to backup or migration, Nintex partner with ShareGate, AvePoint and Metalogix. Back Up Documents for the SharePoint Server Agent 

QuestionWhere can I find then Nintex Subscription Overview within the Office 365 tenant? AnswerThe Nintex Subscription Overview can be found through the following steps:From a sites where Nintex for Office 365 is installed access Site Contents Open one of the Nintex Apps From the ribbon Select Information > Subscription Overview  

QuestionIs there any effect in workflow functionality when the assignee to use setting is modified from Production to Development and vice versa? AnswerThe workflows will continue to function as expected, without any issues.  Related LinksHow to Designate a Production or Development Workflow in O365Assignee Use for Workflow 

QuestionIs it possible to connect to a list on O365 with List Lookup on a form in On-Prem? and vice versa AnswerIt is not possible to connect to a list from a different platform using List Lookup on a Nintex Form 

QuestionIs there a method to allow side-load of these apps directly into the tenant, or should we temporarily enable access to the SharePoint Store, install the adds-ins and then disable access (assuming that the apps do not require ongoing access to the store). AnswerThere is no option available to install Nintex app without access to Microsoft App store 

QuestionIs there a limit on the number of items that can be submitted using a Nintex Form on O365. AnswerNo.  Once Nintex Forms has been purchased/subscribed to there are no limits on the number of form submissions. 

QuestionDoes the "Office 365 user access management" action work with external accounts? AnswerThe "Office 365 user access management" action does not work with external accounts. Additional InformationWithin the Office 365 Admin Portal, you can view Users and see their Status.  Statuses reflect the license a user account has (e.g. Office 365 Enterprise, Dynamics 365, Unlicensed, etc.) or if they're a Guest.  Any account that has the status of Guest cannot be affected by the "Office 365 user access management" action and will result in a "User Not Found" error. 

QuestionWhat will happen if an account password used in a Shared Connection Manager expires? AnswerThe Shared Connection Manager has to be re-configured to use the new password otherwise the workflow will be suspended with an error indicating an invalid password.  As the alternative is to use a service account credential that has no expiration password policy to configure the Shared Connection Manager. 

QuestionAre there any issues on Nintex Office 365 services? AnswerYou can check the status of Nintex Office 365 apps via Nintex Services Related Linkshttps://community.nintex.com/docs/DOC-1356 

QuestionWhen using Nintex Workflow for Office 365 "Create List Item" action and the workflow is configured to start on a conditioned (Conditional Start Workflow), the created item will have the "Created By" item property as SharePoint App instead of the workflow initiator.  AnswerThis is currently a platform limitation based on how the "Conditional Start Workflows" are configured to start and run. The "Conditional Start Workflow" will have SharePoint App as the workflow initiator.  Related LinksConditional Start in Nintex for Office 365. 

QuestionCan we configure the From Email Address which is used when sending emails from Nintex Workflow for Office 365? AnswerThe From email address is set by default by Nintex and cannot be customize.  Related LinksUser Voice : From Field in Send an Email 

QuestionCan a form that was originally designed with the 'Classic' forms designer be converted to a new 'Responsive' Nintex Form? AnswerCurrently there is no way to directly convert an existing 'Classic' form to a Responsive form. If you would like to move between the design styles you can do so through the following: Open the current form design.  Select 'Delete Form' from the designer ribbon (we recommend exporting the form design for backup purposes unless you wish to revert back in the future). Re-open the Nintex Forms app from the list ribbon and you will be prompted to select your new design style.  

QuestionWhat happens to running workflow instances when a new design of the workflow is published within the designer? AnswerWhen a workflow instance has been started and committed to the database, any changes that are made to the workflow design will not be reflected until a new workflow instance is started. Any running instances will run as the workflow was configured when that instance was started.