Apologies in the delay in responding to you, and thanks again for submitting your requests!
This scenario makes sense – I’ll add this into our backlog for review and prioritisation. I will endeavour to keep this ticket updated with any progress.
KateArne shared this idea ·
314 votes18 comments · 2 - Nintex Forms for SharePoint » Form Filling Experience · Flag idea as inappropriate… · Admin →
This feature has been included into Universal Forms for SharePoint and Office 365.
Once we have shipped Universal Forms for SharePoint, I will update this feature.
145 votes14 comments · 2 - Nintex Forms for SharePoint » Form controls · Flag idea as inappropriate… · Admin →
Thanks for your suggestion Vadim. As we are currently building Universal Forms for Office 365, SharePoint and Nintex Workflow Cloud, we are considering how we move forward with Live Forms with all the Nintex Infrastructure.
We currently support Google reCaptcha in Nintex Forms for Nintex Workflow Cloud which may suit your needs as the platform supports anonymous forms and pushing data to different systems.
158 votes3 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
8 votesOpen for voting · 3 comments · 5 - Nintex Workflow Cloud » Runtime · Flag idea as inappropriate… · Admin →
Without going into the technical detail; the previous value made available in conditional start is actually the current value just before any updates are made to the item. When the item is updated, we lose the ability to get the value prior to the update.
To restate the workaround as indicated in the idea; create an additional column in the list or library and update this with the current value of the column of interest. Then when the actual column is updated, the previous value is still available in the additional column. Of course one need not make this additional column visible in the view or Form so the users are not confused.
698 votesOpen for voting · 50 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
333 votes22 comments · 1 - Nintex Workflow for SharePoint » Documentation · Flag idea as inappropriate… · Admin →Jon Hardy responded
We are currently at the early stages of evaluating the whole topic of workflow documentation.
476 votes21 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →Jon Hardy responded
The task ID is populated once the task is completed. Before this the task list items can be locked by the task engine for processing and a workflow accessing this task may fail. There has been therefore a strong reservation form our Engineering group to implement this capability even if technically feasible.If one wishes to delegate the task then the delegation should be used.
Should you have other use cases for accessing the task list before the task is completed then please let us know what they are. There may be an alternative way of meeting this need that will not introduce the possibility of workflow failure.
674 votes48 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
There looks to be 2 requests here
- Update Inline function to allow calculate date difference, factoring in only business days / hours
- Update Calculate date action to factor in only business days / hours
Can you please share which of the two you require and your use cases