CHANNELFLOWCALLBACK()`¶

About ChannelFlowCallback¶

Calls back Amazon Chime SDK messaging with a processing response message. This should be invoked from the processor Lambda. This is a developer API.

You can return one of the following processing responses:

Update message content or metadata
Deny a message
Make no changes to the message

Method Signature¶

METHODS /AWS1/IF_CHS~CHANNELFLOWCALLBACK
  IMPORTING
    !IV_CALLBACKID TYPE /AWS1/CHSCALLBACKIDTYPE OPTIONAL
    !IV_CHANNELARN TYPE /AWS1/CHSCHIMEARN OPTIONAL
    !IV_DELETERESOURCE TYPE /AWS1/CHSNONNULLABLEBOOLEAN OPTIONAL
    !IO_CHANNELMESSAGE TYPE REF TO /AWS1/CL_CHSCHANNELMSGCALLBACK OPTIONAL
  RETURNING
    VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_chschannelflowcallb01
  RAISING
    /AWS1/CX_CHSBADREQUESTEX
    /AWS1/CX_CHSCONFLICTEXCEPTION
    /AWS1/CX_CHSFORBIDDENEXCEPTION
    /AWS1/CX_CHSSERVICEFAILUREEX
    /AWS1/CX_CHSSERVICEUNAVAILEX
    /AWS1/CX_CHSTHROTTLEDCLIENTEX
    /AWS1/CX_CHSUNAUTHDCLIENTEX
    /AWS1/CX_CHSCLIENTEXC
    /AWS1/CX_CHSSERVEREXC
    /AWS1/CX_RT_TECHNICAL_GENERIC
    /AWS1/CX_RT_SERVICE_GENERIC.

IMPORTING¶

Required arguments:¶

`iv_callbackid` `TYPE /AWS1/CHSCALLBACKIDTYPE` `/AWS1/CHSCALLBACKIDTYPE`¶

The identifier passed to the processor by the service when invoked. Use the identifier to call back the service.

`iv_channelarn` `TYPE /AWS1/CHSCHIMEARN` `/AWS1/CHSCHIMEARN`¶

The ARN of the channel.

`io_channelmessage` `TYPE REF TO /AWS1/CL_CHSCHANNELMSGCALLBACK` `/AWS1/CL_CHSCHANNELMSGCALLBACK`¶

Stores information about the processed message.

Optional arguments:¶

`iv_deleteresource` `TYPE /AWS1/CHSNONNULLABLEBOOLEAN` `/AWS1/CHSNONNULLABLEBOOLEAN`¶

When a processor determines that a message needs to be DENIED, pass this parameter with a value of true.

RETURNING¶

`oo_output` `TYPE REF TO /aws1/cl_chschannelflowcallb01` `/AWS1/CL_CHSCHANNELFLOWCALLB01`¶

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->channelflowcallback(
  io_channelmessage = new /aws1/cl_chschannelmsgcallback(
    io_pushnotification = new /aws1/cl_chspushnotifconf(
      iv_body = |string|
      iv_title = |string|
      iv_type = |string|
    )
    it_messageattributes = VALUE /aws1/cl_chsmessageattrvalue=>tt_messageattributemap(
      (
        VALUE /aws1/cl_chsmessageattrvalue=>ts_messageattributemap_maprow(
          key = |string|
          value = new /aws1/cl_chsmessageattrvalue(
            it_stringvalues = VALUE /aws1/cl_chsmsgattrstrvalues_w=>tt_messageattrstringvalues(
              ( new /aws1/cl_chsmsgattrstrvalues_w( |string| ) )
            )
          )
        )
      )
    )
    iv_content = |string|
    iv_contenttype = |string|
    iv_messageid = |string|
    iv_metadata = |string|
    iv_subchannelid = |string|
  )
  iv_callbackid = |string|
  iv_channelarn = |string|
  iv_deleteresource = ABAP_TRUE
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
  lv_chimearn = lo_result->get_channelarn( ).
  lv_callbackidtype = lo_result->get_callbackid( ).
ENDIF.

/AWS1/IF_CHS=>CHANNELFLOWCALLBACK()¶