HP 3000 Manuals HP 3000 Manuals
Routed Messages HP DeskManagerPLUS includes the Routing and Authorization feature, which allows messages to be routed to a specified Distribution List (or Route List) of users for their approval or rejection. The use of this feature is described in HP DeskManager User Reference Guide.
NOTE It is not possible to create or action routed messages programmatically with the Intrinsics.
The HP Desk Intrinsics avoid blockages on approvals of routed messages which would otherwise result from the use of the HPDUserReceive or HPDGateReceive Intrinsics. If a routed message is received by the Intrinsics on behalf ofa user, HP Desk will automatically generate a normal message to the user, and route the message to the next signatory in the Route List with an indication of what has happened. The Intrinsics application may need to recognize a status return that indicates that a routed message has been automatically forwarded on. This behavior can be modified by the use of sp_dont_route_msgs Session Profile option (see Chapter 8 ), which will signify to the application that it should pass on routed messages. Some minor extensions to the Intrinsics transactions are also required to identify routed messages. The programmatic interface has the following limitations: * It is not possible to originate a routed message via the Intrinsics. * It is not possible for a message to be approved or rejected by an Intrinsics application. * It is possible to receive an approved message (that is, at the final destination) and determine that it was approved and who the signatories were, so allowing the message to be processed automatically by the application