When a tag has been manually edited in Historian, what command is required to finalize the changes?

To finalize changes made to a tag in the AVEVA Historian Server, the command required is "Commit Pending Changes." This command is essential because it ensures that any modifications made to the tag during an editing session are saved and applied in the historian database. Until the pending changes are committed, those edits remain in a temporary state and are not reflected in the historical data.

This process allows users to review their edits before finalizing them, thus preventing any accidental or unwanted changes that might affect data integrity. By using the "Commit Pending Changes" command, users are explicitly confirming that they want to apply the changes they have made, transitioning the tag settings from a draft state to a finalized and official state in the system.

In contrast, other options do not effectively capture the intent and need to formally save changes. For example, "Apply Changes" might imply a similar action but does not specifically denote the process of finalizing edits. "End Session" would simply conclude the editing session without saving changes, while "Validate Edits" typically refers to checking data input accuracy rather than committing those changes. Thus, "Commit Pending Changes" is the clear and necessary command to ensure that tag modifications are correctly finalized.