Restrict element status change for user group

[Daniel Machado]

We would like to lock the ability to change the status of an element to a specific group of users. For instance if a user creates a class it should be set to Proposed - as it happens now. However we need to stop users from setting the status to Approved - this one should be limited to a group.

Does anyone know if this is supported somehow?

Thanks
Daniel

[Tas]

I would love this as well.  It would be very useful in our organisation, where the business process model is owned by various parts of the business, and is meant to represent the actual business processes in use.  I would like to delegate out maintainance  of various parts of the model, but provide a controlled status update to a small group of users.

[smendonc]

The below might work for you, but it assumes you are using the corporate edition as that one supports security.  The same technique works for either a database repository or an eap file.

Assuming security is turned on for the model.

1. Create a security group such as 'RequirementGroup'. From the menu choose Project --> Security
2. Add only the users who will be allowed to make changes to this group
3. Group Lock the necessary element using the group 'RequirementGroup'. Right click the element in the project browser and choose 'Lock...'

From this point on only members of the 'RequirementGroup' have the ability to update the element, unless the lock is released.

Limitations:
1. New elements are not automatically locked.  A member of the owner group needs to explicitly lock the element.
2. The granularity of the lock is the whole element.  This means I cannot provide the ability to update the status field to one group, but the ability to update the notes filed to another.

Stan.

[Daniel Machado]

Thanks Stan for the feed-back. We have the corporate edition and we may try locking the element to a group.

However the issue we are trying to prevent is that users creating the element should not be able to select every available status. They should be restricted to "Proposed" for instance.

Thanks again
Daniel

[jsbueno]

Hi Daniel -

this "state machinne"  ability is obviosuly a need by a lot of proccess. In our organizatin we have opted to export EA elements via CSV and track their state in a ticketing tracking software with proper support for a state machinne. For the moment the ticket software is Jira.  Of cours, with the use of jira in paralllell the overall usefullness of EA drops dramatically.

[Kimbo]

Guys,

I thought my question fitted into this thread well..

How can we change the default status from "Proposed" to another value? We've created a type called "WorkInProgress" that we'd like to use as our default

Thanks for any help

Kimbo