1 of 1 people found this helpful
In your effectiveness settings it gives a point each time the article is opened and tries to write that to an "Effectiveness" attribute. I would assume that because it's in that read-only status, it can't append that effectiveness rating. You might be able to change that setting to 0 instead of 1 in Knowledge Administration so it doesn't try to write a point. If that doesn't work, you might have to change that status back to a Read/Write status until 7.6 comes out at which point you can dynamically make certain fields on the form read only based on other attributes.
Unfortunatley setting all of the effectiveness values to 0 didn't have the desired effect. It still throws up the error. As an aside, in the Console you conly get this error if you have the effectiveness attribute on the window wheras in Web Access it errors regardless.
This seems to me a fairly fundemental issue. I would have thought a typical deployment of knowledge management would use a read-only status for the aprroved status of an article, and therfore come across this problem?
Changing the approved status to read/write isn't really an acceptable solution imho as how would we stop anyone changing articles without it going through the required approval process?
I agree. This could be a known issue. Might be worth buzzing support to see if anyone else has reported this.
I've logged with Support. Thanks Jamie for help thus far.