Forcing uploaders to name flows

Post your feature requets for new triggers, conditions, actions and other improvements.

Moderator: Martin

Locked
angelatwork
Posts: 186
Joined: 12 Feb 2014 01:45

Forcing uploaders to name flows

Post by angelatwork » 21 Feb 2014 16:34

Hi,
I just tried to download two flows, but was denied because they were called flow 1 and flow 2.And since I have several flows in the baby state (not worth naming yet) on my android.

My suggesting is that you have to name your flows that you upload with a name other than flow1,flow2 and so on. It will also be better information and identification.

Best regards
Best regards,
AngelAtwOrk

User avatar
MURTUMA
Posts: 697
Joined: 05 Mar 2013 22:43

Re: Forcing uploaders to name flows

Post by MURTUMA » 21 Feb 2014 17:08

Better would be automatic renaming, I.e. "Flow1 (1)".

User avatar
Martin
Posts: 4468
Joined: 09 Nov 2012 14:23

Re: Forcing uploaders to name flows

Post by Martin » 21 Feb 2014 18:21

Automatic renaming can be difficult since a flow/widget might use Execute Flows or setWidgetElementProperty or similar actions that depend on the names of the flows/widgets.
I agree that there should be at least a warning before a flow with a name like Flow X is published in the forum. I will add a check for this.

angelatwork
Posts: 186
Joined: 12 Feb 2014 01:45

Re: Forcing uploaders to name flows

Post by angelatwork » 21 Feb 2014 19:47

That's good enough, if it is possible :-)
Best regards,
AngelAtwOrk

Locked