Fill in this field with the directory containing the electronic files of the documents that will be created.
Use a semicolon ( ; ) as separator if the document has more than one electronic file.

If the file type is set to Complex, fill in the field in this format:

path/file name/ID # of the structure node in which the file will be inserted/file name with extension

If the structure has several folder levels, enter only the ID # of the folder in which the file will be inserted, without the need to add upper level folders. For example: c:\user\file.doc|Folder1\file.doc

This column must be filled out if, in the document category, it is defined that the revision process uses the ISO 9000 model, the route type is Variable, and there is no revision route selected in the corresponding field.

Enter the start date of the document revision process. This date will be available on the document data screen, in the Revision > General > Control section, in the Start date field of the Actual grouping.

Enter the date in the YYYY-MM-DD format (for example: 2025-02-17).
If the date is not inserted in the spreadsheet, the system will automatically use the import date.

Adjust the column title to match the ID # of the attribute associated with the category in which the document will be created.
Then, in the corresponding cells, enter the desired value for each attribute.

If the attribute is multivalued, use a semicolon ( ; ) to separate the values.
If an attribute value contains the semicolon character ( ; ), use the Separator column (described below) to indicate another character that will be used as separator in the values of the attributes.

Insert as many columns as needed, according to the number of attributes defined for the category.

Fill out this column only if you wish to use any separator other than the default one.
By default, the system uses:

• Comma (,) to separate values of multivalued attributes;
• Semicolon ( ; ) to separate values of electronic files and keywords.

If you prefer to use other characters, enter a character or a sequence of characters that are not present in the values to be inserted.
Examples: #, $, %, @, etc.

If this column is not filled out, the default separators (comma and semicolon) will be used automatically, as described above.

This column is optional and must be used only to import a revision to a document that already exists. Insert one of the specified values in order for the system to perform the corresponding operation:

1. Verification of existing documents

• The system checks if there is a document with the provided ID #.
  If there is one, an error alert will be issued, and the creation will not be carried out.

2. Creation of existing revisions

• The system checks if there is a document with the provided ID #.
• If the document exists, the system will create a new revision for it.
• If the document does not exist, the system will issue an error alert and will not create either the document or the revision.

3. Creation of revisions or new documents

• The system follows the verification process from the previous steps:
• If the document exists, a new revision will be created.
• If the document does not exist, the system will create a new document.

4. Editing of existing documents

The system checks if there already is a document with the provided ID #.
If there is one, the system will edit its data by changing its: ID #, category, revision ID #, and validity date.

Restrictions:

• It is not possible to add, delete, or edit electronic files.
• It is not possible to edit or delete revision step participants for the ISO 9000 model; the system only allows for adding new participants to documents without a revision route associated.
• The fields that must not be edited must remain blank in the spreadsheet (except for the Validity date field, which is mandatory).
• If the document does not exist, or if the specified revision is not the current one, the system will not carry out the import.

Enter the validity date of the documents that will be created. This date indicates until when the document will remain valid.

In order for the completion of this field to be accepted, the default validity time associated with the previously selected category must be configured as Variable. Otherwise, the system will issue an error alert and will not carry out the import.

The configuration of a default validity time can be set in the Control tab of the data screen of the corresponding category.

Enter the ID # of a document previously created in the system, to which the documents for import will be linked as part of its structure. If there is not a document with the provided ID #, the system will issue an error alert and will not carry out the import.

This column must be filled out if, in the document category, it is defined that the revision process uses the ISO 9000 model, the route type is Variable, and there is no revision route selected in the corresponding field.

Enter the ID of the users participating in the draft step referring to the revision of the documents to be created, as well as the number of days for the step to be executed.
If the step has been executed already, enter the execution date instead of the number of days and insert value 1. Otherwise, do not enter any additional value.

Use a semicolon ( ; ) to separate the pieces of information.
If the draft step has more than one participant, separate them with a vertical bar ( | ).

For example: USER001;5|USER002;2019-06-26;1

USER001 has not executed the revision step; therefore, the deadline will be calculated from the provided "Start date (Actual)" date and from the recorded number of days.

USER002 has executed the step, so the execution date and value 1 have been inserted.

Conclusion: All defined participants will have a revision sequence equal to 1.

This column must be filled out if, in the document category, it is defined that the revision process uses the ISO 9000 model, the route type is Variable, and there is no revision route selected in the corresponding field.

Enter the ID of the users participating in the review step referring to the revision of the documents to be created, as well as the number of days for the step to be executed.
If the step has been executed already, enter the execution date instead of the number of days and insert value 1. Otherwise, do not enter any additional value.

Use a semicolon ( ; ) to separate the pieces of information.
If the draft step has more than one participant, separate them with a vertical bar ( | ).

For example: USER001;5|USER002;2019-06-26;1

USER001 has not executed the revision step; therefore, the deadline will be calculated from the provided "Start date (Actual)" date and from the recorded number of days.

USER002 has executed the step, so the execution date and value 1 have been inserted.

Conclusion: All defined participants will have a revision sequence equal to 1.

This column must be filled out if, in the document category, it is defined that the revision process uses the ISO 9000 model, the route type is Variable, and there is no revision route selected in the corresponding field.

Enter the ID of the users participating in the approval step referring to the revision of the documents to be created, as well as the number of days for the step to be executed.
If the step has been executed already, enter the execution date instead of the number of days and insert value 1. Otherwise, do not enter any additional value.

Use a semicolon ( ; ) to separate the pieces of information.
If the draft step has more than one participant, separate them with a vertical bar ( | ).

For example: USER001;5|USER002;2019-06-26;1

USER001 has not executed the revision step; therefore, the deadline will be calculated from the provided "Start date (Actual)" date and from the recorded number of days.

USER002 has executed the step, so the execution date and value 1 have been inserted.

Conclusion: All defined participants will have a revision sequence equal to 1.

This column must be filled out if, in the document category, it is defined that the revision process uses the ISO 9000 model, the route type is Variable, and there is no revision route selected in the corresponding field.

Enter the ID of the users participating in the release step referring to the revision of the documents to be created, as well as the number of days for the step to be executed.
If the step has been executed already, enter the execution date instead of the number of days and insert value 1. Otherwise, do not enter any additional value.

Use a semicolon ( ; ) to separate the pieces of information.
If the draft step has more than one participant, separate them with a vertical bar ( | ).

For example: USER001;5|USER002;2019-06-26;1

USER001 has not executed the revision step; therefore, the deadline will be calculated from the provided "Start date (Actual)" date and from the recorded number of days.

USER002 has executed the step, so the execution date and value 1 have been inserted.

Conclusion: All defined participants will have a revision sequence equal to 1.

This column must be created and filled out only if the Physical file control is defined in the document category.

When this column is completed correctly, the document will be archived automatically in the first step configured in the record retention schedule associated with the category, without task generation.

Insert the physical path in the following format: storage place + . + repository ID #

For example: Storeroom.Cabinet 02.1

The document will not be created if:

• The column is created, but the storage place and the repository are not specified.
• The storage place or the repository is not found.
• The repository had its capacity limit exceeded.
• The record retention schedule has only the final destination step configured and it is not "Associate new repository".
• The "Restrict department to access physical record" parameter is checked and the specified repository does not belong to the same department as that of the user who is performing the import.

Additional rules:

• If the record retention schedule has only the "Media burning" step configured, the document will be created, but the task referring to this step will have to be executed manually.
• If the category is not created and the Physical file control is enabled, the document will be created, but not archived.