Workflow task properties not saving. Cannot set start task
Hi,
Just tried this out on a 4.7.2 installation and, while everything appeared to be working normally I noticed that none of the properties on the work flow tasks where being saved i.e. "Is Start Task" etc.
I created the basic approval flow as per the intro video, with the difference being that it was instantiated via the SendToPublish event, which in my opinion is a more obvious choice than cancelling the Publish event. However, when testing the scenario I get a YSOD staying that no start task had been defined. Being sure I had defined one I checked the workflow designer and noticed that it wouldn't save and of the task settings.. and gave no indication as to why ?
Any ideas ?.. has this been used on 4.7.2 before ?
Also, the uninstall of the package totally wrecked my umbraco installation i.e. left things in web.config that should have been removed, actually deleted my umbraco.aspx page and caused issued with tree node rendering.
When I say "doesn't save task properties", I am actually referring to the save button on each individual task rather than the save workflow & close (designer) button.
I did notice the warning during installation and decided to proceed anyway.. I was just wondering if this was a know problem on 4.7.2.
Are there any possible permission issues here ? I find it odd that the workflow itself seems to save (i.e. layout, tasks etc) but the task properties themselves don't.
It isn't a known issue - but as I say I haven't throughly tested with 4.7.2.
Just to be clear, asked you've clicked Save Task properties on the individual tasks you also have to save the workflow design using the buttons at the top.
It may be worth monitoring the requests that workflow is making using firebug or similar to see if any of the requests made throw an error.
I've had to abandon testing for now but hopefully i'll get a chance to try again before the end of the week. I'll probably try it on a clean install too just to be on the safe side. I'll post my findings either way
I have also been seeing this bug where any changes made to the Task Properties and clicking 'Save Task Properties' is not saving any changes made.
I am using Umbraco 4.7.2, Workflow 1.2 and uComponents 4.1.0.
The following error is thrown in the Chrome Dev tools 'Uncaught Reference Error: Umbraco is not defined' - this is linked through to WebResource.axd file. The first few lines of the javascript where it is failing is below:
I also tested this functionality on a new Umbraco 4.7.2 instance with Workflow 1.2 installed without uComponents installed - and the 'Save Task Properties' did work correctly. As soon as I installed uComponents the above JavaScript error is thrown and Save no longer works. So it looks like uComponents could be the culprit here.
Any ideas of how we can use & configure the Workflow with uComponents installed.
I have this problem as well, and I have uComponents installed. I am not certain if that is the javascript with the error, but I know that I receive javascript errors:
Uncaught TypeError: Cannot set property 'position' of undefinedWebResource.axd:149
Actually, upon closer inspection, Umbraco.Conrols.UmbracoTree is created 2 lines later .. not entirely sure why this is failing. Does it need the higher levels created first?
Sorry for the delay. Yes, I was having the same error as you. I was able to fix it by disabling uComponents in the <modules> section of the Web.config file (instead of disabling it in the <httpModules> section of the file, as the post you mentioned pointed out).
Workflow task properties not saving. Cannot set start task
Hi,
Just tried this out on a 4.7.2 installation and, while everything appeared to be working normally I noticed that none of the properties on the work flow tasks where being saved i.e. "Is Start Task" etc.
I created the basic approval flow as per the intro video, with the difference being that it was instantiated via the SendToPublish event, which in my opinion is a more obvious choice than cancelling the Publish event. However, when testing the scenario I get a YSOD staying that no start task had been defined. Being sure I had defined one I checked the workflow designer and noticed that it wouldn't save and of the task settings.. and gave no indication as to why ?
Any ideas ?.. has this been used on 4.7.2 before ?
Also, the uninstall of the package totally wrecked my umbraco installation i.e. left things in web.config that should have been removed, actually deleted my umbraco.aspx page and caused issued with tree node rendering.
Hi,
When you set a start task you first have to save the task properties - at the bottom of the right hand pane and then save the workflow itself.
4.7.2 isn't *officially* supported as the installer tells you - but I do have clients who are running without issues on 4.7.2
The uninstaller is a feature of Umbraco and not my package - I'm afraid that it doesn't always do a great job of removing packages.
Hi Darren, thanks for responding so quickly.
When I say "doesn't save task properties", I am actually referring to the save button on each individual task rather than the save workflow & close (designer) button.
I did notice the warning during installation and decided to proceed anyway.. I was just wondering if this was a know problem on 4.7.2.
Are there any possible permission issues here ? I find it odd that the workflow itself seems to save (i.e. layout, tasks etc) but the task properties themselves don't.
Cheers
Dave
It isn't a known issue - but as I say I haven't throughly tested with 4.7.2.
Just to be clear, asked you've clicked Save Task properties on the individual tasks you also have to save the workflow design using the buttons at the top.
It may be worth monitoring the requests that workflow is making using firebug or similar to see if any of the requests made throw an error.
Yes, that's the process I've used.
I've had to abandon testing for now but hopefully i'll get a chance to try again before the end of the week. I'll probably try it on a clean install too just to be on the safe side. I'll post my findings either way
Cheers
Hello Dave - I've released a new version today - I've verified it with 4.8 and all works well so maybe try with that and let me know how you get on.
Hi Darren,
thanks. Just back from vacation so will give it a go when I get an opportunity. Will feed back
Hi,
I have also been seeing this bug where any changes made to the Task Properties and clicking 'Save Task Properties' is not saving any changes made.
I am using Umbraco 4.7.2, Workflow 1.2 and uComponents 4.1.0.
The following error is thrown in the Chrome Dev tools 'Uncaught Reference Error: Umbraco is not defined' - this is linked through to WebResource.axd file. The first few lines of the javascript where it is failing is below:
I also tested this functionality on a new Umbraco 4.7.2 instance with Workflow 1.2 installed without uComponents installed - and the 'Save Task Properties' did work correctly. As soon as I installed uComponents the above JavaScript error is thrown and Save no longer works. So it looks like uComponents could be the culprit here.
Any ideas of how we can use & configure the Workflow with uComponents installed.
Thanks
I have this problem as well, and I have uComponents installed. I am not certain if that is the javascript with the error, but I know that I receive javascript errors:
My steps are:
Hmm.. That may be a red herring. I get those errors just clicking between tasks as well.
More information:
umbraco v 4.7.1.1 (Assembly version: 1.0.4435.22807)
When loading the workflow editor () I get:
When the page loads. The line of code it is referencing is:
varorg=Umbraco.Controls.UmbracoTree;
it seems like maybe javascript resources are being loaded in the wrong order?
Actually, upon closer inspection, Umbraco.Conrols.UmbracoTree is created 2 lines later .. not entirely sure why this is failing. Does it need the higher levels created first?
I am still having this issue and I am running:
umbraco v 4.9.0 (Assembly version: 1.0.4910.12817)
uComponents 5.4.1
Is there any more information I can provide to resolve this issue? This clearly makes the package a non-starter for us.
Hi Doug,
None of the information provided suggests to me that this is an issue with Workflow - I'd try the same in a clean install without uComponents.
Do you have any idea what this Umbraco reference is so I can try to track this down?
I also get these errors when I open the properties editor (the other is from the designer)
For anyone having a similar problem, this seems to be my problem: http://our.umbraco.org/projects/backoffice-extensions/ucomponents/questionssuggestions/17891-Script-tag-on-rendered-page
I have not yet had a chance to upgrade uComponennts, but I disabled the module in the web.config and things are working.
Hey Doug,
Did you do anything else after disabling the module in your Web.config? Disabling the module did nothing for me in my Umbraco installation.
As I recall, that was all. Are you getting the same error I was?
Hi Doug,
Sorry for the delay. Yes, I was having the same error as you. I was able to fix it by disabling uComponents in the <modules> section of the Web.config file (instead of disabling it in the <httpModules> section of the file, as the post you mentioned pointed out).
is working on a reply...