Nathan Woulfe

Hi @ally-gs - this is not a known issue, will check if it's still an issue in the latest dev branch. I have a couple of other updates to release...

Fixed in v1.1.11, will be on nuget shortly.

@lhall690 will look into it. I don't have any issues when running from source, might be a compilation issue in the javascript.

Pretty sure I know what happened here - installing V8 will have created a new entry in the settings table, but there should only be one. If you delete the...

I'll update the installer too to not add a new row if one exists already, assuming this is the cause. If removing the row doesn't work, I'd try deleting both...

I think that's how it previously worked - I've flip flopped a bit with the rejection stuff as it's modifying the state on the workflow and the task, so was...

Hey @willchis this looks amazing! Will find some time to have a proper look at it all, but don't see any reason why this wouldn't be a great addition. Cheers!

That makes sense. Per workflow sounds great, but agree that global would be much easier in the first instance. Issue with per workflow would be were to define that relationship....

Clients are fun hey... Dirty checking the control would be the way to go. The workflow.commentss directive uses no-dirty-check (not sure why), and isn't used for all comment boxes (also,...

Is this only happening on the final stage of a workflow? Hoping so, because if it is it's a relatively simple fix...