Itebe
My feedback
-
5 votes0 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
-
235 votes12 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
-
410 votes
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.
-
68 votes6 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment -
Support lists with versioning turned on and where "Append Changes to Existing Text" is set to "Yes."
373 votes46 comments · 4 - Nintex Forms for Office 365 » Form Filling Experience · Flag idea as inappropriate… · Admin →Hi all,
There is no movement on this feature at this time. If the status changes, I will update this ticket.
Cheers,
Euan -
37 votes2 comments · 2 - Nintex Forms for SharePoint » Form controls · Flag idea as inappropriate… · Admin →
Thanks for your suggestion.
I will update this idea if there are any updates to share.
Cheers,
Euan -
34 votes4 comments · 2 - Nintex Forms for SharePoint » Form controls · Flag idea as inappropriate… · Admin →
Thanks for your suggestion.
I will update this idea if there are any updates to share.
Cheers,
Euan -
302 votes
Hi all,
With the development of Universal Forms, we are looking at how the current form modes are supported in the existing product.
At this time we are still planning to continue using functions to detect form modes. This is so we are able to support migrations but also give a lot of flexibility in the rules engine.
We do not plan to bring different layouts to Universal Forms at this time. As we are introducing multipage to Universal Forms, we do need to figure out how a multipage form will be printed and is under consideration.
I will update this feature when we release an Advance Preview of Universal Forms if our position changes based on feedback.
Cheers,
Euan
This is a basic one. I'm crashing a lot of workflows trying to add custom values to a flexi-task. Why is not possible to set all metadata values from the Nintex Workflow Action?