Modifying objects
Purpose
You may find that the existing property definitions for an object no
longer suit your requirements and that you need to modify those definitions.
However, when you modify an object, your modifications also affect the
status of all the objects that use that object. You must then re-check
those objects before you can send them to Server for execution. To avoid
modifying object statuses, you can make a copy
of an object and modify the copy.
If an object is already on a Server, it is recommended that you create
a new object revision
rather than removing the object from the Server.
For details, see Object
dependencies.
How to modify objects
Before modifying objects
You can only modify objects:
- To which you have
authorized access
- With the status
Checked or ToBeChecked
- That are not currently
locked by another user (for details, seeLocks
on objects)
Verify the
object status
The status of an object is indicated by the icon displayed next to the
object name both in the left pane and in the Entity
Browser. For details, see Object
life cycle and statuses.
For each life cycle status, the following table indicates the action
you must take to modify an object.
|
|
ToBeChecked
|
You can modify objects with these statuses.
|
|
|
Checked
|
|
|
ReadyToSend
|
You cannot modify objects with this status. To modify the
object, you must send the object back
to design.
Alternatively copy
the object
into your WorkFolder, then modify the copied version of the object.
|
|
|
Archived
|
You cannot modify objects with this status.
To modify the object, you must upgrade
the object and then modify the new instance of the object.
|
|
|
ToBeCommitted
[Transfer CFT only]
|
You cannot modify objects with these statuses. To modify
the object, you must remove
the object from Server.
Alternatively:
- copy
the object
into your WorkFolder, then modify the copied version of the object
- upgrade
the object, then modify the new instance of the object
|
|
|
Committed
|
Modifying the object
From the navigator pane, select the object you want to modify and click 
to display the object properties window.
Composer then checks that the object is not blocked by another user.
If the object:
- Is not blocked
by another user, the properties window opens in the right pane. The object
is now available to other users in read only mode.
- Is blocked, a message
is displayed informing you that the object is blocked by user X.
Because objects exist in a hierarchy of inter-linked dependencies, your
modifications may have an impact on other objects in the repository. Composer
also checks the related objects of the selected object to see if they
are currently blocked by another user.
If a child or parent object of the selected object is blocked by another
user, Composer displays a warning message that:
- Gives the name
of the blocked object and the name of the user who is working on it
- Asks you to confirm
that you want to continue modifying the selected object
If you select to continue with your modifications, Composer opens the
object properties window in modification mode.
If you select not to continue with your modifications, Composer opens
the object properties window in read only mode.
For information on how to complete object property definitions, refer
to the relevant topic for each object. Where it is not possible to modify
the existing entries, the fields are grayed out.
After modifying objects
After you modify an object, you must:
- Check the object and all objects that use it
- Save
the object
- Close the object
properties window - Composer unlocks the object
Check the
objects that use the modified object
When you modify an object, Composer:
- Changes the status
of that object to ToBeChecked
- Looks for any objects
that use the modified object, and changes the statuses of those objects
to ToBeChecked
You must then re-check the objects that use the modified object. For
details, see Checking
objects.
Use the Dependencies
Browser
to see which objects use the modified object.