<request type="EXPORT_TRANSLATION_TABLE" desc="Export Translation Table">
<parameters>
<parameter name="APPLICATION" value="SAMPLE1"/> (1)
<parameter name="TRANSLATION_TABLE" value="MONTH"/> (2)
</parameters>
<contents> (3)
</contents>
</request>Exporting Translation Tables
This manual is in pilot operation.
|
Overview
This function is the same as "Exporting Translation Tables" performed via fusion_place [Manager].
How to Write a Request
Below is an example request for "Exporting Translation Tables":
| 1 | "Application" parameter |
| 2 | "Translation Table" parameter |
| 3 | No request content needed |
Response Content
Below is an example response for "Exporting Translation Tables":
<response type="EXPORT_TRANSLATION_TABLE" desc="Export Translation Table">
<returned-contents> (1)
ADD-TRANSLATION-RULE,HDR,CODE_TO_TRANSLATE, TRANSLATED_CODE
ADD-TRANSLATION-RULE,DTL, 04, M1
....
</returned-contents>
<result>
<code>SUCCESSFUL</code> (2)
<started-at time-zone="Asia/Tokyo">2016/04/28 09:50:04.227</started-at>
<ended-at time-zone="Asia/Tokyo">2016/04/28 09:50:07.827</ended-at>
<messages>
</messages>
</result>
</response>| 1 | Returned Content |
| 2 | Processing Result Code |
Returned Content
The returned content is the exported translation table data. The format is the same as when exporting a translation table via fusion_place [Manager] (however, replacing special characters <, >, & is required).
For more details, refer to:
