The document data source that can be configured within the project allows the upload, storage and management of the files required to submit a successful ESEF filing and makes converted PDF reports available for iXBRL tagging in the Tagging tool.
Management of all documents associated with the project is performed in the Documents tab, located between the Forms and Permissions tabs in the Project configuration.
The Documents tab contains the Documents grid that lists all of the documents (i.e. data sources) added to the project and their properties:
Note: The title of the document (i.e. the document Name) has to be unique within the project
The entries in the Documents grid are sortable; by default, the entries are sorted by the Name column in a lexicographically descending order. All changes made to the document's configuration are applied on saving the entire project configuration.
By default:
By default (i.e. when creating a new project), a document titled Document 1 will be automatically created for the user, once at least one fact collection, client and period are configured for the project.
Additional documents can be created:
Copying a document does not copy its contents, only its configuration. In other words, references (i.e. links or paths) to the external data sources (i.e. HTML\XHTML files) configured for the source document will not be copied over to the newly created document |
An existing document can be removed by selecting its entry in the grid and clicking Remove. Removing a document results in:
All documents configured in the project are accessible:
In order to access a document, the project where the document resides needs to be open first; otherwise, the ribbon section will not be visible\the menu items will be disabled.
In order for the document to be accessible and usable in the Tagging tool, the physical PDF report as well as any accompanying attachments needs to be imported into the document. This can be done by clicking the Import button in the Documents ribbon section\Documents menu
In order to ensure the successful import and tagging of PDF reports:
|
This option allows to import a PDF report into the document selected in the Target document dropdown menu while converting the PDF into an ESEF compliant XHTML file that can be tagged using iXBRL in the Tagging tool editor in the process.
Selecting Unicode mapping will force the tool to map the PDFs internal encoding to Unicode thus possibly affecting the documents layout and look and feel.
Providing a supported external tag properties file in the Tag definition input will automatically tag the imported report based on the external file's contents as discussed in more details here.
This option allows to quickly import an entire reporting package generated by the Tagging tool. Importing the package will automatically create a new project, configured with the reporting taxonomy and the taxonomy extension and a pre-configured document containing the tagged HTML\XHTML report (and any referenced image, stylesheet or script files)
This option allows to import all of the ESEF supported file types to be used as an attachment to the generated filing package. Supported file types are:
This option allows to convert a PDF file into a ESEF compliant XHTML file that can be added to the ESEF filing package
Any XHTML file (i.e. XHTML file created as the result of the PDF conversion and is used to create an iXBRL instance via tagging as well as any other non-tagged XHTML file submitted in the filing) has to pass the XHTML 1.1 schema validation to be ESEF compliant; submitting XHTML files that do not pass the XHTML 1.1 schema validation may result in a submission rejection |
Once the external data sources have been imported into a document, that document can be opened for editing in the Tagging tool by clicking the Edit button in the Documents ribbon section\Documents menu and selecting its name, and clicking Open in the Edit documents dialog that will appear.
Concurrent document access is supported – a document that's currently open for editing can be opened by another user independently and they will be notified that the document is currently being edited.
In case the edits result in conflicting changes, the changes made by the user that saves the document last will be the ones that will be persisted.
Access to documents is controlled via the following permissions located in the project configuration Permissions tab:
All actions that affect the currently configured documents in the project are tracked in the Document history that can be accessed by clicking View history in the Documents ribbon section\Documents menu. The Document history dialog lists the following details on the tracked actions:
In addition to the existing functionalities, exporting/importing the project also exports/imports: