Product Forums

I just wanted to gauge people’s opinions and experiences with the newer K2 Workflow Designer.We’ve had so many problems with K2 Studio workflows over the summer, including issues with what should be very basic functionality. For example, hyperlinks in an email body are no longer being accepted in some of our workflows, resulting in failed workflows with errors stating that there is no connection string for the destination user. Remove the hyperlinks from the email and the exact same steps work perfectly. The errors don’t even match the issue...When we raise tickets with K2, we’re told that development of K2 Studio workflows is no longer supported because it is considered legacy, and the recommendation is to move to the newer Workflow Designer.Fair enough — so I’ve been trying to migrate some of our existing workflows to the new designer.Unfortunately, the experience so far has been extremely poor.Window panes regularly freeze or become unresponsive. When editing an email body, if you e

Issue DescriptionWhen you use a workflow variable of type Date and Time, the converted workflow cannot be deployed. Saving fails with a Bad Request, without indicating the cause in the designer. This occurs whether or not a default value is set for the variable.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you use the NWSwitchAdapter Switch action and leave a branch empty, the branch converts without an outgoing line. At runtime, the workflow follows that branch and stops, preventing subsequent actions on that path from running.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you use the NWBuildStringAdapter Build String action, the composed text is converted as literal text. References such as {ItemProperty:Title} and {Common:CurrentDate} are not resolved, so the variable contains the reference text instead of the actual values.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you use the SPSetFieldWithKeyAdapter Set Field Value or SPUpdateItemWithKeyAdapter Update List Item action, the step converts without the list, method, or column bindings. The step completes successfully at runtime but writes nothing to the list, and references in the value are treated as literal text.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you use the NWSendMessageAdapter Send Notification action with a hyperlink in the message body, the link is carried across as raw markup and cannot be displayed by the designer's body editor, causing the message body to appear empty.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you use the NWSendMessageAdapter Send Notification action with the {Common:AllApproverComments} reference, it converts to an unmapped placeholder. K2 has no equivalent comments field, so the placeholder cannot be mapped or used.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you use the NWSendMessageAdapter Send Notification action with a person selected directly in the recipient field, the recipient is exported as a SharePoint claims login and passed as plain text. K2 cannot resolve the recipient, so the notification is not sent.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you use the WFIfElseAdapter Condition action to compare a SharePoint list column, the column reference is treated as literal text instead of the column value. The condition therefore does not match and always follows the negative branch.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you use the WFIfElseAdapter Condition action and leave one branch empty, the branch is converted without an outgoing line. At runtime, the workflow follows the empty branch and stops, preventing any subsequent actions on that path from running.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you run a workflow that sends emails, the workflow fails and an error occurs.Error Message:The following errors occurs:“Send email failed due to: Error during serialization or deserialization using the JSON JavaScriptSerializer. The length of the string exceeds the value set on the maxJsonLength property.”Thereafter,“"no connection string”ResolutionThe fix is available in:Nintex Automation K2 (5.8) Fix Pack 39. Nintex Automation K2 (5.9) Fix Pack 17. Nintex Automation K2 (5.9.1) Fix Pack 05.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you change the font family of a dropdown, the watermark font updates correctly, but its color changes to match the control instead of remaining grey.When you change the font family of a text box or other control, the watermark remains grey, but its font remains Open Sans instead of matching the selected font.When Use Legacy Theme is unchecked, the control and watermark fonts update correctly, but the watermark color changes instead of remaining grey.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17. Nintex Automation K2 (5.9.1) Fix Pack 05.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you migrate to SPFx, a workflow configured to start when a document is uploaded may start multiple instances for documents that were uploaded previously and already have a K2 workflow instance running. The workflow then stops starting new instances for newly uploaded documents.ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 17.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you host your K2 database on Azure SQL, you may experience high CPU usage on a SQL instance.ResolutionThe fix is available in:Nintex Automation K2 (5.8) Fix Pack 37. Nintex Automation K2 (5.9) Fix Pack 18. Nintex Automation K2 (5.9.1) Fix Pack 05.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Hi everyone,I’m currently developing a workflow in Nintex K2 and I need the workflow to retrieve data from a SharePoint Online list.I’m quite new to K2 and I’m not sure what the correct integration/setup process is between K2 and SharePoint.My requirement is basically:SharePoint Online List → K2 → SmartObject → K2 WorkflowI would like to use the SharePoint list data inside the workflow, for example to retrieve/list items and use the column values in the workflow.I have access to K2 Management, and I can see SharePoint-related Service Types such as SharePoint Site Collection and K2 for SharePoint, but I’m unsure which one should be used and how it should be configured.My main questions are:What is the recommended way to connect K2 to an existing SharePoint Online site/list? Do I need to create a Service Instance in K2 Management using the SharePoint site URL? Which SharePoint Service Type should be used? What authentication method should be configured for SharePoint Online? Does K2 for

