System administrators can create user-defined screens that utilize the underlying web services on which the system is architected.
The Web Service Prompt Engine displays the screen representing the prompt definition. The Web Service Prompt Engine also processes data entered for the prompt transactions through the underlying web services.
Because the Web Service Prompt Engine uses web services, the data is processed directly to the underlying tables as the transactions are submitted. Therefore, you receive immediate feedback if the transaction is successful as well as if it contains validation or web service errors. These errors can then be corrected in 'real time' and re-submitted.
Once a web service prompt has been created, the system administrator must place the corresponding screen into the user groups menu structure. That process makes the new screen available through the menu structure, and the new screen appears like all other screens within the system. The screen name is equivalent to the prompt description. You need only query permissions for the new screen.
User defined fields are available for web service prompts. The fields display in a list of all fields under the appropriate web service. These user defined fields inherit properties from the associated reference form. Right-click in Screen Designer mode to define options for user defined fields.
The following apply to screens based on web service prompts:
Screens |
Behavior/Expectations |
---|---|
The lookup defined on the selected screen for a chosen field |
Is not automatically displayed |
They are standalone record view screens |
With no tabs and no Dataspy filtering features |
Dataspy, Export to Excel, Quick Filter, and Save Layout |
Options are not available |
Common tabs and pop-ups |
(Comments, Documents, Addresses, etc.) are not available |
Available toolbar options |
Previous Screen, Save, Reset Screen, and Help |
Right-click options |
Not available |
The system administrator must associate a Query Code or define a Retrieved Value for each lookup field unless the field is a user defined field with lookup definitions defined on the inherited screen.