FluidTopicsDitaControlFile.xml Control File - Fluid Topics - 3.3

Upload DITA Content to Fluid Topics

Product
Fluid Topics
FT_Version
3.3
Category
Technical Notes

When uploading an archive containing DITA content to Fluid Topics, an additional file can be added to the archive in two cases:

Note: From Fluid Topics v3.4.55, the FluidTopicsControlFile.xml control file replaces the FluidTopicsDitaControlFile.xml.

The file must be named FluidTopicsDitaControlFile.xml.

The following lines show the template of a FluidTopicsDitaControlFile.xml file:

<?xml version="1.0" encoding="UTF-8"?>
<ft:resources xmlns:ft="http://ref.fluidtopics.com/v2/ft-dita#" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:noNamespaceSchemaLocation>
  <ft:resource status="deleted">
    <ft:ditamapFile>${path of the ditamap to be removed within the archive.ditamap}</ft:ditamapFile>
    <ft:ditavalFile>${path of the ditaval to be removed within the archive.ditaval}</ft:ditavalFile>
  </ft:resource>
  <ft:resource status="visible">
    <ft:ditamapFile>${path of the ditamap to be updated within the archive.ditamap}</ft:ditamapFile>
    <ft:ditavalFile>${path of the ditaval to be updated within the archive.ditaval}</ft:ditavalFile>
    <ft:restrictions>
        <ft:groups>
            <ft:group>${ditamap access rights value1}</ft:group>
            <ft:group>${ditamap access rights value2}</ft:group>
        </ft:groups>
    </ft:restrictions>
  </ft:resource>
</ft:resources>

The ft:resource elements are only used to define the generated map the action will be performed on:

  • If the status attribute is set to "deleted", the ft:ditamapFile and ft:ditavalFile elements define the generated map that should be removed.
  • If the status attribute is set to "visible", the ft:ditamapFile and ft:ditavalFile elements define the generated map the access rights should be applied to.