In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   On Demand  |   Home  |   qad.com




Mapping a Program for Regular Non-UIAPI Interface Programs
You do not need to manually map non-UIAPI programs field by field. Instead, you can use the ADAPTER: (x) SI API option under QGen/Generate Schema to map and generate the schema and place it in the receiver for you.
Use this tool for customized versions of CHUI screens to work with SI APIs, customizations made using ICT and .Net UI Configurable screens. Each customization is defined somewhere in the data. In the case of ICT, customizations are configured in the database; for the .Net UI, customizations are defined in the XML configuration file. Customizations are normally executed by session triggers, but the system replicates them in the background without relying on any UI triggers to fire them up.
When the user has added additional fields to the screen, there is a problem. The SI API requires that the XML that comes in matches the schema defined for that API. If you have added additional fields to the standard screen, you will get an error if the XML contains these new fields not present in the schema. Use QGen to create schemas for SI APIs. However, there is no need to go through the UI screen with QGen to define iterations and map each field.
1
Run a QGen client session script. Press Ctrl+O to open the Options Menu and choose Generate Docs; then press F1.
2
Choose the appropriate options.
Adapter:
Select SI API.
QDoc Name
Enter the QDoc name; for example, enter maintainItemMaster for Item Maintenance (1.4.1).
User
Enter a user to apply the customization to. If you leave the field blank, the customization will apply to all users.
3
Enter appropriate information to connect to the QXI server.
4
Select a QAD Enterprise Applications version from which to get the receiver list.
5
Choose the SI API receiver name and press Continue.
6
The new schema is now uploaded directly to QXI and the receiver you identified earlier. When you create an empty QDoc, the new custom fields are available.
7
Add the .Net UI runtime directory to the PROPATH of the QGen client (where the configurable screens configuration file resides).
Edit QXtendAdapter /script/client.qgen and add “mfgInstallDir /qadui/com/mfgpro” to the PROPATH.
Add “mfgInstallDir /qadui/com/mfgpro” to the PROPATH of qadSI_AS appserver.
For EE, add the following:
For any custom or configurable programs, add “PROPATH = /qxiadapter, /mfgsvr/lib/qra.pl, /mfgsvr/bbi,/mfgsvr”.
For configurable screens, add “mfgInstallDir /qadui/com/mfgpro ” to the PROPATH of the .NET Progress code:
PROPATH = /qxiadapter, /mfgsvr/lib/qra.pl, /mfgsvr/bbi,/mfgsvr,/<custom or configurable programs>,mfgInstallDir /qadui/com/mfgpro
ICT also has the facility to dynamically add new fields to the screen, and it will work for that too as long as ICT is in the PROPATH. ICT also allows you to execute additional programs that may have fields statically defined in them. In this case, you would need to modify the .p manually to conform to Native API standards and modify the schema yourself.