/AWS1/IF_WML=>LISTMOBILEDEVACCESSOVERRIDES()¶
About ListMobileDeviceAccessOverrides¶
Lists all the mobile device access overrides for any given combination of WorkMail organization, user, or device.
Method Signature¶
METHODS /AWS1/IF_WML~LISTMOBILEDEVACCESSOVERRIDES
IMPORTING
!IV_ORGANIZATIONID TYPE /AWS1/WMLORGANIZATIONID OPTIONAL
!IV_USERID TYPE /AWS1/WMLENTITYIDENTIFIER OPTIONAL
!IV_DEVICEID TYPE /AWS1/WMLDEVICEID OPTIONAL
!IV_NEXTTOKEN TYPE /AWS1/WMLNEXTTOKEN OPTIONAL
!IV_MAXRESULTS TYPE /AWS1/WMLMAXRESULTS OPTIONAL
RETURNING
VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_wmllstmobiledevacco01
RAISING
/AWS1/CX_WMLENTITYNOTFOUNDEX
/AWS1/CX_WMLINVALIDPARAMETEREX
/AWS1/CX_WMLORGNOTFOUNDEX
/AWS1/CX_WMLORGSTATEEXCEPTION
/AWS1/CX_WMLCLIENTEXC
/AWS1/CX_WMLSERVEREXC
/AWS1/CX_RT_TECHNICAL_GENERIC
/AWS1/CX_RT_SERVICE_GENERIC.
IMPORTING¶
Required arguments:¶
iv_organizationid TYPE /AWS1/WMLORGANIZATIONID /AWS1/WMLORGANIZATIONID¶
The WorkMail organization under which to list mobile device access overrides.
Optional arguments:¶
iv_userid TYPE /AWS1/WMLENTITYIDENTIFIER /AWS1/WMLENTITYIDENTIFIER¶
The WorkMail user under which you list the mobile device access overrides. Accepts the following types of user identities:
User ID:
12345678-1234-1234-1234-123456789012orS-1-1-12-1234567890-123456789-123456789-1234Email address:
user@domain.tldUser name:
user
iv_deviceid TYPE /AWS1/WMLDEVICEID /AWS1/WMLDEVICEID¶
The mobile device to which the access override applies.
iv_nexttoken TYPE /AWS1/WMLNEXTTOKEN /AWS1/WMLNEXTTOKEN¶
The token to use to retrieve the next page of results. The first call does not require a token.
iv_maxresults TYPE /AWS1/WMLMAXRESULTS /AWS1/WMLMAXRESULTS¶
The maximum number of results to return in a single call.
RETURNING¶
oo_output TYPE REF TO /aws1/cl_wmllstmobiledevacco01 /AWS1/CL_WMLLSTMOBILEDEVACCO01¶
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->listmobiledevaccessoverrides(
iv_deviceid = |string|
iv_maxresults = 123
iv_nexttoken = |string|
iv_organizationid = |string|
iv_userid = |string|
).
This is an example of reading all possible response values
lo_result = lo_result.
IF lo_result IS NOT INITIAL.
LOOP AT lo_result->get_overrides( ) into lo_row.
lo_row_1 = lo_row.
IF lo_row_1 IS NOT INITIAL.
lv_workmailidentifier = lo_row_1->get_userid( ).
lv_deviceid = lo_row_1->get_deviceid( ).
lv_mobiledeviceaccessrulee = lo_row_1->get_effect( ).
lv_mobiledeviceaccessruled = lo_row_1->get_description( ).
lv_timestamp = lo_row_1->get_datecreated( ).
lv_timestamp = lo_row_1->get_datemodified( ).
ENDIF.
ENDLOOP.
lv_nexttoken = lo_result->get_nexttoken( ).
ENDIF.