Process Extension Privileges

We have created our first process extension. It is triggered on the Actions Menu. It is an attribute on a page 3 Part object.

How do I control who is allowed to edit this field? As an administrator I am able to trigger the extension in any stage of the part object lifecycle. When I log in as a standard user I get an error that the process extension was not complete. “No value assigned”

Add Comment
3 Answer(s)

Assign additional roles to the px to update the attribute on Page 3 part object.

Agile Angel Answered on May 19, 2016.
Add Comment

When I assign the role to the px, it gives me an exception error. When I assign the role to a specific user it will only allow it to work if they can modify in all status’ of the part object. If I add a statement of “if the part is in Preliminary”, it gives me an error message and doesn’t assign the value. I don’t want the user to be able to add the value if the part is Released.

Agile User Answered on June 3, 2016.
Add Comment

Hi Nelly,

    you can check for the part or change also.

Pseudo:

if(part is released) then assign attribute to field

Here a sample for Change type object:

private static boolean isReleased(IChange change) throws APIException {
 return (change.getStatus().getStatusType().
 equals(StatusConstants.TYPE_RELEASED);
}

PXs are executed with the privileges the executing user has, but it is always good to let him know why the PXs did not do it’s job. For example by returning an Action result like ” Value not assigned, as part is already released”

Agile Angel Answered on June 3, 2016.

Is it not possible to do this on the front end just with the roles and privileges? Is this happening because of the way the actual extension was written?

on June 9, 2016.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.