7.8.5.3 ConfirmUpdate
The ConfirmUpdate Method allows a Client to confirm that it can connect after the configuration has been applied. The Client shall disconnect from the Server and reconnect before calling ConfirmUpdate. The RevertAfterTime parameter passed to the CloseAndUpdate Method specifies how long the Server shall wait for confirmation.
If the Server could not apply all changes then the return code is Bad_TransactionFailed and no changes were applied.
If the Method is called too soon the Server returns Bad_InvalidState.
The permissions needed to call this method shall be specified by the subtype and should require one of the administrator Roles.
Signature
ConfirmUpdate(
[in] 0:Guid UpdateId
);| Argument | Description |
| UpdateId | The id returned by CloseAndUpdate. |
Method Result Codes (defined in Call Service)
| Result Code | Description |
| Bad_TransactionFailed | An error occurred applying the changes and they have been rolled backed and the ConfigurationVersion does not change. |
| Bad_UserAccessDenied | The current user does not have the rights required. |
| Bad_InvalidArgument | The UpdateId is not valid or is no longer valid. Any transaction associated with the UpdateId has been rolled back. |
| Bad_InvalidState | The Server has not had a chance to apply the changes and the Client needs to wait and call the Method again. |
| Bad_SecurityModeInsufficient | The SecureChannel is not authenticated. |
Table 28 specifies the AddressSpace representation for the ConfirmUpdate Method.
| Attribute | Value | ||||
| BrowseName | 0:ConfirmUpdate | ||||
| References | NodeClass | BrowseName | DataType | TypeDefinition | ModellingRule |
|---|---|---|---|---|---|
| 0:HasProperty | Variable | 0:InputArguments | 0:Argument[] | 0:PropertyType | Mandatory |