Find out what data is required by the web service to get an answer

What do you want to do ?

Get a list of the data needed to reach a decision

Find out the next screen that should be displayed to reach a decision

Get a list of the data needed to reach a decision

Determinations Server

When you send an Assess request to the Determinations Server it is possible that you may not have supplied enough information for the Determinations Server to return the known values for all the outcomes you have requested.

Any attribute outcomes, that are unknown will have the <unknown-val /> element as their value.

Any inferred relationship outcomes that are unknown. Will have a state attribute, which indicates if the inferred relationship is known, unknown, or uncertain.

If an outcome is unknown, you can use a decision report to determine what data you need to provide in order for that outcome to become known.

The procedure for determining what data needs to be provided to reach a decision is a simple sequence.

  1. Make the initial request with known existing data. Make sure all outcomes will return a decision report if they are unknown. The base-attributes outcome style is the best style for getting all attributes that you need to provide.
  2. Parse the decision reports in response, noting all information that needs to be collected.
  3. Get that information, add it to the request and re-submit the request.
  4. All outcomes should become known.
Example

In this example we want to determine if the claimant is eligible for the Low income allowance.

 

Request

 

Response

 

From the response above, we can see that the attribute eligible_low_income_allowance is unknown, if we look at the decision report we can see that the reason why the outcome is unknown is because the two attributes claimant_income and claimant_public_housing_client is unknown. If we provide these attributes in the next request the outcome should become known.

 

Request with new information

 

Response with known outcome

 

Get a list of the data needed to reach a decision when a relationship is involved

When the decision may need to go through currently unknown relationships you should set the resolve-indecision-relationships to true. in the config section of the Assess operation. If this is set to true, the Determinations Server will look past the relationship to determine what other attributes or relationships might be needed. If it is not set, the Determinations Server will only tell you the relationship which is unknown

Example

In this example we want to determine if the claimant is eligible for the teenage children allowance.

 

Request

 

Response

 

From the response above, we can see that the attribute eligible_teenage_allowance is unknown, if we look at the decision report we can see that the reason why the outcome is unknown is because the relationship claimantschildren is unknown. Because we set resolve-indecision-relationships to true, the Determinations Server is also able to tell us that for all children that are targets of the relationship, we will also need to know the child’s age.

 

Request with new information

 

Response with known outcome


Find out the next screen that should be displayed to reach a decision

For information on finding out the next screen that should be displayed to reach a decision, refer to the Determine an Attribute's Value topic.