please bring the new Actionable items feature to sharepoint on Prem

https://community.nintex.com/view-blog-post.jspa?blogPost=2485&utm_source=Connect&utm_medium=social-post&utm_campaign=Sep2017-ActionableMsgs&mktosrc=Social_media

Currently there is not audit logs for track workflow changes. It would be helpful to have a functionality that would allow Administrators to monitor activities in SharePoint, Nintex Forms and Nintex Workflows. Essentially something like the Audit logs for SharePoint.

Please provide a feature to track all administrator changes like create, update, delete and publish Nintex forms and workflow.

We have C-level employees approving workflows via LazyApproval. Unfortunately this has a negative context and we are getting pushback by our workflow implementers to see if we can adjust this label.

I see that the emails can be modified, but we are still seeing remnants of that verbage in our approval history.

Is there a way I can modify this? Thank you.

Currently the store data action only allows one value to be stored. If want to store multiple values to later retrieve need to use the action multiple times. Can Store data action be updated to allow multiple values?

With the recently release Nintex Forms enterprise feature to print to PDF, it would be great to access this functionality via a Nintex Workflow.
As an example a Nintex Workflow could take a Nintex Form and generate a PDF file to be created in a library.

Today, the docusign actions allow one user to sign a document. It doesn't allow 2 users to sign the same document (using the same enveloppeID)

HR Example : a new contract is first sent to the new employee for signing and the same contract is sent to the manager for signing. Today the only way of doing it is to send the document twice in tow different envelope.

we leave a few scenario behind

As start workflow option to start a workflow you can set the "value differs from the old value" option. Nintex Workflow obviously has access to this information. Within the workflow you can not load the previous value into a variable or something else. That would be nice.

Actually you have to use multiple hidden fields storing the previous value to use in for workflow porposes.

Currently available in a Request Approval action but not in a Flexi Task.

A request I receive frequently is the ability to restart a workflow from it's point of failure instead of from the beginning. It would include the ability to restart from the last successful action.

A Workflow Action to easily select the columns to export to CSV (attach to an email notification for example) including data in Repeating Sections.

Currently I can do this manually, but very cumbersome and time consuming.

Hi there

For a long time XML was the de facto standard input notation for web service calls but there have clearly been changes to, and developments in, the available notations.

It would be really good to see some of these new input methods being supported in the web service actions in the workflow product such as JSON.

Thanks 

Nintex workflows for O365 does not have error handling feature for many actions. The typical behavior at SP2013 is that user can choose to handle errors for certain actions. In office 365, Nintex provide a flag for subset of actions. This flag determines weather action succeeded or not.

Such actions are:
1. Web Request
2. Query XML
3. Update XML
4. Create item in another site
5. Delete multiple items
6. Update multiple items

Nintex Workflow works well with Lync 2013 however it would be great to see the product to work with Skype for Business 2015.

Some of the expected features would be to see:
- Instant message notification
- Functional Lazy Approval

To have a Pause action that executes based on the action configuration rather than relies on the SharePoint Timer Service (at least 5 minutes)

It would be a good idea if it would be possible to import the holidays (Easter, Christmas and so on) from a file (iCal or something) for each year.

Christmas is at the same date every year but Easter and some other Holidays are flexible. So you have to add the flexible Holidays manually which is not fun.

Would be great to check the design of a workflow if it meets best practices such as if it is too large (and should be broken into smaller workflows) or the actions used are appropriate, such as using Commit Pending Changes instead of pause.