search

octoblu / issues

The place to report Octoblu issues
3 stars 2 forks source link

Unable to bluprint flows #234

Closed brianehlert closed 8 years ago

brianehlert commented 8 years ago

The attached flows will not bluprint LiveDemov4.json.txt

brianehlert commented 8 years ago

The one pattern that I have now noticed. If I copy and paste nodes in the Designer, then I am not able to bluprint.

brianehlert commented 8 years ago

CalendarSample.json.txt

brianehlert commented 8 years ago

I created a new flow. Then updated it with the Nodes, Links, Name, and Description from this JSON source. I have the same result of not being able to bluprint.

brianehlert commented 8 years ago

This has to be tied to the number of or content of Compose Nodes that I have. I exported the JSON and then imported into a new flow and the compose nodes went all strange and broke all of the strings within a compose node into sub arrays.

brianehlert commented 8 years ago

Pretty sure that the root of the issue is me declaring array positions in compose nodes for keys. key = payload.Lync[0].Command

(Jade told me I could and showed me how) ;-)

iamruinous commented 8 years ago

I think we got this fixed. There was a problem using dynamic keys in the compose node. You may need to hard-refresh to make sure you get the latest version of the compose.html page.

brianehlert commented 8 years ago

My flows still don't bluprint. Went as far as closing browser to reset. Has the change been pushed?

iamruinous commented 8 years ago

Be sure to click on your compose node and make sure everything looks ok

brianehlert commented 8 years ago

I just clicked on my compose nodes in one of the flows that did not bluprint and (thankfully) I don't care about. When I select the Compose nodes, nothing displays. They appear blank (with no key value pairs)

iamruinous commented 8 years ago

you may have to clear your cache. The HTML page changed but the browser doesn't seem to notice it.

brianehlert commented 8 years ago

I fear clicking on the compose nodes in my critical flows. The simple one that no longer displays has 1 trigger. and 4 compose nodes. and three delays, and one target device Each compose node has two or three key value pairs.

Such as: CloseApp = payload.Lync[0].Command DoItNow = payload.Lync[0].Argiment

brianehlert commented 8 years ago

I have to dump my cache entirely? Closing an re-opening is not picking up the change? (this is firefox)

iamruinous commented 8 years ago

I had to clear my cache to make it work. I couldn't get Chrome to recognize the new page, even though no-cache is turned on for that page.

Or try a different browser.

brianehlert commented 8 years ago

Okay, that did it for FireFox too. After I forced it to clear the broswer cache, it displayed the Compose correctly and allowed me to BluPrint one of the flows.

The most complex of the flows still does not bluprint.

If the issue is sitll Compose node related it has one with {{ }} combined with the dynamic keys. One with a dynamic key that is three nested keys in the array, plus a key that is not dynamic.

An another a bit more complex: CloseApp = payload.Lync[0].Command DoItNow = payload.Lync[0].Argiment CloseApp = payload.Lync[1].Command DoItNow = payload.Lync[1].Argiment CloseApp = payload.Foo[0].Command DoItNow = payload.Foo[0].Argiment

brianehlert commented 8 years ago

The key to this ended up being a change in the Compose Node. The 'older' version of the Compose Node that were in my flows would not blueprint (or save after the above fix was implemented). The workaround required that I open each compose node in the designer so that they would update and then the flow would both blueprint or save.

The issue that I would like to see derived from this is that there either needs to be a better way to update nodes, or there needs to be a less manual process, possibly a flow level process when I investigate a flow that is not functioning instead of node by node. In the end, the requirement should be less stumbling and manual intervention required by the customer.