philipplucas
My feedback
-
8 votes
Thanks for your suggestion.
I will update this idea if there are any updates to share.
Cheers,
Euanphilipplucas supported this idea ·
An error occurred while saving the comment -
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
philipplucas supported this idea ·
-
16 votes
philipplucas supported this idea ·
-
125 votes8 comments · 4 - Nintex Forms for Office 365 » Form Filling Experience · Flag idea as inappropriate… · Admin →
Thanks for your suggestion. I will update the ticket if we have anything to share on this idea.
Cheers,
Euanphilipplucas supported this idea ·
-
768 votesOpen for voting · 49 comments · 3 - Nintex Workflow for Office 365 » Runtime · Flag idea as inappropriate… · Admin →
philipplucas supported this idea ·
-
18 votes
philipplucas shared this idea ·
-
1 vote1 comment · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment philipplucas commented
If you configure your text variable to appear on the start form you will be able to decide if it is multiline or not. Maybe this helps.
-
76 votes
An error occurred while saving the comment philipplucas commented
This is very important! At the moment I can almost never see how the lookup (for example when assigning a task) was actually configured. If I want to be sure it's correct I have to reconfigure it. This is not acceptable for productive work.
philipplucas supported this idea ·
-
54 votesOpen for voting · 1 comment · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
philipplucas supported this idea ·
-
21 votes
An error occurred while saving the comment philipplucas commented
We have a big project at the moment, having the exact same issue for our staging environments. This means that at the moment we need to repair workflows for many hours/days after migrating them from dev to test to prod.
Very annoying and a big time eater. Thus, the workflows aren't really portable at all.
philipplucas supported this idea ·
-
57 votes
philipplucas supported this idea ·
-
137 votes
philipplucas supported this idea ·
-
201 votes
Hi all,
We do not have any immediate plans to support this feature but will update this ticket if our position changes.
Cheers,
Euanphilipplucas supported this idea ·
-
14 votes
philipplucas supported this idea ·
-
27 votesOpen for voting · 1 comment · 1 - Nintex Workflow for SharePoint · Flag idea as inappropriate… · Admin →
philipplucas 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.
An error occurred while saving the comment philipplucas commented
How about writing the previous value in the database on item update to make it available afterwards. This will not be necessary if versioning is enabled on the list/library as one should be able to receive the previous value from a previous version. Additionally this could be an optional setting so safe some DB space if not required.
philipplucas supported this idea ·
-
674 votes48 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
Hey all,
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
Thanks
Lisaphilipplucas supported this idea ·
-
14 votes
philipplucas supported this idea ·
-
89 votes1 comment · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
philipplucas supported this idea ·
-
92 votes3 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
philipplucas supported this idea ·
I wonder how this feature is still missing. This would be a huge enhancement!