Welcome to the Axosoft Community, Sign in | Register | Help
in Search

Edit vs. Edit in Workflow question

Last post 09-05-2007, 3:54 PM by Marc.Dimmick. 11 replies.
Sort Posts: Previous Next
  •  11-23-2005, 9:53 AM 5292

    Edit vs. Edit in Workflow question
    I am trying to force people to "Edit in Workflow". I followed a prior description as to how to do that by removing the "Edit Feature" security setting. My problem now is that "Update Item" is grayed out for them. They can still Log Work, but cannot update the Actual Duration. How do I do this?
  •  11-23-2005, 9:55 AM 5293 in reply to 5292

    RE: Edit vs. Edit in Workflow question

    You can have a workflow step update the actual time based on the worklog...so if there was a "final" step you could have it take place there.

    Jonas
    Axosoft


    Axosoft Development Team
    Blog
  •  11-23-2005, 10:17 AM 5294 in reply to 5292

    RE: Edit vs. Edit in Workflow question
    They are not always moving the workflow step, but are logging work. Is there a way to auto-update the items. Is there anything I could run, say once a day or something like that, that would batch update all Actual Durations from the Work Logs?
  •  11-23-2005, 10:22 AM 5295 in reply to 5292

    RE: Edit vs. Edit in Workflow question

    Nevermind this post.

    Jonas
    Axosoft


    Axosoft Development Team
    Blog
  •  02-25-2006, 2:53 PM 5296 in reply to 5292

    RE: Edit vs. Edit in Workflow question

    The question remains a valid one I believe: how do you force users to use the Edit in Workflow instead of the regular Edit in order to enforce the field template of a particular workflow step?

    Using Web version 6.0.2.6182, in the Manage User Security Roles, I have disabled access to Edit Defect and indeed in the Defect List screen and in the View Defect screen, the Edit button is disabled. However, in the View Defect screen, the Edit in Workflow button is still enabled but clicking on it generates an error:

    You do not have the appropriate privilege for the attempted action.

    Basically, in the Manage User Security, there should be two rights to be enabled or disabled for a role: Edit and Edit in Workflow. Also, in the Defect List, there should be two buttons for these 2 actions instead of just one for Edit, which encourages not using the workflow.

    Cheers

    Eric 


    Eric Amiel
  •  03-11-2006, 4:42 PM 5297 in reply to 5292

    RE: Edit vs. Edit in Workflow question

    We have the same problem.
    Will this behaviour be fixed in OnTime 6.1?

    Harry


    Harry Fresacher
    Bellevue Investainment
  •  03-13-2006, 4:30 PM 5298 in reply to 5292

    RE: Edit vs. Edit in Workflow question
    Currently in OnTime there are two security role settings for edit and edit in workflow step functions.

    Info on the Security role for the "Edit item" button:

    The edit item button is controlled by the Edit Defect/Feature/Task security roles in OnTime. The edit item button can be disabled/enabled by removing/adding the Edit Defect/Feature/Task security role.

    Info on the Security role for the "Edit selected item in workflow step" button:

    This button is controlled by the "Change a Defects/Features workflow step" security roles. The edit selected item in a workflow step can be disable/enabled by removing/adding its security role.



    Thank you,

    Axosoft Support

    Dragan Marceta
    www.Axosoft.com
  •  03-14-2006, 7:08 PM 5299 in reply to 5292

    RE: Edit vs. Edit in Workflow question

    Ahhh,

    But the problem there is that if you do not have the ability to change the workflow step - you cannot edit the item or even view it in the Windows Client.

    You should be able to edit an item if you can set a new workflow step or could set it to the current workflow step.  Then users who have just updated the wotkflow step can still open and edit the item but users who can't dset that step or set a new step can't.

    And you should be able to view an item at any time (perhaps with a specific field template - perhaps not) an not be ale to make changes.

  •  03-16-2006, 1:24 PM 5300 in reply to 5292

    RE: Edit vs. Edit in Workflow question

    @SupportRep: Please read the post of eamiel above.
    The behaviour you are describing is just part of the problem and does not make much sense, as stated above.

    Harry


    Harry Fresacher
    Bellevue Investainment
  •  09-04-2007, 9:31 PM 13059 in reply to 5298

    Re: RE: Edit vs. Edit in Workflow question

    This explination I found a little confusing. What I did find is that in the security roles there is an option for edit Bugs, Features, Incidents. The confusing part was there was no reference to edit in workflow.

    After experimenting I found the reference in Security was just for the Edit button and Edit in workflow was provided by default. Hope this may help others having similar issues trying to force people to use Edit in Workflow.


    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
  •  09-05-2007, 3:46 PM 13087 in reply to 13059

    Re: RE: Edit vs. Edit in Workflow question

    Hello Marc,

    The security role permissions are labeled in a way that might need clarification, so let me explain.

    Currently within OnTime 2007, if you have the "Edit" permission enabled for an item type, a user can click the 'Edit' toolbar button and edit it. The field template that's applied will be the one specified at the project level, regardless of an item's workflow step.

    In security permissions, the "Change an <item's> Workflow step" permission is what controls whether or not a user can edit the item 'in Workflow'. Double-clicking an item in the main grid is one way of editing an item 'in Workflow', as is clicking the 'Edit in Workflow' toolbar button. The field template that's applied will be the one associated with a workflow step, if one is applicable. If the current workflow step does not have a template applied, the template will be based on the project-specified field template.

    So, if you enable the "Edit" permission and disable the "Change Workflow step" permission, that role will be able to edit items, and the field template applied will be the project-level template. In this situation, double-clicking an item will default to simply editing the item, not editing the item in the workflow.

    If you do the reverse- disable "Edit" and enable "Change item's Workflow step"- then that role will be forced to 'Edit in Workflow'. If an item resides outside of a workflow step, then the item becomes uneditable. Yet as long as an item already exists in a workflow step, it can be edited. At the project level, you can configure OnTime to force newly created items to begin in a specified workflow step, and in conjunction with this role, you can force your users to edit items in Workflow.

    I know that must all sound a bit confusing, especially at first glance. So let me know if you need any clarification, or if you have anything to add. 


    Thank you,

    Tom Harder
    Axosoft Support
    support@axosoft.com
    1.800.653.0024 option 3
    --'Fear the Bug' Podcast--
  •  09-05-2007, 3:54 PM 13088 in reply to 13087

    Re: RE: Edit vs. Edit in Workflow question

    Thats great, I fully understand now. Thanks you.

     

    Smile


    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
View as RSS news feed in XML

© 2002 - 2007, Axosoft, LLC. All Rights Reserved. | Privacy
Bug Tracking | Defect Tracking Videos | Help Desk Software