This service returns a list of all the screens available from a rulebase. this includes automatically generated screens as well as those build by the Rulebase engineer.
The List Screens request and response is the identical for Generic and Specific calls.
The Call is a simple SOAP Request with no parameters:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:typ="http:// oracle.com/determinations/server/9.3/rulebase/types">
<soapenv:Header/>
<soapenv:Body>
<typ:list-screens-request/>
</soapenv:Body>
</soapenv:Envelope>
The response contains a list of screens available in the rulebase.
The response is a complex XML type structured as:
"list-screens-response"
The response element.
"screen-summary” (recurring element)
For every screen available in the Rulebase a screen summary element will be returned. It has the following attributes:
"id" – the identifier for the screen
"name" (optional) – the name of the screen (not all screens have a name)
"title"- the title of the screen
"entity” – the entity the screen is associated with "is-automatic"- a Boolean value indicating if the screen is automatically generated, (true) or defined in the rulebase (false).
Example Response:
In the below example there are three screens all built in the rulebase (is-automatic= false for all), and their titles are "Applicant Details, "Applicant Summary" and "Applicant Address".
<SOAP-ENV:Envelope
xlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:typ="http://oracle.com/determinations/server/9.3/cwg/types">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<typ:list-screens-response>
<typ:screen-summary entity="applicant" id="s42@Screens"
is-automatic="false" title="Applicant Details"/>
<typ:screen-summary entity="applicant" id="s26@Screens"
is-automatic="false" title="Applicant Summary"/>
<typ:screen-summary entity="applicant" id="s13@Screens"
is-automatic="false" title="Applicant Address"/>
</typ:list-screens-response>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>