SUBMITFEEDBACK()`¶

About SubmitFeedback¶

Sends feedback to CodeGuru Profiler about whether the anomaly detected by the analysis is useful or not.

Method Signature¶

IMPORTING¶

Required arguments:¶

`iv_profilinggroupname` `TYPE /AWS1/GUPPROFILINGGROUPNAME` `/AWS1/GUPPROFILINGGROUPNAME`¶

The name of the profiling group that is associated with the analysis data.

`iv_anomalyinstanceid` `TYPE /AWS1/GUPANOMALYINSTANCEID` `/AWS1/GUPANOMALYINSTANCEID`¶

The universally unique identifier (UUID) of the AnomalyInstance object that is included in the analysis data.

`iv_type` `TYPE /AWS1/GUPFEEDBACKTYPE` `/AWS1/GUPFEEDBACKTYPE`¶

The feedback tpye. Thee are two valid values, Positive and Negative.

Optional arguments:¶

`iv_comment` `TYPE /AWS1/GUPSTRING` `/AWS1/GUPSTRING`¶

Optional feedback about this anomaly.

RETURNING¶

`oo_output` `TYPE REF TO /aws1/cl_gupsubmitfeedbackrsp` `/AWS1/CL_GUPSUBMITFEEDBACKRSP`¶

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_gup~submitfeedback(
  iv_anomalyinstanceid = |string|
  iv_comment = |string|
  iv_profilinggroupname = |string|
  iv_type = |string|
).

This is an example of reading all possible response values

/AWS1/CL_GUP=>SUBMITFEEDBACK()¶