| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | recipient(+) | 0;1 | POINTER | 200 | B | |
| .02 | surrogate for alerts | 0;2 | POINTER | 200 | AC | This field may contain a pointer to the NEW PERSON file who has been designated as a SURROGATE recipient. That individual will receive alerts designated for the current user during the period of time specified by the entries in SURROGATE START DATE/TIME field [#.03] and the SURROGATE END DATE/TIME field [#.04] or, if one or both of those fields is not specified, until the SURROGATE entry is removed. If the SURROGATE END DATE/TIME field [#.04] is populated, the SURROGATE data will be removed automatically the first time an alert is sent to the current USER after the specified date and time. |
| .03 | surrogate start date/time | 0;3 | DATE-TIME | This field may contain a date and time which will specify when forwarding of alerts to the SURROGATE specified in field #.02 will begin. If there is no entry in this field, and field #.02 is populated, alerts will be sent to the surrogate immediately. | ||
| .04 | surrogate end date/time | 0;4 | DATE-TIME | This field may contain a date and time. If data is present, it indicates the time at which sending of alerts to the individual specified in the SURROGATE field (#.02) should be terminated. If no data is present, and the SURROGATE field is populated, then alerts will be sent to the SURROGATE until that entry is removed. | ||
| 1 | alert date/time | XQA;0 | MULTIPLE | 8992.01 | ||
| 2 | surrogate | 2;0 | MULTIPLE | 8992.02 | This field is a multiple based on the start date/time for a surrogate relationship. This will permit multiple surrogate relationships to be scheduled. Since a start date/time for the surrogate relationship is required, if the user does not enter one, then the NOW as the current date/time will be used. |
Not Referenced