Tom Castiglia
My feedback
-
674 votes47 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
Lisa -
14 votes2 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
-
106 votes2 comments · 2 - Nintex Forms for SharePoint » Form controls · Flag idea as inappropriate… · Admin →
We want to add more controls to the repeating section and this is something we are working on with Universal Forms.
In the future we should be able to support most controls in the repeating section.
I will update this feature when I can confirm this will be available in Universal Forms.
Cheers,
Euan -
331 votes
-
359 votes
-
6 votes
-
698 votesOpen for voting · 50 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment An error occurred while saving the comment I have numerous customers with this requirement and I've seen quite a few posts on the Nintex Community site requesting this feature as well.
-
2 votes
-
253 votes
I am pleased to announce this capability has rolled out this week as a Component Workflow. Learn more at https://www.nintex.com/blog/whats-new-component-workflows/
An error occurred while saving the comment Likewise, we have a client asking for this feature. They have 25 content types published to 400 site collections via Content Type hub.
-
469 votesOpen for voting · 14 comments · 3 - Nintex Workflow for Office 365 » Runtime · Flag idea as inappropriate… · Admin →
-
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.
An error occurred while saving the comment This really needs to be escalated!. As noted below, when using the Request Data action, the Task ID is populated right away. But for To-Do Task, FlexiTask, Request Review & Request Approval - the Task ID is not populated until the task is complete. This is a pretty fundamental workflow requirement. There is a workaround using workflow.asmx for list workflows (via GetRunningWorkflowTasksForListItem), but this wouldn't work in a site workflow.
-
255 votes23 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
Please have a look at the condition builder just released as part of conditional start. Is this the kind of condition builder that you need in “wait for field change in current item” ?
An error occurred while saving the comment Also Contains, Not Equal, Begins with, Ends With
I'm so glad to see this feature moving closer to reality. This will open up a whole new set of powerful use cases for Nintex.