Shared Fields Page
Shared fields page shows the list of pre-defined shared fields and allows to define new shared fields or delete them.
But what is shared field?
All Composite Data Types in Codejig Builder except embedded and transient have field "identifier" holding the unique number for each instance stored in the database, all document data types contain field "document timestamp" - this fields are common for a group of data types. If we decide to rename field "identifier" to "id", we'd like to do it once, not in each data type separately. Exactly for these purposes Codejig Builder introduces Shared Field concept - a field that is "shared" between different data types and has the same id in all data types. "Identifier", "document timestamp" are examples of predefined system shared field (see list of all such fields below), but you can also create your own shared fields.
You can create your Shared Fields on Sahred field's page (link is available in Codejig Builder's Menu). To add a shared field to a data type go to Details Page of this data type.
|identifier||Integer||Read only. The Unique number for each instance stored in the database. Its value is generated automatically during persistence.||Directories, Documents, Reports, Journals|
|Metainfo||MetaObject||Read Only. This field contains various system info (version, date of creation, etc.) and exists mostly for system purposes and should rarely be used by Codejig Builder's users.||Directories, Documents, Reports|
|serial number||SystemString||Nullable string without translations. Business records usually require a serial number. This field is widely used in CodejigEPR.|
Its content can be autogenerated by Sequences.
|Directories, Documents, Reports|
|document timestamp||Timestamp||All documents are dated. Document timestamp determines the order of applying documents. Document timestamp of the journal's record is equal to the document timestamp of its registrar.||Documents, Journals|
|registrar||Dynamic||Read only. As the only way to create journal's records is applying a document, each journal's record has exactly one document which has registered this record.||Journals|
|relative order||Integer||For collection fieds of embedded type determines the order of embeddeds inside a collection. Has no sense for embeddeds outside collections.|
For non-embeddeds this field determines order of items in tree view (see Tree View for more details).
|Directories, Documents, Reports, Embeddeds|
TODO :: add info about reports system fields