@RobinHunter 

Hi Robin,

Nice to see you here  

> We expected these settings to ensure that all doc connections for this doc class would follow that setting (unless a user intentionally edits the “Update Revision” field).

What you should expect is that all new connections between a document of that class, and any object, should get that value. That's it, a classic "default value".

> Under normal circumstances, releasing a new Rev causes the old rev to become obsolete, and also causes the object connections to be moved to the Latest Released Revision (as expected)

I would not say it's "normal" because it either becomes Obsolete if you have changed the system setting that makes it to be Obsolete (something you do on purpose) or if the user decides to obsolete old document revisions.

What happens "depends", is what I would say.

> This can occur if we find an error in a released doc and need to immediately set it to obsolete (even before we’ve created a new / corrected revision).

I haven't tried this recently so I don't know how it will behave, but would it be an option to make a new revision from one of the older, obsolete, revisions and after that making the revision obsolete? Just an idea to try. This only works, of course, if not all old revisions are truly obsolete and should not be used (then again, you keep them around for a reason, so how bad can they be, worse than the one you want to set to obsolete now? )

> This means that when we do eventually create a new revision of the doc, and then release that new rev, the doc connections are not moved forward to that newly released revision as would be expected. Instead they remain fixed to the old obsolete revision.

The user has the option to move them though, right? It takes manual work, of course.

> My question: Why does IFS change the connections to “Fixed” when there are no released revisions?

This has changed a number of times during the years. Firstly, Update Revision is treated much more strictly nowadays than in some of the older IFS Apps releases. So that's that.

Then I remember we had a long-running customer case where it was very important that old, now obsolete, document revisions, should not be "suggested" to be used in new object connections (or something like it). So, to not "risk" an obsolete document revision being used, we set the connection to Fixed. I hope I'm remembering that discussion correctly. At any rate, we did not add code "just for fun" to make a change like that, so it's done very deliberately. That's another way to say it's not a bug. But it might not work in the most optimal way, at least not for you.

> Wouldn’t it be better to leave them as “Latest Released Revision” (as is specified in the Doc Default Values) such that the connections are automatically moved forward if/when a new revision is eventually released?

It would be better for you , but would it be better for the majority of customers (yes yes, we could add more settings...)? I don't know. And that setting, as I said above, is for when we create the connections. It's not used after that as I remember it.

Is this clearer?

Feel free to add an idea to the Ideas section here on IFS Community to get some setting to control this behavior. Or change or work processes Or ask for a information message to appear when we change those connections to Fixed..., or...