Committing a Change

Committing a change signifies that the change has been committed from the development database to the production database and thus is no longer considered a "change". A committed change is no longer taken into account when issuing the Notification of Past Changes warning message.

Changes must be set as committed manually. It can be done in either of the following ways:

• Setting the Committed flag in the Log editor to true sets the logged change as committed
• Setting the Committed flag in the Log Comment editor to true sets all logged changes sharing the same comment as committed

The rather vague term "recently changed object" used in the Background Information topic then actually means "object which has not been committed yet".