Compress Series of Editions

This manual is in pilot operation.

Overview

Immediately after publishing workspace edition data via [Web-API], the old public edition is still retained (invisible to the user), and the new public edition holds differential data from the old one. When this compress series of editions process is executed, the data of the old public edition is merged into the new one, and the old public edition itself is deleted. This helps reduce memory usage.

Only users with Designer or Administrator privileges can execute this request.

Note: When "Publish Workspace Edition Data" is executed via fusion_place [Manager], the system also performs the compress series of editions automatically after "publication."

How to Write a Request

Below is an example request for "Compress Series of Editions":

<request type="COMPRESS_EDITIONS" desc="Compress Series of Editions">
  <parameters>
    <parameter name="APPLICATION" value="SAMPLE1"/> (1)
  </parameters>
  <contents> (2)
  </contents>
</request>
1 "Application" parameter
2 Request Content

Parameters

Only the target application needs to be specified.

Parameter Required Key Description

APPLICATION

Yes

None

Specify the label of the target application.

Request Content

There is no "Request Content."

Response Content

Below is an example response for "Compress Series of Editions":

<response type="COMPRESS_EDITIONS" desc="Compress Series of Editions">
  <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 result codes are used.

Notes

This process does not include "Sweeping Garbage." If data cleanup is required, run the sweeping garbage process separately after this.