Stefanie Sloper
My feedback
-
18 votes2 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
Stefanie Sloper supported this idea ·
-
16 votes
Stefanie Sloper supported this idea ·
-
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.
Stefanie Sloper supported this idea ·
-
1 vote
Stefanie Sloper shared 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
LisaStefanie Sloper supported this idea ·
-
60 votes
Thanks for your suggestion Joseph. Can you expand more on what your requirements are?
Thanks,
EuanAn error occurred while saving the comment Stefanie Sloper supported this idea ·
-
78 votes3 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
Stefanie Sloper supported this idea ·
-
30 votes
Stefanie Sloper supported this idea ·
-
3 votes
Stefanie Sloper supported this idea ·
-
768 votesOpen for voting · 49 comments · 3 - Nintex Workflow for Office 365 » Runtime · Flag idea as inappropriate… · Admin →
Stefanie Sloper supported this idea ·
-
12 votes
An error occurred while saving the comment Stefanie Sloper commented
We also need to use caps in task outcomes. it seems like more effort to have changed these to lower case, is there a reason behind this?
Stefanie Sloper supported this idea ·
-
27 votes
Stefanie Sloper shared this idea ·
-
15 votes
Stefanie Sloper shared this idea ·
-
296 votes
Thanks for your suggestion.
I will update this idea if there are any updates to share.
Cheers,
EuanAn error occurred while saving the comment Stefanie Sloper commented
Please add support to conditionally require an attachment.
Stefanie Sloper supported this idea ·
-
199 votes22 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
Thanks for your feedback. We announced our intended support for APIS in 365 at WPC. Please see the dedicated API forum on UserVoice for further info
Stefanie Sloper supported this idea ·
-
33 votes
With the release of Task ID in the task actions, the best approach here is to query the task IDs for the comments and other details and write them to an audit list. That way you can control the retention period in accordance with your retention policies.
This can either be done within each workflow that creates tasks, or if a blanket approach is adequate a site workflow that runs to a schedule, using the scheduled start capability.
Stefanie Sloper supported this idea ·
Just had to implement a nasty polling loop to workaround this. Please add :-)