543 votesOpen for voting · 34 comments · 3 - Nintex Workflow for Office 365 » Runtime · Flag idea as inappropriate… · Admin →
@ Andrea P , please see the earlier note on the platform limitations. We are looking at how we may meet the needs for debugging and workflow status visibility given these platform constraints. This is not to stimulate the uptake of Hawkeye, if you have an enterprise subscription license then you are entitled to Hawkeye anyway.
22 votes4 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
@the immediately previous comment (anonymous). A designer can create a connection (unless your administrator has disabled this option) by creating the connection from within the action in the designer. Note this connection will be a personal connection i.e. can only be used by the creator and will have tenant wide scope (i.e. can be used anywhere that the designer has SPO provileges to do so). Please refer to the help file for types of connections.
Can you share some examples of how you are using constants in your workflows?
The set workflow status allows custom status to be shown that is relevant to your workflow logic. It can also be populated with some standard status values as described in help. Reproduced here for convenience. This does not allow you to capture suspends or terminated status though. Please see and vote on suggestion "Workflow Errors". Thanks.
"You can specify a custom value, such as "Workflow Started," or a standard workflow status value from SharePoint, such as "Completed." For example, you might add two instances of this action to a workflow: one at the beginning, with the status value "Workflow Started," and another at the end, with the status value "Completed." For the list of standard workflow status values from SharePoint, see Workflow status values."
316 votesOpen for voting · 8 comments · 3 - Nintex Workflow for Office 365 » Runtime · Flag idea as inappropriate… · Admin →
This is on the road map. Please keep voting as input into the prioritisation process for development. Thank you.
66 votesOpen for voting · 4 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
In 365 we have allowed Actions sets with elevated privileges to be nested in paralle actions and other Action sets. In this respect Nintex for Office 365 is enhanced in comparison with on-premises.
While you wish to add the link to your Forms, this suggestion is probably better placed in the Nintex Workflow for Office 365 forum. Delegation would be workflow functionality.
126 votesOpen for voting · 8 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
Hi Scott and Cory,
I believe your use case is already supported by the Flexi-task action.
Select "All must agree on a specific outcome" under the "Behaviours" section in the configuratio.
Specify "approive", for example, as the response that all must agree to.
Then should the first or subsequent person not agree, the task will complete at that time without waiting for any other respondents. You do not need the task iDs (which can be saved if you select a variable to store them in under "Store task IDs in" in the configuration).
I believe this request should actually read "Populate task id as soon as the task is created" which is then the same reqiuirement as the idea of that description and we should merge these two.
1 vote0 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
Double left click in the Action box to open the action configuration window.
Unfortunately (or fortunately from a security perspective) the requirement to activate the elevated priviledges feature is inherant in the SP online App model architecture. This is required once per site (the Store app model) runs within a site scope.
Because of the fundamental platform differences it is not possible to have a totally seemless migration between Nintex on-premises and Nintex for office 365. There will always be a degree of manual reconfiguration involved.
You are correct, inline functions are not supported in 365 currently as yet, please add your votes to this suggestion as we actively evaluate the development programme with this uservocie input.
This is not normal behaviour. The start settings have been working as designed without issue, please contact Nintex support and raise a support case. Hopefully we can identify the issue quickly and get your start options working as you require.
446 votes33 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
We’ve just released the ability to capture comments from via LazyApproval, apart from that you can also easily store and retrieve those comments (including ones made via Nintex Forms or directly via the task) into a new task action variable (Task comments).
For those who are specifically interested in capturing from LazyApproval the way you do is by supplying the outcome separated by a comma and then the comments .e.g. ‘Rejected, Need more detail before can approve’.
Check it out and let me know what you think…
The blog/whitepaper is not yet completed. Now that I am back from the US after InspireX17 I will commence writing it up. I will place the link in these comments when it is published.
Great idea, thank you. I will add it to the ideas list for prioritisation.
20 votes2 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
Thank you for the suggestion, and yes we have this on the list for development. It is not scheduled yet, so anyone who is interested in this please keep voting for it. We take Uservoice votes and feedback into account when prioritizing product developments.
This is already available however to see it you need two things. 1. an enterprise license and 2. you need to be signed in with site collection administrator rights.
Also available is the overall Farm view, again this requires an enterprise license and central administration administrator credentials.
From both of these views one can filter to find all sub sites of a particular site or export as CSV and use something like Excel to perform more sophisticated filtering on any column.
Thank you for suggesting this. It has been addressed in the code that is scheduled for general release in the October release.
Jon - Product Manager Workflow