We're using OnTime 2007. When using the OnTime web interface, if you try to add a new Feature, AND change the Workflow Step to something other than "Feature Requested", the application throws the following error:

Error Message :
"Failed to load viewstate. The control tree into which viewstate is being loaded must match the control tree that was used to save viewstate during the previous request. For example, when adding controls dynamically, the controls added during a post-back must match the type and position of the controls added during the initial request." 

This error message does not happen 100% of the time...but it does happen pretty frequently.  Once the error is thrown, there is no way to go back to the data that you were entering.

We know that people should typically NOT be changing the workflow step when adding a feature...but I had to leave the workflow step field editable so that it could be changed once the feature has been added, and someone is ready to "move" it to the next workflow step.

Also, this is not a problem if you use the Customer Portal interface to add a feature because the Workflow step is not editable through this interface. This is also not a problem if you use the Windows client software.  The tool gracefully allows you to set the workflow step, and does not crash.

Any pointers?

Thanks,

Cory

What's the exact version of OnTime? This should be fixed in 7.1.2

---

Dan Suceava
http://www.axosoft.com

We are running version 7.1.2.7389.

Do you have different field templates for the workflow steps?  What fields change in the field templates when changing the workflow step?

---

Dan Suceava
http://www.axosoft.com

We're using a custom Fields template, but it's the same template for all of the workflow steps.

 

While this is still happening, we did manage a temporary work-around. For now, we've forced all new features into the "Feature Requested" step. This works because we have just started working with features in OnTime and have them all in one folder/project. However, if we decide to move the features into the projects where they belong, the status will change back to "Requested" no matter where they are in our workflow.

For now, this error isn't an issue. I'll post a new topic if we have any issues if/when we decide to make the move. 

Thanks.

Cory

Is expirianced with different templates and because different control order (by moving or hiding controls in template). We could get the values of the controls by using backspace. Second attempt to edit the item always succeds.

You maybe start with no workflow step using the project template and afterwards when changing to WF step you use you common template for all WF steps? My teory assumes that your project and WF templates are different.