With the new announcement of the Azure App Service (especially the API Apps and Logic Apps), it would be great if there was a way to integrate Nintex Workflow with the azure app service:

• API Apps - With API apps being promoted as a way to reuse functionality across different applications it would be good if there was a way for Nintex Workflow to use API apps from the marketplace as well as API apps built by the organisation. Given that API apps use swagger, it would make the configuration experience similar to that provided via other Nintex Workflow Actions.
• Logic Apps - although the platform is a little similar to Nintex Workflow in that it is a drag and drop designer, it is a tool that is quite useful for integration scenarios. It would be awesome if there was a way for eithter Nintex to be able to trigger the initiation of a logic app or for the logic app to be able to trigger a workflow e.g. via REST. (Although there is currently a connector available for SharePoint on premise, it is still somewhat limited especially at the triggering scenario).

Some of the list contains more than 5000 items and cause the list view have issue to display items, error message in the list show: This view cannot be displayed because it exceeds the list view threshold (5000 items) enforced by the administrator.

Wish to have the action that are able to archive any list without the fields configuration like create list item. And it would be good that the action is able to save the current list as template and create on behalf with the name that user specific in action.
Because I would like archive every column with every column's data.

Archive reason is because the data is required for future reference.

Hi Michael,
I just spoke to the person who reported the Nintex problem. He said that the string function worked after adding the {TextStart} and (TextEnd} around the value, but string functions should work on their own and should not require extra tags for them to work. Having to remember this every time is not practical. You may wish to pass this on to Nintex developers for consideration.

Regards
Mustansir Ferozpurwala
JP2030 JSO Software Engineer
Lockheed Martin Australia
M 0402 300 211
mustansir.ferozpurwala@lmal.com.au
Contractor to Defence

From: Nintex Support [mailto:support@nintex.com]
Sent: Thursday, 12 March 2015 2:36 PM
To: JP2030 Software
Subject: RE: Nintex issue [ ref:00D90q6Cb.50090jNzxn:ref ]

Hi Mustansir,

Thank you for your email, you need to add {TextStart} and (TextEnd} around the value you are trying to evaluate. Please see Function behavior in our help files.

http://nintexdownload.com/helpfiles/nw2013/NintexWorkflow2013UserManual.html

Kind regards,

Michael Floyd | Nintex Workflow for Everyone® | Service Engineer I | support@nintex.com

It would be nice, if all the Task will have the same Features.

• In Flexi Tasks I'm not allowed to hide the item properties ont the Task site.
• In Flexi Task I miss to ask for data like in Request Data. It would be great to be able to choose a Flexi Task, ask for an Input and choose the outcomes.

• There is although no Action ID in Flexi Task that can be stored and used with other Actions.

• In Request Data there I miss the "Edit Settings for" in Notification and in Required Notification.

• It would be although great to have the "Edit Settings for" in Reminders.

Then we miss the Responsible and Deputy handling.
We often make Tasks for a responsible. The Reminder is send to responsible and deputy. But the deputy is not allowed to Close the Task.
It would be great to have two Assign Fields. One for the responsible and one for the deputy.
Then the deputy will only answer the Task when he knows the responsible is not available the next time (Holiday).

Remove the workflow action "Start a Workflow" of the current workflow.

We had a user create a workflow "Workflow A" and the first step in the workflow was "start Workflow A". There needs to be a filter/configuration that prevents this as an option because became an endless recursive workflow instance. We removed the workflow, deleted the workflow, delete the item and then the list and this workflow still kept going. We then stopped the timer job and restarted IIS and this was still occurring. The ultimate fix was lock access to the site collection containing the item that the workflow was ran on.

To prevent this from becoming an issue for us or anyone else in the future a mechanism that would remove current workflow as an option would save much head headache. Yes, they could still create this same logic with 2 workflows, but the likelihood is far less.