<request type="EXPORT_PARTICIPANT_AUTHS" desc="Exporting Participant Authorities">
<parameters>
<parameter name="APPLICATION" value="SAMPLE1"/> (1)
</parameters>
<contents> (2)
</contents>
</request>
Exporting Participant Authorities
This manual is in pilot operation.
|
Overview
This function is the same as "Exporting Participant Authorities" performed via fusion_place [Manager].
How to Write a Request
Below is an example request for "Exporting Participant Authorities":
| 1 | "Application" parameter |
| 2 | No request content needed |
Response Content
Below is an example response for "Exporting Participant Authorities":
<response type="EXPORT_PARTICIPANT_AUTHS" desc="Exporting Participant Authorities">
<returned-contents> (1)
ADD_OR_UPDATE_PARTICIPANT_AUTH,HDR,PARTICIPANT,USER_ACCOUNT,IN_CHARGE,TO_BE_NOTIFIED
ADD_OR_UPDATE_PARTICIPANT_AUTH,DTL,"A","User1",false,false
....
</returned-contents>
<result>
<code>SUCCESSFUL</code> (2)
<started-at time-zone="Asia/Tokyo">2018/01/23 09:50:04.227</started-at>
<ended-at time-zone="Asia/Tokyo">2018/01/23 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 participant authority data. The format is the same as when exporting participant authorities via fusion_place [Manager] (however, replacing special characters <, >, & is required).
For more details, refer to: