To revise a business object, use this syntax:
revise bus TYPE NAME REV bus TYPE NAME REV1
- The first object must be the last in its revision family. If not, the
command will error with
Business object is not revisionable. You cannot insert
a revision into the middle of an existing revision family.
- If the second object belongs to a revision family, the command will
work, but will issue the warning
Business object being inserted will be removed from its
previous revision chain.
Creating new revisions has several side effects. When appending to a
revision sequence with the command, these behaviors are handled as described
below:
- Float and Replicate rules. Ordinarily the float and replicate rules
for relationships cause relationships to be moved or copied to new revisions.
These rules are ignored; no relationships are added or removed to or from the
inserted object, nor are any relationships added or removed to or from any of
the previously existing members of the target sequence.
- File Inheritance. Ordinarily, a new revision of an existing object
inherits all files checked into the original object. When using this interface,
if the appended object already has checked in files, it does not inherit any
files from the revision sequence. If the appended object has no files checked
in, the behavior is controlled by the file keyword
in.
- Triggers. No triggers will fire.
- History. Revision history records will be recorded on both the new
object and its previous revision (that is, both objects that are specified in
the command).