Before creating a new revision
What happens when you create a new revision
You can create a revision of any type of object, on condition that:
- ToBeCommittedXFB Monitor CFT only
- Committed
- Archived
For details, see Object life cycle and statuses.
To create a new revision of an object:
- Name: the name of the selected object and all objects that use it
- Status: the status of each object in the list
- Revision Name: by default, the revision name is set to 2 for the first revision. This number increments for each subsequent revision that you create.
The name of each object revision comprises the object name followed by the revision name or tag. By default, the revision tag is a number that increments for each subsequent instance that you create. For example, MyBusiness-Document_[2
Optionally, modify the default revision number and assign a name to the object instance.
To modify the revision name:
- Double-click the Revision Name field and enter a name.
- If you enter the name MyRevision, the next time you create a revision of that object, its revision name is set to MyRevision2.
Note: When you have created at least one revision of an object, you can no longer modify the object name.
The revision number is displayed in the tooltip when you position the cursor over the object name in the left pane.
To view previous revisions of the object, use the History Browser.
When you create a new object revision, Composer:
Because objects are often interlinked in a network of dependencies, creating a new revision of an object may involve creating a new revision of all the objects linked to it. To ensure coherence in the network of object dependencies, Composer creates a Broadcast Group for each Axway Server where the previous revision of an object was sent. A Broadcast Group is an object that groups several objects for a given Axway Server.
Composer displays the Broadcast Group in the History Browser.
When you create a new object, Composer assigns the tag number [1] to the new object. This is the first instance of the object. After you send object [1] to Server, you can then create a new revision of this object. The first time you create a new revision of object [1]:
You can then make the required modifications to revision [2], check the object and send it back to Server. Revision [2] replaces revision [1] on the Axway Server that you specify. Object [1] is archived and is available via the History Browser. Its status is set to Archived and it is non-modifiable.
The archived object retains all dependency links with its child objects.
The results of the operation depend on the following factors: