Index
Multiple posting is a feature that allows several documents and/or folders to be posted with a single action. It is done through a file (.zip) that contains the folders and/or documents to be posted. In addition, you can use a description file. This file has information that will be used in the post and serves to reuse the same information for all documents. Such information may be:
• File name (required field);
• Description;
• Keyword;
• Additional comments;
• Author;
• Version/review description;
• Expiration date.
For information on how to create and use the description file, see Post directories in multiple post.
When the folder has approvers, only the files posted directly to the folder will be sent for approval. The sub-folders and their files are not sent for approval, following the same concept of a common publication with approvers.
Here’s a tip!
For large volumes of documents, we recommend the use of Document taxonomy, which can help organize and sort files properly. For more details, see the Document taxonomy page.
01. After clicking on the option Multiple post in the location where it will be created, click on Choose files, located to the left of the window just below the files table.
02. Find and select the file compressed in ZIP format that contains the folders or documents to be posted.
03. Click on the icon displayed next to the name of the file that was selected to display its contents.
04. In the Main column, select which files should be considered in the post.
At least one file needs to be selected as the main file.
05. In the Description file column, select the description file for the post.
The description file is used when multiple documents are being posted, and each file has specific properties. Its use is not required.
06. Define other requested information.
Post directories.
When checked, this option determines that the existing structure in the compressed file will be created in the document browsing when the multiple post is implemented.
Clear upload directory when posting
When checked, it determines that the files located in the upload directory will be deleted once the multiple post is complete.
07. Click on Next.
08. Link the information defined in the description file to the information requested when posting documents.
This step is only necessary if a description file is used. If it is not used, this window is not displayed.
09. Click on Next.
10. Enter the other information requested.
If a description file is not being used, you can define all the detailed information below, and they will be valid for all documents being posted.
If a description file is being used, you can only define the information that was not defined in this file. And this information – which will be defined in this step, since they are not in the description file – will also be valid for all documents being posted.
Comment
Brief description with relevant information that will be assigned to all documents being posted.
Tags
Labels that are assigned to all documents for easy searching later. Tags act as keywords and allow the document to be tagged in a more personal and informal manner. You can find the document by browsing or searching. Enter with or without the character “#” to enable auto complete of the tags in the tags field. The auto complete retrieves a drop-down list of the five most used tags based on the characters typed after the character "#".
Version/review description
Description of the current version/review of documents being posted.
Version/review
Number of the start version/review of documents being posted. This field is only enabled when adding documents and when the "Manual control of the start version" field of the Parameters feature under the General tab in the Control panel is checked. When the Control Panel field is not checked, the version/review "1000" is automatically assigned to the documents, and cannot be changed. This field format is numeric (999,999) and the first three numbers represent the version and the other three represent the review. After the first publication, the platform automatically controls the progress of the versions and reviews, and numbers cannot be changed.
Create compulsory version/review
When selected, it determines that it is not possible to change the documents and keep the same version/review, i.e., you can only make changes by creating a new version or review of the documents. If this field is checked when posting the document, it remains disabled when editing its properties.
Document expires?
When checked, it determines that the document will expire on the date entered in the field "Valid until". Otherwise, the documents will not expire and the date entered in the field "Valid until" is not considered. This option will be displayed as checked when the field “Document expires?"– from the Parameters feature of the General tab in the Control Panel – is checked.
Expiration notification period
Advance period – in days – from which expiration notification for the documents will be issued. If you enter zero (0), it will consider the number of days entered in the platform's general parameters.
Valid from
Date from which the documents will be available to users – according to their access permissions. This date allows the documents' author to schedule their viewing to the other users of the platform, as they will only be displayed as of that date. When the external documents are valid only as of a future date, the author views them with a red arrow representing that they are future documents. The future posting date cannot be earlier than the current date and the future post does not send notification e-mail (approval, new version/review of documents, etc.).
Valid until
The date from which the documents will be considered expired when the option "Document expires?" is checked. The expiration date is suggested considering the field "Document expiration days" – from the Parameters feature under the General tab of the Control Panel – if it has a set value. If the field "Document expires" of that feature is not checked, that date is disregarded.
Document type
Type to which the documents belong.
Subject
Subject to which the documents are related.
Icon type
Graphic element representing the documents. When this option is not selected, the documents are related to a standard icon based on the file extension.
Author
Author user of documents being posted.
Language
Language to which the documents are related. The language is used to index the content and document information. Indexed information is used in searches by content. As default, the language determined is shown in the user preferences function. If it is not defined in the user profile, the standard language defined in the General Parameters of the platform is suggested.
Notify?
When checked, this option specifies that users who have the subject related to the documents as a subject of interest will be notified when the application is posted. If the subject related to the documents is a mandatory subject, all active users will be notified, regardless of whether or not it is a subject of interest to these users.
Allows download and printing?
When checked, this option determines that the documents allow their content to be downloaded and printed by users who have permission to do so, i.e., the Download and printing option under the document's Security tab is checked for a user or a group to which the user belongs.
Update properties of a controlled copy?
When checked, this option updates information in the document properties, which is required to print the controlled copy of the documents.
Use internal viewer?
When checked, this option determines that the documents will be displayed in the platform's internal viewer. In multiple posting, this option only applies to PDF files or images that do not require conversion.
11. Click on Next.
12. Define the criteria for the documents being posted.
For more information about the procedure, see Define security criteria for folder or document.
13. Click on Save.
Please note!
This documentation is valid as of the 1.6.5 update (Liquid). If you use a previous update, it may contain information different from what you see on your platform.
