« Exporting Data Using Forms   |   Compress Series of Editions »

Publish Workspace Edition Data

This manual is in pilot operation.

Overview

This function is almost equivalent to "Publish Workspace Edition Data" performed via fusion_place [Manager].footnote:[Unlike the Manager operation, this request does not automatically perform "Compressing Edition Series" or "Compressing Ledger Line Data by Generation" after publication. Only users with Designer or Administrator privileges can execute this request.

How to Write a Request

Below is an example request for "Publish Workspace Edition Data":

<request type="PUBLISH_EDITION" desc="Publish Workspace Edition Data">
  <parameters>
    <parameter name="APPLICATION" value="SAMPLE1"/> (1)
    <parameter name="SOURCE_EDITION" value="EDITION1"/> (2)
    <parameter name="SCENARIOS" value="BUDGET,FCST"/> (3)
  </parameters>
  <contents> (4)
  </contents>
</request>
1 "Application" parameter
2 "Source Ledger Edition" parameter
3 "Target Scenarios" parameter
4 Request Content

Parameters

In addition to the target application, you can specify the source ledger edition and one or more target scenarios.

Parameter Required Key Description

APPLICATION

Yes

None

Specify the label of the target application.

SOURCE_EDITION

No

None

Specify the key of the source ledger edition for publication. If omitted, the "workspace edition" will be used as the source.
Specifying a public edition key will result in an error.

SCENARIOS

No

None

Specify the labels of target scenarios, separated by commas ",". If left empty or omitted, all scenarios will be targeted for publication.

Request Content

There is no "Request Content."

Response Content

Below is an example response for "Publish Workspace Edition Data":

<response type="PUBLISH_EDITION" desc="Publish Workspace Edition Data">
  <returned-contents> (1)
  </returned-contents>
  <result>
    <code>SUCCESSFUL</code> (2)
    <started-at time-zone="Asia/Tokyo">2015/02/28 09:50:04.227</started-at>
    <ended-at time-zone="Asia/Tokyo">2015/02/28 09:50:07.827</ended-at>
    <messages>
      ... (3)
    </messages>
  </result>
</response>
1 Returned Content
2 Processing Result Code
3 Message

Returned Content

There is no returned content.

Message

If the processing result code is "SUCCESSFUL," nothing is displayed in the message field.

If the processing result code is "FAILED," the message field displays the reason for the failure.

No other processing result codes are used.