I understand that when you end a request in Edit in Workflow the popup is populated with the fields you have defined in a Field Template. So why is there an Edit button which pulls up the request without the fields defined in the Field Template???

---

Regards
Marc Dimmick
MMgmt, Grad.Cert.Mgmt
Mobile: 0418 140 536

"The best way to predict the future is to create it" - Dr.Peter F. Drucker

Hello Marc,

This is designed to give some OnTime users the ability to edit items outside of their Workflow if needed. For instance, a project leader might need to edit a field which doesn't display in the current workflow step, and the regular 'Edit' option is an alternative to moving the item around the workflow until the field is visible.

When 'Editing in Workflow' the workflow step field template is applied, yet while simply 'Editing' an item the project-level template is applied.

Both 'Edit' and 'Edit in Workflow' are available as separate security permissions, therefore you can force your users to only be able to 'Edit in Workflow'.

Let me know if you have any further questions. 

---

Thank you,

Tom Harder
Axosoft Support
support@axosoft.com
1.800.653.0024 option 3
--'Fear the Bug' Podcast--

Is it possible to lock out the edit feature to a security group?

---

Regards
Marc Dimmick
MMgmt, Grad.Cert.Mgmt
Mobile: 0418 140 536

"The best way to predict the future is to create it" - Dr.Peter F. Drucker

Hello Marc,

You can restrict/allow the 'Edit Defect' permission in the security roles to control the overall 'Edit' function for Defects. The same applies to the other item types.

The "Change a Defect's(or other item type) Workflow Step" permission controls whether or not the user can edit the item in the Workflow. Disabling this option will restrict your users to only be allowed to regularly edit the item, and will use field templates applied to the project-level, not the workflow step.

---

Thank you,

Tom Harder
Axosoft Support
support@axosoft.com
1.800.653.0024 option 3
--'Fear the Bug' Podcast--