How to Add Parametric Fields to Reports and the Global Tag List
Information
You can quickly reach the relevant topic with the help of navigation on the right side.
Adding Parametric Fields to Reports in Document Management Module and General Tag List User Help Document
1.Adding Parametric Fields to Reports in Document Management Module and Tags Used in Reports
Parametric field is added to the "MasterSablon_TR.xls" format, which is the report format of the Document Summary List report from the Document Management Module reports. The steps to add these parametric fields to reports and the list of tags (shortcodes) used in the Document Management Module are included in this help document
1.1.Display of Parametric Fields in Document Management Module in Document Summary Report
In order to show the parametric fields added to the Document Summary List report in the Document Management Module reports, it is necessary to first define the parametric field in the language settings menu. In the language settings, parametric field definition such as text, list, etc. is done. These defined parametric fields are displayed in the Document Management module in the other information tab in the menus such as document preparation, document transfer to the system and so on. In the process of preparing a document or transferring a document to the system, the information of the defined parametric fields in the other information tab is entered. After preparing a document or transferring it to the document system, go to the Report formats menu. The report format (MasterSablon_TR.xls) of the Document Summary List report is downloaded from the Report Formats menu. If you want to use this downloaded report format (MasterSablon_TR.xls) as a code such as <DOC_ADI```>, <DOC_KODU\>in the document file of the fields defined in the language settings, it will be enough to write the area code in the tag without lbl. For example, if you want to use code in the downloaded report format for lblFIELD2, it is written as the shortcode<FIELD2\>```. In this way, the parametric fields in the other information tab of the document transferred to the system in the document preparation or document transfer menus are written as a tag in the Document Summary List Report format. After the parametric fields are written as tags in the report format, the report format (MasterSablon_TR.xls) is saved to the computer with the same name. The Document Summary List Report format with the same name saved is uploaded to the system again in the Report Formats menu. Document Summary List After uploading the report format, go to the Document Summary List Report menu in Document Management's Reports. On the screen that opens, the document uploaded to the system with the process of preparing the document or transferring the document to the system is displayed. While the document is selected, the Excel export button is clicked and the Excel format is taken into the report where the tags of the parametric fields are located in the section where the field information entered in the other information is seen to come and the tags are seen to work.
1.1.1.Defining a Parametric Field in a Document Management Module
In the Document Management Module, go to SAT```>BSAT\>Configuration Settings\>```Language settings menu for parametric addition. In the Modules area, Document Management Module is selected.
After selecting the Document Management Module, after the list comes to the Headings tab and lblALAN is written in it. FIELD2,FIELD3 listed here,.... FIELD6 text type fields ,lblFIELD7,lblFIELD8 ..... lblFIELD11 is a list type of parametric fields. Text-type and List-type parametric field definitions are made and in order to show these fields in the Document Summary List report, first text-type and then list-type parametric identification is performed.
1.1.1.1.Text Type Parametric Field Identification Process
In the Document Management Module, in other menus such as Integrated Management System>Document Operations> Document Preparation, in other menus, in order to define a text-type field in the other Information tab, first go to the System Infrastructure Definitions/ BSAT/ Configuration Settings/ Language Settings menu, search for text-typed parametric fields by typing text in the type field and the list of text-typed parametric fields is listed in the Language settings menu. Parametric fields with the text type listed are defined as fields. This text-typed field will then be defined to use the tag to display it in the Document Summary list.
lblFIELD2 To enter the data of the field by selecting a parametric field with text type, (change) button is clicked.
By filling in the required fields such as the order no information whether the field will be mandatory or not(save) button to record the text type parametric field definition.
1.1.1.2.List Type Parametric Field Identification Process
In order to define a list-type parametric field in the other information tab in other menus such as Integrated Management System```>Document Operations\>``` Document Preparation menu in the Document Management Module, first go to the System Infrastructure Definitions/ BSAT/ Configuration Settings/ Language Settings menu, search for list-type parametric fields by typing a list in the type field and the list of list-type parametric fields is listed in the Language Settings menu. The field definition of the listed list-type parametric fields is made. This list-type field will then be defined to use its tag in the process of showing it in the Document Summary list.
lblFIELD7 For data entry of the field by selecting the list type parametric (change) button is clicked.
To enter the list values of a list-type field Click the (New) button, type the list values and save them.
The list is defined for a value of 1.
The list is defined for a value of 2.
Whether the field will be mandatory or not, by defining the sequence no information and list elements and filling in the required fields(save) button to record the list-type parametric field definition.
If you want to use these fields we have defined as codes such as <DOC_ADI```>, <DOC_KODU\>to the document summary list report format, it will be enough to write the area code in the tag without lbl. The code to be used in the Document Summary List report format for the parametric field lblFIELD2 that we defined with text type is the short code<FIELD2\>. For the list-type lblFIELD7 parametric field, the shortcode <FIELD7\>``` will be used in the Document Summary list report format.
1.1.2.Entering the values of fields to be added to the document summary list
In order to enter the values of the fields to be added to the Document Summary list, the value of the field is entered in the other information tab in the menus such as Document Preparation, Export to My Document Site. A document upload process is made to the system to make this process necessary. To upload this document, click SAT```>Document Operations\>```Document Transfer to System menu. In this menu, a document is transferred without approval and control. With this menu, the values of these fields in the Other information tab are entered in the document upload process. After these field values are entered, the labels of the fields added to the report format and the reflection of these parametric fields to the report are performed. Field information must be entered in order to obtain the information of the field values defined in the report.
On the screen that opens, the folder to which the document will be transferred is selected and the ! Click the (Next) button.
Document information is entered on the Document Information tab. Click the More info tab to enter the information for the parametric fields defined in the Language settings. These fields are the text-type "Document Description" and the list-type "Document Type" parametric fields.
Document detail information is entered and the document to be uploaded is selected. This is the same as in the document preparation menu.
After all the information is entered into the system, the document is imported with the "Add File" button from the "Document File Upload (Turkish)" area.
After uploading the document to the system, the message "The file has been successfully transferred" is received.
On the document information screen, click ! With the help of the (Save) button, the transfer of the document to the system is completed.
Document transfer menu to the system A document is transferred to the system without approval and control. In the process of transferring this document to the system, the information of the parametric fields defined in the document management module is entered.
1.2.3.Adding Tags of Parametric Fields Defined to Report Format to Document Summary List
To add the tags of the defined parametric fields to the Document Summary list, go to SAT```>BSAT\> Configuration Settings\>```Report Formats menu. Qdms is the menu from which all reports are loaded.
With the help of the buttons on the screen;
: A new report format is uploaded to the system.
: The report format selected in the list is displayed and downloaded.
: The report format selected in the list is deleted.
! By clicking the (View) button, the Document Summary List report format template (MasterSablon_TR.xls) is downloaded to the computer.
The information about the field definitions and tags of the parametric fields defined in the report format is written and the report is saved to the computer in the format of the same name. As in the example, the short code tag <FIELD2```>is written for the Parametric field with text type. For a list-type parametric field, the shortcode tag<Field7\>``` is written.
Report format of the same name ((MasterSablon_TR.xls) (New) button is loaded back into the system in the report formats menu.
In the Report formats menu, the report format of the same name is loaded.
1.2.4.Display of Parametric Fields Added to Document Summary List Report Format
After the report format upload process, which is tagged to the Document Summary list report format (MasterSablon_TR.xls), go to the Integrated Management System```>Document Operations\>Reports\>```Document Summary list report menu.
On the screen that opens, the folder containing the document transferred to the system in the Document to System menu is selected in the folder area to which it is connected(Search) button is clicked to bring the Document to the document summary list.
(Export to Excel) button displays the "Document Summary List Report".
It is seen that the tags in the Excel format report received with the Excel transfer button work and the values of the defined parametric fields are informative in the report.
2.Replacement (Shortcodes) Tag Table in Document Management Module
The list of common tags (short codes) used in the Document Management Module is in the table below.
| Acronym | Description |
|---|---|
<DOC_KODU```>``` | DocCode |
<DOC_TIPI```>``` | DocumentType |
<REV_NO```>``` | Revision No |
<MANUAL_REVNO```>``` | Manual Revision No |
<DOC_ADI```>``` | Document Name |
<DOC_ING_ADI```>``` | Document English Name |
<DOC_GRUP_KODU```>``` | DocGroupCode |
<DOC_GRUP_ADI```>``` | Document GroupName |
<DOC_HAZ_TAR```>``` | Preparation Date |
<HAZ_SICIL```>``` | Authored by Registry |
<HAZ_POZ```>``` | AuthorPositionCode |
<HAZ_POZ_TAN```>``` | AuthorPositionDefinition |
<CREDIT```>``` | AuthorNameLast Name |
<KONT_SICIL```>``` | Checked by Sicil |
<KONT_POZ```>``` | Controlling PositionCode |
<KONT_POZ_TAN```>``` | ControllerPositionDefinition |
<KONTROL_EDEN```>``` | CheckerNameLast Name |
<SORUMLU_SICIL```>``` | Responsible Registration Number |
<SORUMLU_POZ```>``` | ResponsiblePositionCode |
<SORUMLU_POZ_TAN```>``` | ResponsiblePosition Description |
<RESPONSIBLE```>``` | ResponsibleNameSurname |
<SOR_KISIM_KODU```>``` | ResponsibleDepartmentCode |
<SORUMLU_KISIM```>``` | ResponsibleDepartment |
<REV_SICIL```>``` | RevisedEdenRegistryNo |
<REV_POZ```>``` | RevisedByPositionCode |
<REV_POZ_TAN```>``` | RevisedEdenePosition Definition |
<REVIZE_EDEN```>``` | RevisedNameSurname |
<REV_TARIHI```>``` | RevisionDate |
<REV_NEDEN```>``` | RevisionReason |
<ONAY_TAR```>``` | Approval Date |
<SON_ONAY_SICIL```>``` | Final Approver Registry |
<SON_ONAY_POZ```>``` | Last Validator Position Code |
<SON_ONAY_POZ_TAN```>``` | Final Approver Position Description |
<SON_ONAY```>``` | Last Validator Name Surname |
<TUM_ONAY_SICIL```>``` | Track record of all Approvers |
<TUM_ONAY_POZ```>``` | Position of All Approvers |
<TUM_ONAY_POZ_TAN```>``` | Position descriptions for all approvers |
<TUM_ONAY_ADI```>``` | All Approvers Name Last Name |
<YAYIMLAYAN_SICIL```>``` | Published by Sicili |
<YAYIMLAYAN_POZ```>``` | Published by position code |
<YAYIMLAYAN_POZ_TAN```>``` | Posted by position description |
<PUBLISHER```>``` | Publisher name surname |
<YONETIM_SISTEMLERI```>``` | Management Systems |
<REFERANS_DOKUMANLAR```>``` | ReferenceDocs |
<GRUP_EGITICI```>``` | Instructor |
<X_ONAY_ADI```>``` | X. Approver's Name (X=1,2,3...) |
<X_ONAY_SCL```>``` | X. Approver's Record(X=1,2,3...) |
<X_ONAY_POZ```>``` | X. Approver's Position Code(X=1,2,3...) |
<X_ONAY_POZ_TAN```>``` | X. Approver's Position Description (X=1,2,3...) |
<PRN_KK```>``` | Controlled Copy Parameter (parameters QDMS-GEN-10,11) |
<P_SICIL```>``` | Print Area Registry |
<P_ADI```>``` | Print Alan Staff Name |
<P_TARIH```>``` | Print Date Received(dd.mm.yyyy) |
<P_UTARIH```>``` | Print Date Received (dd.mm.yyyy hh:mm:nn) |
<KONTROL_DEPARTMAN_ADI```>``` | Controlling person's Department |
<ONAYLAYAN_DEPARTMAN_ADI```>``` | Final Approver's Department |
<REVISION```>```** | Revision |
<KONTROL_TAR```>``` | Check date |
<REV_EDEN_DEPARTMAN```>``` | Reviser's Department |
<PROCESSES```>``` | Processes on which weaving depends |
<X_ID```>,\<X_DATE\>,<X_APPROVAL\>,<X_REASON\>,<X_REVISION\>,<X_REVIZE_EDEN\>``` is activated with parameter --79. | Revision History X=1,2,3.. |
<SUREC_KODLARI```>``` | Process Codes |
<REVEDEN_DEPARTMAN_KODU```>``` | Revised's Department Code |
<KONTROL_DEPARTMAN_KODU```>``` | Controller Department Code |
<ONAYLAYAN_DEPARTMAN_KODU```>``` | Final Approver's Department Code |
<ON_KONT_SICIL```>``` | Pre-Carrier's Registration Number |
<ON_KONT_POZ```>``` | Pre-Carrier's Position Code |
<ON_KONT_POZ_TAN```>``` | Pre-Controller Position Description |
<ON_KONT_EDEN```>``` | Pre-Controller's Name Surname |
<KONTROL_GRUP```>``` | Control Group Code |
<KONTROL_GRUP_ACK```>``` | Description of the Control Group |
<ONKONTROL_GRUP```>``` | Code of Preflight Group |
<ONKONROL_GRUP_ACK```>``` | Description of Preflight Group |
<GRUP_EGITICI_POZ_TAN```>``` | Trainer's Position Description |
<OZGECPOZ```>``` | Review Position |
<GOZ_GEC_TAR```>``` | Review Date |
<SONRAKI_GOZ_GEC_TAR```>``` | Next review date |
<HAZIRLAYAN_DEPARTMAN_ADI```>``` | Prepared by Department Name |
<U_TARIH```> : Used in the e-signature parameter. (Example: This document was approved by e-signature on \<U_TARIH\>```.)
3.Tags Used in Quality Record Documents for Quality Record
The list of tags used for quality recording is in the table below.
<KK_NO```>``` | Quality Record number |
|---|---|
<KK_ONAY_ADI```>``` | Name and surname confirming the Quality Record |
<KK_ONAY_POZ```>``` | Position code confirming Quality Record |
<KK_ONAY_POZ_TAN```>``` | Position description confirming Quality Record |
<KK_ONAY_TAR```>``` | Quality Record approval date |
<KK_HAZIRLAYAN```>``` | Quality Record creator |
4.Document Summary List Report Tag List
In document management, the list of all documents in the system is generally reached, and the name and description of the tags used for the report Document Summary List Report are included in the table.
```<DOC_KODU\>``` | Document Code |
|---|---|
<DOC_ADI```>``` | Document Name |
<DOC_ING_ADI```>``` | Document English Name |
<DTIP_ACK```>``` | Document Type |
<DOC_HAZ_TAR```>``` | Preparation Date |
<REVNO_SON```>``` | Revision No |
<REV_TARIHI```>``` | Revision Date |
<REVIZE_EDEN```>``` | Revised by |
<SORUMLU_KISIM```>``` | Responsible Part |
<REV_NEDEN```>``` | Revision Reason |
<REVISION```>```** | Revision |
<SON_GOZGEC```>``` | Last Review Date |
<GEL_GOZGEC```>``` | Next Review Date |
<GOZGEC_PER```>``` | Review Period |
<ONAY_TAR```>``` | Approval Date |
<PROCESSES```>``` | Processes Used |
<RESPONSIBLE```>``` | Document Responsible |
<DESTRUCTIONSaSU```>``` | Archiving Time |