Documents - Migration Guide

Version Date Notes By
0.3 2018-10-26 Added Attributes JFM
0.2 2018-10-25 Added Document files JFM
0.1 2018-10-25 Initial release JFM

Document Tree (t01w016)

The document tree is save under the table t01w0016 not as a normal tree but with a following structure:

  • Each tree node is save without the parent node but instead are given and order number
Field Description/Notes
C2720 Node ID - Nor very usefull
C2721 Document revision ID or Document Family ID
C2722 ID from the itemn table
C2723 1 - Means its from a document family, 2 means is a document revision.
C2736 Order of all the branches
C2733 Oder of the branch path

Example

Having a document family (id 10) with the following tree:

-> Engineering Department (id 100)
------> Instructions (id 50)
-> Quality Department (id 200)
------> Instructions (id 50)

The data is saved like this

C2720 C2721 C2722 C2723 C2736 C2737
1 10 100 1 0 0
2 10 50 1 0 1
3 10 200 1 1 0
4 10 50 1 1 1

Document files

The original document is saved on the folder cdoc\intra_doc\documentosOriginais\

The viewing file is save on the folder cdoc\intra_doc\documentos\

Both are named using the MD5 of the version id (C1019) + file extension to guarantee uniqueness (hopefully)

Some clients dont have the Original Document option, and others (older) clients might use a diferent naming strategy, so you must always check on the client specific documentation

Attributes

Attributes are defined by classe (family) and used when inserting documents. Every classe that have attributes have a table named ATR_ wich will have the attribute values by document revision

This tables have a fixed field name C0 wich will hold the document revision id. All other field are atributes and are named ATR

Example

Attribute definition on t01w047 for family id 100

C13690 C13691 C13692 C13693
1 100 Tipo de Documento ATR1
5 100 Morada ATR5
9 100 Telefone ATR9

Corresponding atribute table (ATR_100)

C0 ATR1 ATR5 ATR9
10 Carta Morada X 999999999
11 Fax Morada Y 888888888