Submitting Change Packages
|
CLI EQUIVALENT
|
si submitcp
|
You submit a change package in order to commit the associated changes to the repository. When reviews are mandatory, submitting a change package begins a review process that must be completed before the changes are committed to the repository.
You can submit change packages containing any combination of deferred, pending, and committed entries.
To submit a change package in the GUI, select the change package, and select > .
Key Considerations
• If exclusive locking is enabled, you cannot successfully submit a change package that contains a deferred check in if you do not have a lock on the member. You must check out the member before submitting the change package.
• Locked change package entries must be converted to deferred check in entries in order for the Submit CP operation to complete. The Check In dialog box displays when a locked entry is encountered. If the Check In operation results in a revision conflict (the revision being checked in is not the member revision) or a lock conflict (another user has an exclusive lock on the member), you can still proceed with the Submit CP operation by selecting the Force Creation of New Branch option.
• You cannot successfully submit a change package that contains deferred Rename or deferred Move entries if another user has a lock on the member.
• You cannot successfully submit a change package if the revision being updated is frozen.
• If a change package is submitted only containing pending entries, you are prompted to commit those pending entries, even if there are no deferred or lock entries.
• If Change Package Description templates are enabled and configured, you are prompted to populate Description template content prior to submitting the change package.