pub:databasemapping
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionLast revisionBoth sides next revision | ||
pub:databasemapping [2013/12/04 16:38] – external edit 127.0.0.1 | pub:databasemapping [2017/11/28 15:59] – [Introduction] ken | ||
---|---|---|---|
Line 5: | Line 5: | ||
===== Introduction===== | ===== Introduction===== | ||
- | Database Mapping, a new module of iDocs, supports the user when merging an application overlay with a database directly, e.g. iForms, iChecks ACH. The following information is designed to assist the user. | + | Database Mapping, a new module of iDocs Version 6.90 (11/ |
===== Overview of User's Guide ===== | ===== Overview of User's Guide ===== | ||
- | Access to Database Mapping is found within the main menu of the “Work with Form Applications”, | + | Access to Database Mapping is found within the main menu of the “Work with Form Applications”, |
{{pub: | {{pub: | ||
}} | }} | ||
- | [[DatabaseMappingMergerFormwithdatabase]] | + | |
+ | |||
+ | {{pub: | ||
+ | |||
+ | |||
===== Work with Database Mapping - Option 19 ===== | ===== Work with Database Mapping - Option 19 ===== | ||
Line 24: | Line 29: | ||
**Exploring the Edit Database Map Screen** | **Exploring the Edit Database Map Screen** | ||
- | **Master file (Optional to the user)** | + | **Master file** |
- | Data entered into the master file field becomes a report’s | + | (Optional) The data contained on the master file will be treated as the header |
- | **Level file (Optional to the user)** | + | **Level file** |
- | Level file data is the detail | + | (Optional) The data contained on the Level file will be treated as the detail |
**Master Field and Level Field** | **Master Field and Level Field** | ||
- | If both the Master file and Level file are used, these fields must be specified. The files are linked by Master Field and Level Field. | + | These fields must be specified if both the Master file and Level file are used. The files are linked by Master Field and Level Field. |
- | Below is a sample report: | + | |
+ | A sample report | ||
{{pub: | {{pub: | ||
Line 48: | Line 53: | ||
{{pub: | {{pub: | ||
- | Below shows the results when the entered value is 2 and there are 5 records in the level file: | + | Changing |
{{pub: | {{pub: | ||
- | Note: Because | + | Note: There is a total of 3 pages, but because |
{{pub: | {{pub: | ||
Line 58: | Line 63: | ||
**Email Output Spool Manually** | **Email Output Spool Manually** | ||
- | To email output | + | If the user wants to email output manually, |
**Fax Output Spool Manually** | **Fax Output Spool Manually** | ||
Line 66: | Line 71: | ||
**Retain Output after Email/Fax** | **Retain Output after Email/Fax** | ||
- | This option allows for the retention or deletion of the output spool after it is manually faxed or emailed. | + | This option allows for the retention or deletion of the output spool after it is manually faxed or emailed. |
===== Working with the Master Field ===== | ===== Working with the Master Field ===== | ||
- | From the ‘Edit Database Map’ screen, press F7 to open the “Database Field Maintenance screen”. | + | From the ‘Edit Database Map’ screen, press F7 to open the “Database Field Maintenance screen”. |
{{pub: | {{pub: | ||
- | The Map Field Maintenance screen | + | From the Database |
- | Note: The iDocs User Guide only briefly refers | + | |
{{pub: | {{pub: | ||
+ | |||
+ | The Map Field Maintenance screen looks similar to the interface of the Spool DataMap Field Maintenance screen, but it no longer uses the **From Row**, **To Row**, **From Column**, **To Column** fields. | ||
+ | |||
+ | Below is a in-depth explanation of the fields described in the iDocs User Guide. | ||
**Date format** | **Date format** | ||
Line 117: | Line 124: | ||
===== Working with the Level Field ===== | ===== Working with the Level Field ===== | ||
- | From the ‘Edit Database Map’ screen, select F8 to open the “Database Map Field Maintenance” screen. | + | From the ‘Edit Database Map’ screen, select F8 to open the “Database Map Field Maintenance” screen. |
{{pub: | {{pub: | ||
+ | |||
+ | From the Database Map Field Maintenance screen, press F6 to add a new field or select option #1 to edit an existing field. | ||
{{pub: | {{pub: | ||
Line 131: | Line 139: | ||
===== Working with the Footer field ===== | ===== Working with the Footer field ===== | ||
- | From the ‘Edit Database Map’ screen, press F9 to open the “Database Field Maintenance” screen. | + | From the ‘Edit Database Map’ screen, press F9 to open the “Database Field Maintenance” screen. |
Note: The footer fields are available only when the level file is defined for database mapping. | Note: The footer fields are available only when the level file is defined for database mapping. | ||
{{pub: | {{pub: | ||
+ | |||
+ | From the Database Map Field Maintenance screen, press F6 to add a new field, or select option #1 to edit an existing field. | ||
{{pub: | {{pub: | ||
Line 144: | Line 153: | ||
{{pub: | {{pub: | ||
- | To display all the valid level fields within database mapping, select F4 (List) within the “Field Name” field. | + | At the ' |
Only the level fields defined for database mapping are selectable. | Only the level fields defined for database mapping are selectable. | ||
- | Note: Conditionally | + | Note: With the footer field, the conditional |
===== Bursting and Sorting ===== | ===== Bursting and Sorting ===== | ||
Line 155: | Line 164: | ||
If both Master and Level files are specified, the bursting function will be defined for the Master Field. | If both Master and Level files are specified, the bursting function will be defined for the Master Field. | ||
- | When using the sorting | + | Sorting |
+ | Specify | ||
If sorting is not indicated, the file will be sorted by either key fields or sorting fields. | If sorting is not indicated, the file will be sorted by either key fields or sorting fields. | ||
- | For example, the following setting will arrange | + | For example, the following setting will break the output result |
{{pub: | {{pub: | ||
Line 173: | Line 183: | ||
The built-in special fields from the list above include: | The built-in special fields from the list above include: | ||
- | 1. *DATE: return the current system date. You can format the output value with field ‘Date format’ | + | * |
- | + | | |
- | + | | |
- | 2. *DOCNAME: return the name of a current map. | + | |
- | + | | |
- | 3. *DOCTEXT: return the description of a form, check or ACH. | + | * |
- | + | | |
- | 4. *PAGENBR: return the current page number. This field is useful when you merge an overlay with a map, and wish to auto number pages. | + | |
- | + | ||
- | 5. *TIME: return the system time with format HH:MM:SS | + | |
- | + | ||
- | 6. *USER: return the user name of a current job. | + | |
An example of a user-defined special field, a field returning a value assigned by the user, is the *COPYRIGHT option above. | An example of a user-defined special field, a field returning a value assigned by the user, is the *COPYRIGHT option above. | ||
- | |||
- | To define a new field press F11 from the ‘Edit Database Map’ screen to open the User-Defined Field screen. | ||
{{pub: | {{pub: | ||
+ | To define a new field press F11 from the ‘Edit Database Map’ screen to open the // | ||
{{pub: | {{pub: | ||
Note: Only User-defined fields are editable or removable in the maintenance screen. | Note: Only User-defined fields are editable or removable in the maintenance screen. | ||
- | |||
- | |||
To define a new user-defined field, press F6: | To define a new user-defined field, press F6: | ||
Line 207: | Line 207: | ||
This action is similar to ‘Merge with Spool Mapping’. | This action is similar to ‘Merge with Spool Mapping’. | ||
- | {{pub: | + | {{pub: |
+ | |||
+ | **Outq name** : enter the output queue name \\ | ||
+ | **Copies** | ||
+ | **Font** | ||
+ | **Spool file name** : change the default output PCL name (FMGLASER) \\ | ||
+ | **Override Master/ | ||
+ | **Manual Email (Fax):** there are 03 valid values on these fields | ||
+ | * **Blank** | ||
+ | * **Y** | ||
+ | * **N** | ||
+ | **F6=Override Master (Level) Cond**: Change the conditional settings (filters) of master (level) file | ||
+ | |||
+ | {{pub: | ||
+ | |||
+ | From the override condition screen, a user is able to see the condition settings of current form and then can override the conditions. | ||
**API of merge** | **API of merge** | ||
Line 213: | Line 228: | ||
You also can use the IMRGDBMAP command to merge a database map with an application. | You also can use the IMRGDBMAP command to merge a database map with an application. | ||
- | {{pub: | + | {{pub: |
The application name can be a form, a check or an ACH name. | The application name can be a form, a check or an ACH name. | ||
+ | **Application name** : enter the application name.\\ | ||
+ | **Outq name** | ||
+ | **Copies** | ||
+ | **Font** | ||
+ | **Spool file name** | ||
+ | **Override Master/ | ||
+ | **Manual Email (Fax) :** there are 03 valid values on these fields | ||
+ | * **Blank** : use the value of form definition. | ||
+ | * **Y** : enforce the output PCL is emailed despite the ‘Manual Email (Fax)’ setting in form definition. | ||
+ | * **N** : enforce the output PCL is ignored to email despite the ‘Manual Email (Fax)’ setting in form definition. | ||
+ | **Override Master (Level) File Condition**: | ||
+ | |||
+ | {{pub: | ||
===== Some Helpful Tips to Define an Application ===== | ===== Some Helpful Tips to Define an Application ===== | ||
pub/databasemapping.txt · Last modified: 2022/06/25 17:02 by 127.0.0.1