Restrict user from creating Parts.
User should be able to do only save as on existing objects. But when we assign only “SaveAs” privilege, without “Create” Privilege user is unable to do save as. Agile throws exception. Can someone please help me how to achieve this either with configuration/sdk.
Wow, that is a very interesting use case. To break down what you are seeing, the SaveAs is simply a copy function that grabs the values and then goes into a Create mode so inherently you cannot use SaveAs without Create. Yet let’s explore what you are looking to accomplish. As I understand you have a set of users that may create, then another level of users who may only use SaveAs from those created. This may need to have a PX to fully reach the level of performance you are seeking. Just thinking off the cusp on Criteria and if I set a rule for discussion sake that the Item needs to be in a RELEASED state, then I could use SaveAs which would then appear in the Actions menu. On the flip side if I attach the Criteria that the Items needs to be in a RELEASED state and attach that to the Create privilege and assign to the user… would that function? All-in-all I am skeptical that we may reach an acceptable function using the config. Try the idea out and let me know if it works. Otherwise look to a PX to provide the capability.
Hi mg,
As Patrick wrote above, the “save as” feature is an equivalent to Create new. The reason this feature exists is to simplify the creation of objects and reduce errors (filling in the same fields). In my opinion, trying to restrict users to use only Save As while not enabling them to use Create New is incorrect process implementation.
I personally think that it would be more correct to implement the process of item creation correction within the organization rather to figure out how to implement within the IS criteria which disable a user the ability to use the basic create new option.
Best regards,
Ron Ziv
Hi Patrick,
As you suggested, i tried creating a criteria and tag this to the ‘Create’ privilege, but the “criteria” at class level cannot be tagged to Create privilege 🙁
I tried this with px- custom px (Action Menu), its working fine. Once the px is triggered, i am displaying a message- saying “<Object Number> Created!”, but then again this is not very user friendly, as user has to note down new object number – search for it and then do the modifications if any.
Hi Ron,
I understand what you are saying, but our costumer need this functionality.. So thought of giving it a try.