Vikrant Behal
My feedback
-
3 votes0 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
Vikrant Behal shared this idea ·
-
3 votes
Vikrant Behal supported this idea ·
An error occurred while saving the comment -
22 votes1 comment · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
Vikrant Behal shared this idea ·
-
20 votes
Vikrant Behal shared this idea ·
-
3 votes0 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
Vikrant Behal shared this idea ·
-
12 votes1 comment · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
Vikrant Behal supported this idea ·
Vikrant Behal shared this idea ·
-
21 votes0 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
Vikrant Behal shared this idea ·
-
16 votes0 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
Vikrant Behal shared this idea ·
-
35 votes0 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
Vikrant Behal shared this idea ·
-
6 votes
Thanks for your suggestion.
I will update the ticket if we have anything to share on this idea.
Cheers,
EuanVikrant Behal shared this idea ·
-
75 votes5 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Vikrant Behal commented
It'll be great if Nintex can enable it for Web Request as well.
Vikrant Behal supported this idea ·
-
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.
Vikrant Behal supported this idea ·
-
99 votes
Vikrant Behal supported this idea ·
-
55 votes1 comment · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
Vikrant Behal supported this idea ·
-
468 votes
Reinstating this request as it is clear that delegation is required and not escalation.
An error occurred while saving the comment Vikrant Behal commented
Hi Jon - This has been open for 9+ months. Does Nintex has plans to develop it?
Vikrant Behal supported this idea ·
-
768 votesOpen for voting · 49 comments · 3 - Nintex Workflow for Office 365 » Runtime · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Vikrant Behal commented
This is great feature and Nintex should enable it for Office 365 as well.
Vikrant Behal supported this idea ·
-
67 votes1 comment · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
Vikrant Behal shared this idea ·
-
76 votes
An error occurred while saving the comment Vikrant Behal commented
It's a surprise that developers can't check the already configured settings.
Vikrant Behal supported this idea ·
-
89 votes
Hi Sridhar,
Can you share some examples of how you are using constants in your workflows?
Ta, Rick
Vikrant Behal supported this idea ·
-
87 votes
Hi Sridhar,
The issue we currently have is the workflow engine does not send us any kind of event to indicate that the component workflow (or any workflow) has suspended meaning we can’t send any notification back to the parent workflow. We are currently talking with Microsoft to see if they can provide us the info we need, will update you once we know more..
Cheers, Rick
An error occurred while saving the comment Vikrant Behal commented
This is much needed feature.
Vikrant Behal supported this idea ·
While Component workflows are available for re-usability but that doesn't serve the use-case of associating workflows with specific content-type.
It'll be great if Nintex can enable content-type level forms and workflows on Nintex Online platform.