Or leave us a private message
Unload external dlls from the designer
However in discovering this I rebuilt my dll a number of times. I couldnt copy it to the place I had referenced because warewolf has a handle to that DLL. Im assuming you host components like this in a separate appDomain so if you give me the ability to recycle that so I can do a build / deploy cycle without me having to shutdown warewolf would be great. If you can already do this and I just havnt figured out how, ... well then shame on me :)
decision trees getting cluttered
Income > 10000 goes to the 1st outcome, >8000 the 2nd and > 5000 the third.
In the current version you have to make a tree looking like the left pic in the diagram.
If you attached priorities to a decision you could make it look like the second diagram. Say your income is 9000, you will fail the first check but pass both 2 and 3, however if you have a priority you would pass the income > 8000 check and stop evaluation at that point. Maybe a useful idea? Things like risk pricing models would benefit greatly from this and the designer space would look far less cluttered
My guess is you are talking about bundling up individual decisions into a single decision tree activity that would act like a switch.
Is this correct?
Decisions should have a heading. Just showing the first condition is less than ideal.
if A==1
AND IF B==0
the decision reads "If A==1" in the designer canvas which is acttual misleading
We also added the ability for you to put the text there that you want (check the bottom of the decision) so you can overide the default.
Refactor option
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.
Resize
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.
Cannot connect db call to decision
Cannot connect my db call to the decision to continue the workflow?
I cannot get the connector link squares on the service?
Hi Alex
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
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
Service d'assistance aux clients par UserEcho
