Or leave us a private message
Hey guys, would it be possible to add a Refactor option, so that should a Proc change and be deployed to live server, that we could easily update the various usages of that proc on all the workflows in which it is used? I realise that some workflows may need to be changed when a proc changes, but it could be that the revised proc just returns an additional field which is only used by one workflow, which means that it wouldn't effect the rest of the workflows, as this additional field would be ignored within all the other workflows using the proc?
As it stands, changing the underlying proc will only affect services that change accordingly. If you add a field to the proc, you only need to change the instance that needs that change, the others will simply ignore it by default. However, they will all show in a warning state so that you know which ones are not completely up to date. If this is not what you mean, please let us know.
I am battling to find the risize marker to make this assign box bigger. It would be nice if this could be made more obvious or if we could resize from any of the 4 corners.
Check out the latest release!
Cannot connect my db call to the decision to continue the workflow?
I cannot get the connector link squares on the service?
The tool has been connected to itself already so the grips are not showing. It doesn't look like this is intended behaviour, so delete the link to itself and the grips will appear
Suggestion: auto-text on assign
Thanks. The intellisense box now appears after you type either part of the variable name or [[
Good one Alex. This should be in from 0.3.3.0
Customer support service by UserEcho