In NWC I need to create an xtension using api v3.all the posts I’m seeing suggests that NWC can’t utilise v3 at the moment.is this the case or am I just configuring the xtension wrong?. I keep getting an error saying the specification is incorrect. cheers marc

I’m working on a flow to update a Nintex Table from a report retrieved from our ERP. Part of the flow requires that it compare a ticket number from each row of the report to what’s already in the table, so it will only add new rows.The approach I’m using is to use a Query a Table action to generate a collection of only the ticket numbers (i.e. theTableResult>Rows) then using a Check If Item Exists in Collection action from a ticket number in the report, to see whether a given ticket number is in the collection and hence in the table.The snag I’ve run into is that the Check action doesn’t seem to be correctly evaluating whether the supplied value is found in the collection. This is what the collection looks like in Log to Instance Details, along with the raw result of the Check action for ticket 71629 (supplied as a default text variable):Logging the First Row from that same table query appears to show the value correctly:In other words, it seems to work fine showing the info directl

I’m trying to generate a text variable with a custom date.I can’t use “Format date from String”: none of the built-in “Format” options match what I need.I’d prefer NOT to use a form (this will be a component workflow, invoked from an external app), so I’m not sure this documentation applies:  https://help.nintex.com/en-us/nwc/content/designer/Functions/formatDate.htmThis is EXACTLY what I’m looking for: yyMMddHHss:  I’m trying to use fn-FormatDate({Workflow:Current Date and Time},"yyMMddHHmm") in “Set Variable”.It’s printing out “fn-FormatDate(...)” instead of executing the inline function:Q: What am I missing??? BACKGROUND:What brought the question up is that I was trying to do several SMALL tasks that I THOUGHT were “trivially simple”: a) format a custom date string (this question), b) generate a random number, c) create a text file formatted with embedded newlines, d) etc. etc.I found this “workaround” for the custom date string:1. Call Format Date Time with one of the built-in form

Hello,Just have question about Nintex workflow “Assign Flexi Task” not sure if that was the expected behaviour. I have setup a workflow with “Assign Flexi Task” for some reason when I rejected the assign task it does not go to the next step where it send email. The Approve outcome works but not Reject.   

Issue DescriptionWhen you install a fix pack on a K2 5.9 environment with the Client Tools installed, navigating to any K2 site displays a "Configuration Error" screen.Error Message:The following error occurs:“Server Error om ‘/Management’ Application.”ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 16.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you migrate from Exchange Online EWS to Microsoft Graph for Send Mail workflow actions, the Send Mail action fails when the configured From address is a mailbox other than the default K2 service account mailbox.Error Message:The following error occurs in the HostServer log:“Code: ErrorItemNotFoundMessage: The specified object was not found in the store., The process failed to get the correct properties.”followed by:“ServerEvent: There is no connection string for the destination email address”ResolutionThe fix is available in:Nintex Automation K2 (5.9.1) Fix Pack 05. Nintex Automation K2 (5.9) Fix Pack 16. Nintex Automation K2 (5.8) Fix Pack 37.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the pa

Issue DescriptionWhen you use the PUT method to upload files to SharePoint Online, PDF files are uploaded and displayed correctly. However, other file types appear to be saved but are corrupted and cannot be viewed.When you change the method from PUT to POST, an error occurs.Error Message:The following error occurs:“404 {"error":{"code":"itemNotFound","message":"The resource could not be found."”ResolutionThe fix is available in:Nintex Automation K2 (5.9) Fix Pack 16. Nintex Automation K2 (5.9.1) Fix Pack 05.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

.

Issue DescriptionWhen you enter content that exceeds the available field length in Workflow Designer, a horizontal scroll bar is displayed at the bottom of the field. However, the scroll bar height and behavior is inconsistent between versions.ResolutionThe fix is available in:Nintex Automation K2 (5.9.1) Fix Pack 04. Nintex Automation K2 (5.9) Fix Pack 16.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you are creating or editing a workflow in the Designer, the Operator filter for SmarObjects under Functions is not visibleResolutionThe fix is available in:Nintex Automation K2 (5.8) Fix Pack 36. Nintex Automation K2 (5.9.1) Fix Pack 04.Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.