When you create an ePortal server message for an OS 2200 TIP Data Source, the server message may contain one or more special metadata fields. These metadata fields are in addition to the regular fields which carry user data. Your ePortal application can access the metadata fields like any other field in an ePortal message; that is, you can access the metadata field in your Understanding Orchestration or using the code in your Getting Ready to Build a New Presentation Project. However, the metadata field will not appear in the data record accessed by your OS 2200 TIP application.
Below are descriptions of the metadata fields which may be found in an ePortal server message in an OS 2200 TIP Data Source:
tiptrancode__ - This is a string representing the transaction code used to invoke a TIP application, as configured in the VALTAB. This metadata field exists if and only if the direction of the server message is Input or Input/Output. That is, this field exists only for records which may be sent to the OS 2200 server. If you leave this value blank, the default TIP transaction code is used.
The following metadata fields are included in a server message generated for a DPS form if and only if the direction of the server message is Input/Output. These fields are automatically set by ePortal when an error is returned by a DPS application.
dpserrortext__ - This is a string that contains the error text returned by a DPS error handling function.
dpserrory__ - This is an integer that contains the Y-coordinate of the field in error. This field defaults to -1 if a coordinate is not available.
dpserrorx__ - This is an integer that contains the X-coordinate of the field in error. This field defaults to -1 if a coordinate is not available.
dpserrorhandling__ - This is a flag used to determine if automatic handling of errors returned by DPS error handling function should be performed by ePortal. The default is True.
Refer to the following topics for more information on configuring the TIP transaction code: