issue with cloning function in workflows - V 1.91.2099

Plugins & Plugin Development Alternate UI
1

amg, thank you for implementing this!
The table to easily change devices makes that brilliantly usable.

On my initial testing I have found this:

When you clone one workflow and choose new devices via the exchange table the cloned workflow has the same workflow id as the original one. On the cloned workflow the newly chosen device is not there, still the old one.
Changing the name on the new workflow alters the name of the original one (probably to do with identical ids)

2

[quote=“pls90, post:1, topic:197177”]amg, thank you for implementing this!
The table to easily change devices makes that brilliantly usable.

On my initial testing I have found this:

When you clone one workflow and choose new devices via the exchange table the cloned workflow has the same workflow id as the original one. On the cloned workflow the newly chosen device is not there, still the old one.
Changing the name on the new workflow alters the name of the original one (probably to do with identical ids)[/quote]

oups, I will release a hotfix in version 2099. that is the hotfix =>

3

new release has solved all the mentioned issues, thank you!

4

I did some more testing.
As stated earlier the initially reported issues are gone.
I came across one other thing.
Cloning a workflow and subsequent saving of all workflows leads to a duplicate state id warning between the new workflow and a different one that was not cloned (see attachment).
The debug function gets rid of it, but I wonder how 2 not in any way related workflows can cause that problem.

5

[quote=“pls90, post:4, topic:197177”]I did some more testing.
As stated earlier the initially reported issues are gone.
I came across one other thing.
Cloning a workflow and subsequent saving of all workflows leads to a duplicate state id warning between the new workflow and a different one that was not cloned (see attachment).
The debug function gets rid of it, but I wonder how 2 not in any way related workflows can cause that problem.[/quote]

independant issue not linked to that new functionality. because you have lots of workflow , the “save all” is big. it seems vera has some issue when somebody saves data into device variable inside a device “handler” ( which is what ALTUI is )at the same time the engine is doing something ( potentially a reload for instance ), this happens sometimes, even without cloning any workflow. the debug is the only way I am aware of to avoid that