Postable or unpostable changeset

<< Click to Display Table of Contents >>

dpPower > Start working in dpPower > Introduction to the system > Changesets >

Postable or unpostable changeset

The content of a changeset is saved and updates the database only when the changeset is posted. A changeset can have different settings that control how and by whom changes can be saved to the database. The different options and what they mean when working with changesets are described below.

Postable - All changes in the changeset can be posted. Posting means that the changes made to the changeset are saved to the database and thus become visible to other users. This is the default setting.

Unpostable - The changeset cannot be posted. The changes made are only in the changeset and are not available to other users. The choice means that system postings are not performed either.

System posting - Only the system is allowed to post changes to the changeset. An example of when system posting is performed is in connection with operational reports in the Operator module. When the user performs an outage report, the system automatically posts this change to the database.

Private - No one else can review the changeset. It does not appear in the list of changesets. In the graphical view of changesets, private is indicated by a sunglasses symbol. A changeset associated with a task cannot be Private. When the changeset is sent to another user, the changeset remains private, but for the new user.

Use postable changeset when all changes made to your changeset should be postable to the database, thus updating or changing the original data.

Use unpostable changeset when changes made in your changeset should not be able to be posted to the database and thus not update or change the original data. This choice means that system postings are not performed either.

Use system postings when only the system is allowed to post changes to your changeset.