The following sections detail the process of sending an external automatic entry.
Message is Assembled
The Send built-in persistent class method packages the attributes of the external class and sends them to the destination application.
An external automatic entry requires that both applications recognize all the attributes being used in the message. Therefore, the following must apply:
In the originating application, the direction of the attributes must be defined as input-output in order to be valid in both the auto entry buffer and the video buffer.
In the destination application, the attributes can have their direction defined as either input or input-output in order to be valid.
Message is Sent
The Send built-in persistent class method transfers the message in the auto entry buffer, as required, to:
The HUB server of applications on the same host.
Applications on other hosts, for non-Agile Business Suite applications using the HUB Listener service/HUB Socket protocol adapter.
Message is Processed
In the destination application, the message is processed as if it were normal screen input. A value for the built-in attribute Maint may need to be supplied.
Note: External automatic entries use the same value of Glb.Priv as the originating user account.
All logic is processed, except for construct logic.
Note: This is different from internal automatic entries, where the logic of the receiving ispec is not performed.
Within the destination ispec, a recall (using the Recall command) of a different ispec is ignored. A recall of the same ispec causes a reply to be returned to the originating application. If Glb.Error is set to “*****”, an error is returned when processing is complete.
The destination ispec may initiate automatic entry transactions to other ispecs. Any resulting chain of automatic entry transactions must not be cyclical. Refer to Security Issues with External Automatic Entries for more information about Series of Automatic Entries. |
CautionReplies are Received
The response is received in the auto entry buffer of the originating application. Information regarding the result of the external automatic entry is contained in Glb.Status and Glb.Hubstatus.