Importing locked objects
When you import locked objects, you are actually importing only the definitions of the locked server objects instead of importing an entire deployed application.
If you try to access objects with locks, you see the following behavior:
- If you try to open an object with a read-only lock, the object opens but you cannot modify its execution conditions, Run If qualification, If or Else actions, and so on.
- If you try to open an object with a hidden lock, you receive a BMC Remedy AR System warning, No information is returned for the hidden locked object. (ARWARN 8838)
On a form with a read-only lock, you cannot create new fields or delete existing ones. When you create a form, add all the form action fields to one or more views and mark them as Hidden if showing them in that view is inappropriate. Then, export the form as locked. When the user imports this form, all necessary form action fields are already present in the form; the user is not required to add form action fields except for choosing which of these fields to be on a specific view.