Class MxaccessGateway.AcknowledgeAlarmReplyPayload.Builder

java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<MxaccessGateway.AcknowledgeAlarmReplyPayload.Builder>
com.google.protobuf.GeneratedMessage.Builder<MxaccessGateway.AcknowledgeAlarmReplyPayload.Builder>
mxaccess_gateway.v1.MxaccessGateway.AcknowledgeAlarmReplyPayload.Builder
All Implemented Interfaces:
com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, Cloneable, MxaccessGateway.AcknowledgeAlarmReplyPayloadOrBuilder
Enclosing class:
MxaccessGateway.AcknowledgeAlarmReplyPayload

public static final class MxaccessGateway.AcknowledgeAlarmReplyPayload.Builder extends com.google.protobuf.GeneratedMessage.Builder<MxaccessGateway.AcknowledgeAlarmReplyPayload.Builder> implements MxaccessGateway.AcknowledgeAlarmReplyPayloadOrBuilder
 Reply payload for AcknowledgeAlarmCommand AND
 AcknowledgeAlarmByNameCommand — both ack command kinds reuse this
 payload case (`MxCommandReply.acknowledge_alarm`); there is no
 dedicated by-name reply case. Surfaces AVEVA's native ack return
 code (AlarmAckByGUID for the GUID arm, AlarmAckByName for the
 by-name arm); 0 means success. The MxCommandReply's hresult field
 carries the same value and is preferred for protocol consumers —
 this payload exists so the gateway-side WorkerAlarmRpcDispatcher
 can echo native_status into AcknowledgeAlarmReply.hresult without
 unpacking the outer envelope.
 
Protobuf type mxaccess_gateway.v1.AcknowledgeAlarmReplyPayload