I think I need some clarification... So prior to 9.3.1, when you are running tools (models/script tools) that had to edit your data in some way, like calculating fields, you could run these tools in and out of an edit session. In 9.3.1, if you ran these same tools out of an edit session, you encountered an error message. I believe a patch after the 9.3.1 release "fixed" this behavior so that you can run these tools in AND out of an edit session once again.
I say this because we had two machines up with just 9.3.1 and another with 9.3.1 with the latest patch installed (I have to remember which one that was). Well the regular 9.3.1 release showed this new behavior, while the 9.3.1 + patch "fixed" it back again.
Personally, I liked this data "safeguard" in 9.3.1. By designing it so that these tools can only work in an edit session, ensures that editors always have the option of doing an UNDO if they (or the tool) makes a mistake. It also notified them that if they wanted to edit the data, they needed to start an edit session. 🙂
While testing in 9.4, I also found that you can run these tools out of an edit session... So my questions are:
Why are editors able to run tools (that edit the data) out of an edit session? Do more customers prefer this behavior? Does it have to do with running scripts doing mass edits for maintenance purposes?
As an enhancement request, can we have the option to change a setting on the toolbox or tool (model/script tool) where you can only run it during an edit session? This would greatly help us at our organization, especially when we may not share the same workflows as the next agency.
Thank you very much!
BTW, I am not sure if this is in the right category as it also deals with editing... You can move it.
