<request type="IMPORT_PARTICIPANT_AUTHS" desc="Importing Participant Authorities">
<parameters>
<parameter name="APPLICATION" value="SAMPLE1"/> (1)
</parameters>
<contents>
ADD_OR_UPDATE_PARTICIPANT_AUTH, HDR, PARTICIPANT, USER_ACCOUNT .... (2)
ADD_OR_UPDATE_PARTICIPANT_AUTH, DTL, AD_P, Taro. Yamada,....
ADD_OR_UPDATE_PARTICIPANT_AUTH, DTL, AD_A, Taro. Yamada, ....
....
</contents>
</request>Importing Participant Authorities
This manual is in pilot operation.
|
Overview
This function is the same as "Importing Participant Authorities" performed via fusion_place [Manager]. In other words, participant authorities can be added, updated, or deleted in bulk.
How to Write a Request
Below is an example request for "Importing Participant Authorities":
| 1 | "Application" parameter |
| 2 | Request content |
Parameters
Specify the target application.
| Parameter | Required | Key | Description |
|---|---|---|---|
APPLICATION |
Yes |
None |
Specify the label of the target application. |
Request Content
The request content is the data to be imported. The format is the same as when importing participant authorities via fusion_place [Manager] (however, replacing special characters <, >, & is required).
For more details, refer to:
Response Content
Below is an example response for "Importing Participant Authorities":
<response type="IMPORT_PARTICIPANT_AUTHS" desc="Importing Participant Authorities">
<returned-contents> (1)
</returned-contents>
<result>
<code>ERROR</code> (2)
<started-at time-zone="Asia/Tokyo">2015/07/28 09:50:04.227</started-at>
<ended-at time-zone="Asia/Tokyo">2015/07/28 09:50:07.828</ended-at>
<messages>
User account name specified in the user account field "USER_ACCOUNT"... (3)
...
</messages>
</result>
</response>| 1 | Returned Content |
| 2 | Processing Result Code |
| 3 | Message |
