/AWS1/IF_PPT=>LISTTEMPLATEVERSIONS()

About ListTemplateVersions

Retrieves information about all the versions of a specific message template.

Method Signature

METHODS /AWS1/IF_PPT~LISTTEMPLATEVERSIONS
  IMPORTING
    !IV_NEXTTOKEN TYPE /AWS1/PPT__STRING OPTIONAL
    !IV_PAGESIZE TYPE /AWS1/PPT__STRING OPTIONAL
    !IV_TEMPLATENAME TYPE /AWS1/PPT__STRING OPTIONAL
    !IV_TEMPLATETYPE TYPE /AWS1/PPT__STRING OPTIONAL
  RETURNING
    VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_pptlisttmplvrssrsp
  RAISING
    /AWS1/CX_PPTBADREQUESTEX
    /AWS1/CX_PPTFORBIDDENEXCEPTION
    /AWS1/CX_PPTINTERNALSERVERER00
    /AWS1/CX_PPTMETHODNOTALLOWEDEX
    /AWS1/CX_PPTNOTFOUNDEXCEPTION
    /AWS1/CX_PPTPAYLOADTOOLARGEEX
    /AWS1/CX_PPTTOOMANYREQUESTSEX
    /AWS1/CX_PPTCLIENTEXC
    /AWS1/CX_PPTSERVEREXC
    /AWS1/CX_RT_TECHNICAL_GENERIC
    /AWS1/CX_RT_SERVICE_GENERIC.

IMPORTING

Required arguments:

iv_templatename TYPE /AWS1/PPT__STRING /AWS1/PPT__STRING

The name of the message template. A template name must start with an alphanumeric character and can contain a maximum of 128 characters. The characters can be alphanumeric characters, underscores (_), or hyphens (-). Template names are case sensitive.

iv_templatetype TYPE /AWS1/PPT__STRING /AWS1/PPT__STRING

The type of channel that the message template is designed for. Valid values are: EMAIL, PUSH, SMS, and VOICE.

Optional arguments:

iv_nexttoken TYPE /AWS1/PPT__STRING /AWS1/PPT__STRING

The string that specifies which page of results to return in a paginated response. This parameter is not supported for application, campaign, and journey metrics.

iv_pagesize TYPE /AWS1/PPT__STRING /AWS1/PPT__STRING

The maximum number of items to include in each page of a paginated response. This parameter is not supported for application, campaign, and journey metrics.

RETURNING

oo_output TYPE REF TO /aws1/cl_pptlisttmplvrssrsp /AWS1/CL_PPTLISTTMPLVRSSRSP

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->listtemplateversions(
  iv_nexttoken = |string|
  iv_pagesize = |string|
  iv_templatename = |string|
  iv_templatetype = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
  lo_templateversionsrespons = lo_result->get_templateversionsresponse( ).
  IF lo_templateversionsrespons IS NOT INITIAL.
    LOOP AT lo_templateversionsrespons->get_item( ) into lo_row.
      lo_row_1 = lo_row.
      IF lo_row_1 IS NOT INITIAL.
        lv___string = lo_row_1->get_creationdate( ).
        lv___string = lo_row_1->get_defaultsubstitutions( ).
        lv___string = lo_row_1->get_lastmodifieddate( ).
        lv___string = lo_row_1->get_templatedescription( ).
        lv___string = lo_row_1->get_templatename( ).
        lv___string = lo_row_1->get_templatetype( ).
        lv___string = lo_row_1->get_version( ).
      ENDIF.
    ENDLOOP.
    lv___string = lo_templateversionsrespons->get_message( ).
    lv___string = lo_templateversionsrespons->get_nexttoken( ).
    lv___string = lo_templateversionsrespons->get_requestid( ).
  ENDIF.
ENDIF.