EVALUATEFEATURE()`¶

About EvaluateFeature¶

This operation assigns a feature variation to one given user session. You pass in an entityID that represents the user. Evidently then checks the evaluation rules and assigns the variation.

The first rules that are evaluated are the override rules. If the user's entityID matches an override rule, the user is served the variation specified by that rule.

If there is a current launch with this feature that uses segment overrides, and if the user session's evaluationContext matches a segment rule defined in a segment override, the configuration in the segment overrides is used. For more information about segments, see CreateSegment and Use segments to focus your audience.

If there is a launch with no segment overrides, the user might be assigned to a variation in the launch. The chance of this depends on the percentage of users that are allocated to that launch. If the user is enrolled in the launch, the variation they are served depends on the allocation of the various feature variations used for the launch.

If the user is not assigned to a launch, and there is an ongoing experiment for this feature, the user might be assigned to a variation in the experiment. The chance of this depends on the percentage of users that are allocated to that experiment.

If the experiment uses a segment, then only user sessions with evaluationContext values that match the segment rule are used in the experiment.

If the user is enrolled in the experiment, the variation they are served depends on the allocation of the various feature variations used for the experiment.

If the user is not assigned to a launch or experiment, they are served the default variation.

Method Signature¶

IMPORTING¶

Required arguments:¶

`iv_project` `TYPE /AWS1/EVYPROJECTREF` `/AWS1/EVYPROJECTREF`¶

The name or ARN of the project that contains this feature.

`iv_feature` `TYPE /AWS1/EVYFEATURENAME` `/AWS1/EVYFEATURENAME`¶

The name of the feature being evaluated.

`iv_entityid` `TYPE /AWS1/EVYENTITYID` `/AWS1/EVYENTITYID`¶

An internal ID that represents a unique user of the application. This entityID is checked against any override rules assigned for this feature.

Optional arguments:¶

`iv_evaluationcontext` `TYPE /AWS1/EVYJSONVALUE` `/AWS1/EVYJSONVALUE`¶

A JSON object of attributes that you can optionally pass in as part of the evaluation event sent to Evidently from the user session. Evidently can use this value to match user sessions with defined audience segments. For more information, see Use segments to focus your audience.

If you include this parameter, the value must be a JSON object. A JSON array is not supported.

RETURNING¶

`oo_output` `TYPE REF TO /aws1/cl_evyevaluatefeaturersp` `/AWS1/CL_EVYEVALUATEFEATURERSP`¶

Domain /AWS1/RT_ACCOUNT_ID

Primitive Type NUMC

Examples¶

Syntax Example¶

This is an example of the syntax for calling the method. It includes every possible argument and initializes every possible value. The data provided is not necessarily semantically accurate (for example the value "string" may be provided for something that is intended to be an instance ID, or in some cases two arguments may be mutually exclusive). The syntax shows the ABAP syntax for creating the various data structures.

DATA(lo_result) = lo_client->/aws1/if_evy~evaluatefeature(
  iv_entityid = |string|
  iv_evaluationcontext = |string|
  iv_feature = |string|
  iv_project = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
  lv_string = lo_result->get_variation( ).
  lo_variablevalue = lo_result->get_value( ).
  IF lo_variablevalue IS NOT INITIAL.
    lv_boolean = lo_variablevalue->get_boolvalue( ).
    lv_string = lo_variablevalue->get_stringvalue( ).
    lv_long = lo_variablevalue->get_longvalue( ).
    lv_double = lo_variablevalue->get_doublevalue( ).
  ENDIF.
  lv_string = lo_result->get_reason( ).
  lv_jsonvalue = lo_result->get_details( ).
ENDIF.

/AWS1/CL_EVY=>EVALUATEFEATURE()¶