inFORM Decisions Information Portal

User Tools

Site Tools

Trace:
pub:databasemapping

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
pub:databasemapping [2015/07/13 14:30] – [Merge an Application with a Database Map] kenpub:databasemapping [2017/11/28 15:59] – [Introduction] ken
Line 5: Line 5:
  
 ===== Introduction===== ===== Introduction=====
-Database Mapping, a new module of iDocs Version 7, that supports the user when merging an application overlay (Forms, Check, ACH) with a database directly. The following information is designed to assist the user.   +Database Mapping, a new module of iDocs Version 6.90 (11/28/2017), that supports the user when merging an application overlay (Forms, Check, ACH) with a database directly. The following information is designed to assist the user.   
  
 ===== Overview of User's Guide ===== ===== Overview of User's Guide =====
Line 15: Line 15:
  
  Navigate to the two new Database Mapping options, “19=Work with database map” or “20 Merge with database map” by selecting the “More Options” key, F23.  Navigate to the two new Database Mapping options, “19=Work with database map” or “20 Merge with database map” by selecting the “More Options” key, F23.
-{{:pub:databasesscreenprint2.png?&900|----}}+ 
 +{{pub:databasesscreenprint2.png?&950|----}} 
  
  
-[[DatabaseMappingMergerFormwithdatabase]] 
  
 ===== Work with Database Mapping - Option 19 ===== ===== Work with Database Mapping - Option 19 =====
Line 206: Line 207:
 This action is similar to ‘Merge with Spool Mapping’. This action is similar to ‘Merge with Spool Mapping’.
  
-{{pub:mergeappwithdatabasemapscreen.png|}}+{{pub:mergeappwithdatabasemapscreen.png?900|}}
  
 **Outq name** : enter the output queue name \\ **Outq name** : enter the output queue name \\
Line 214: Line 215:
 **Override Master/Level File**: If a user wants to change the master file or level file which is defined in form, he can manually input the override file name on these fields. \\ **Override Master/Level File**: If a user wants to change the master file or level file which is defined in form, he can manually input the override file name on these fields. \\
 **Manual Email (Fax):** there are 03 valid values on these fields **Manual Email (Fax):** there are 03 valid values on these fields
-      * **Blank**          : use the value of form definition. +  * **Blank**          : use the value of form definition. 
-      *  **Y**          : enforce the output PCL is emailed despite the ‘Manual Email (Fax)’ setting in 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.+  * **N**          : enforce the output PCL is ignored to email despite the ‘Manual Email (Fax)’ setting in form definition.
 **F6=Override Master (Level) Cond**: Change the conditional settings (filters) of master (level) file  **F6=Override Master (Level) Cond**: Change the conditional settings (filters) of master (level) file 
  
-{{:pub:databasemapfieldconditions.png|}}+{{pub:databasemapfieldconditions.png?900|}}
  
 From the override condition screen, a user is able to see the condition settings of current form and then can override the conditions. From the override condition screen, a user is able to see the condition settings of current form and then can override the conditions.
Line 227: 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:mergewithappapi.png|}}+{{pub:mergewithappapi.png?900|}}
  
  
 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**     : enter the output queue name.\\
 +**Copies**     : enter the number of copies.\\
 +**Font**        : select to change the default font ID.\\
 +**Spool file name**  : change the default output PCL name (FMGLASER).\\
 +**Override Master/Level File** : If a user wants to change the master file or level file which is defined in form, he can manually input the override file name on these fields.\\
 +**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**: Change the conditional settings (filters) of master (or level) file by enter a SQL statement, for example
 +
 +{{pub:mergewithappapi2.png?900|}}
 ===== 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