No direct corresponding action. Using the App Step will get you elevated privileges if you need that.

Tip for Sharegate migration that I'm sure you're aware of, edit all on-prem workflow to remove all Action Sets before migration as Sharegate won't migrate Action Set including anything within, even if it can migrate the actions within.

Hi Warwick!

Thanks for the answer. Yes, I noticed that in online action "Run If" does not have the option to run as the work-flow owner as it has in on-prem versions. I guess "app step" will do the trick but must test it.

About the tip - yes, I am aware of this inconvenience as I faced it already. This is why I am looking for a solution.

Your proposition is to break the "action step", put all action nested outside it and then migrate to online? Then after migration group those actions again using app step?

One important thing I see for the "app step" to be available is to activate feature from site level "Workflows can use app permissions". 

Regards,

Tomasz

Tomasz,

As Warwick mentioned, its not available in O365 yet. The action is for display purposes mainly and something that is on the roadmap for O365.

Your approach to break up the actions is best when migrating your workflows at the moment and hopefully doesn't cause too much trouble for you in the interim. 

As for run as workflow owner, use app step to achieve that and everything else should be good to go.

Eric

All - I submitted a critical feature request to Sharegate that they should be able to migrate the actions within an action set to NW4O365 (if those actions are themselves supported), without migrating the action set.  Seems like they were going to expedite that. But I have no date commitment for that.  I mentioned that we had some workflows that used action sets extensively and there for could not be migrated at all unless we were to redesign the existing workflows first.

Tom, that is a very good news indeed!

I have a client who has almost everything stored in action sets (they have a veeery large workflows and uses them mostly for increasing their readability), even putting action sets within other action sets so redesign those workflows will be really painful...

Regards,

Tomasz

Hi! Just a follow up. According to the recent status change in this "User voice" forum topic: https://nintex.uservoice.com/forums/218291-3-nintex-workflow-for-office-365/suggestions/6668806-uda-support Nintex has already started working over implementation of UDAs in O365 Nintex Workflow

So does this mean that Action Set can be mapped to App Step. Is this something that can be set up in sharegate?

No.. You have to take all actions from inside of the action step migrate that way modified workflow and then wrap up in app step if needed.

I have hundreds of Action Sets. This will be a nightmare.

I would really rather the ability to map Action Sets to App Steps. Is this something Sharegate could implement? Or does it have to come from Nintex?

Kind Regards

Joanne Morris

Technology Systems Analyst

Technical Services

Thiess Pty Ltd

179 Grey Street, South Bank QLD 4101

Locked Bag 2009, South Brisbane QLD 4101

T +61 7 3002 9428

E <mailto:jmorris@thiess.com.au> jmorris<mailto:jmorris@thiess.com.au>@thiess.com.au<mailto:username@thiess.com.au>

thiess.com<http://www.thiess.com/>

<http://www.thiess.com.au/>

<http://www.facebook.com/ThiessGroup>

Action Sets are still under development for O365 but it is said they will be introduced soon (check the http://nintex.uservoice.com/). However even after they are present Sharegate will have to include their support in their migration tool.

Further speaking - I do not know if there is any better counterpart for Sharegate for Nintex migration. Sorry

And yes, I understand your pain as I went through it recently too. Maybe not hundreds, but the number was also devastating. And sorry to say this - that is the only way, to break down action set and put all actions inline. Be aware there are many more actions not supported during migration, as "foreach" - for that purpose you should breakdown each such "containing" action and put all inside actions inline, then after migration re-build your workflow. If you won't do that, after migration you will get only blank placeholders with names, but no underneath actions will be present.

Regards,

Tomasz

Well, it needs to be in the next couple of months or we will be unpacking 100s of 'Action Set' actions to enable transfer of workflows from 2010 to 365. Not to mention UDAs and possibly child workflows.

Kind Regards

Joanne Morris

Technology Systems Analyst

Technical Services

Thiess Pty Ltd

179 Grey Street, South Bank QLD 4101

Locked Bag 2009, South Brisbane QLD 4101

T +61 7 3002 9428

E <mailto:jmorris@thiess.com.au> jmorris<mailto:jmorris@thiess.com.au>@thiess.com.au<mailto:username@thiess.com.au>

thiess.com<http://www.thiess.com/>

<http://www.thiess.com.au/>

<http://www.facebook.com/ThiessGroup>