Before I open an LP on the Template Editor, I'm curious about the work flow. In particular, if there was a menu option / bookmark that took you directly to the attribute editor for an item -- it doesn't matter which item, since you don't have to save changes to the item -- would it be materially different than having a separate Template Editor?
I get that modifying an item without really saving changes to the item itself just to affect a template seems odd, but you have all the tools you need in the attr editor to manage the templates. So I guess it's a question of priority. Is the one-interface approach where you pretend to edit an item just too weird?
Thanks again for the input and testing, Elaine.
Before I open an LP on the Template Editor, I'm curious about the work flow. In particular, if there was a menu option / bookmark that took you directly to the attribute editor for an item -- it doesn't matter which item, since you don't have to save changes to the item -- would it be materially different than having a separate Template Editor?
For example:
https:/ /HOSTNAME/ eg2/staff/ cat/volcopy/ attrs/item/ 1
I get that modifying an item without really saving changes to the item itself just to affect a template seems odd, but you have all the tools you need in the attr editor to manage the templates. So I guess it's a question of priority. Is the one-interface approach where you pretend to edit an item just too weird?