The ATL COM module tarmedValidator provides methods to
browse, search & validate records of the Tarmed tariff
browse, search & validate records of the Tarmed tariff
API browser of tarmedValidator100 COM module
ITarmedValidator::EnableLog property | |||
---|---|---|---|
Get and Set the log activity for the module. The default log activity is enYes. | |||
Restful webservice calling syntax | |||
[GET] | /baseURL/ITarmedValidator/GetEnableLog?param | ||
[param] | pITarmedValidator= | longValue |
|
[JSON result data] | peEnableLog: | longValue |
|
[PUT] | /baseURL/ITarmedValidator/PutEnableLog | ||
[JSON input data] | pITarmedValidator: eEnableLog: |
longValue, //interface address longValue |
|
[HTTP result status] | 200 | Return status 200 signals a successful method call | |
204 | Return status 204 (noContent) signals that the end of an iteration is reached | ||
>= 400 | Return status >= 400 signals an unsuccessful function call. The returned JSON{errorCode: code, errorText:"text"} supplies the error message the same as GetAbortInfo() would do. | ||
C/C++ calling syntax | |||
[get] HRESULT | EnableLog( YesNoType *peEnableLog ); | ||
[put] HRESULT | EnableLog( YesNoType eEnableLog ); | ||
[C/C++ return value] | S_OK | This value is returned if the function call was successful. | |
S_FALSE | This value is returned if the end of an iteration is reached | ||
E_name | This value is returned if the function call was unsuccessful and an error exception was generated. Note that if you are using SmartPointers an exception is thrown under these conditions. | ||
Calling argument description | |||
[out,retval] YesNoType | *peEnableLog | Boolean that defines if the logging is enabled (enYes) or not (enNo) | |
[in] YesNoType | eEnableLog | Boolean that defines if the logging is enabled (enYes) or not (enNo) | |
Remarks | |||
If SmartPointers are used than the function names and calls are rewritten by Microsoft into the form | |||