The issue is still there. My form is not getting triggered also when I set it to print without any condition ; like giving a trigger of EVERYPOLICY and setting that to 'Return(1)' in Setrcptb.dal file.
Here is what I get after I run my gendaw32;
Company Name (after ini conversion): ANY
Line of Business (after ini conversion): TESTXML
Trans Type: NB
Run Date: 20120831
DM10797: Warning in SetNextImage(): No forms for current transaction. FAPTotalForms(pRPS->CurrentFapFormsetH) < 1). Processing will continue.
Now I am getting the forms triggered, I guess the issue was with AFGJob.jdt file.
One new issue creeping up is - we are not getting prints ; it says our BATCH file is empty when I try to run genptw32 transaction.
This is what I have in Errfile.dat -
DM17065: Warning in GENGetRecipientSet(): BATCH1 batch is empty, Unable to RCBGetFirstRcpSetRec(NULL).
When I use the Test stream scenario ; I could see the following:
On Form level trigger
Trigger - Group 1 <any> Group2 <TESTXML> Form <TESTXMF> Search Mask <!/DOCUMENT/DOCSET/KEY2='5'>
Trigger - Group 1 <any> Group2 <TESTXML> Form <TESTXMF> returned 1.
On section level trigger
Trigger - Group 1 <any> Group2 <TESTXML> Form <TESTXMF> Section <TESTXM> Search Mask <!/DOCUMENT/DOCSET/KEY2='5'>
Trigger - Group 1 <any> Group2 <TESTXML> Form <TESTXMF> Section <TESTXM> returned 0.
How can same trigger condition give '1' for the first time and '0' for the second time?
Please check for the below in your library since you are getting an empty batch.
1) Check in the Forms Trigger (at the GRP File level), whether you have given appropriate Trigger condition and Recipients are selected.
2) Check you have proper routing settings defined in your INI files say using <BatchingByRecip> and define the recipient batches.
3) You may also use the "IfRecipUsed" Form set level rule in Afgjob to designate recipients to corresponding batches say, ;IfRecipUsed;;BATCH1=INSURED;
;RULStandardJobProc;1;Always the first job level rule;
/* Every form set in this base uses these rules. */
<Base Form Set Rules>
;RULStandardTransactionProc;2;Always the first transaction level rule;
/* Every image in this base uses these rules. */
<Base Image Rules>
;RULStandardImageProc;3;Always the first image level rule;
/* Every field in this base uses these rules. */
<Base Field Rules>
;RULStandardFieldProc;4;Always the first field level rule;
Could you please correct these for any mistakes ?
I used the <BatchingByRecip> setting also; but it didn't help.
[Oracle Delivery Cloud|https://edelivery.oracle.com/EPD/Download/get_form?egroup_aru_number=15238196] [Oracle Delivery Cloud|https://edelivery.oracle.com/EPD/Download/get_form?egroup_aru_number=15238196] Your XML structure is something that should be reconsidered. You are attempting to use a XML structure that is documented in the Documaker XML Guide for the XML Import configuration of Documaker not the rules processor configuration. Your AFGJOB and INI files indicate that you are trying to use the rule processor configuration.
The XML Import style of XML requires you to use the structure where you specify the tags for specific use shown below under *****XML IMPORT EXAMPLE **** file. While this is valid XML and will work, it is probably the most restrictive XML design. The intent of the Import XML implementation is to make Documaker a dumb print engine - you tell it exactly what you want to include in the final output. The documentation clearly states the following on the chapter of the XML Guide that is labeled Importing and Exporting XML Files with Documaker Server.
+"Keep in mind that importing XML is not the same as using an XML file as your extract file. Import assumes you are using a specific file layout that describes your document in a predefined manner."+
It is the least flexible and requires the person deigning the forms to also understand the data structure, it cannot take advantage of any of the rule processing (RP) features that make the product worth the $$ that customers spend on it.
Documaker can use any well formed XML file (it can be successfully opened in a browser is the simplest test). You really should not mix and match the AFGJOB IfRecipUsed and the batching by recip rules - they are not intended to be a mix you are missing the AFGJOB rules that invoke batching by recip: ;BatchingByRecipINI;2;; and optionally ;BatchingByPageCountPerRecipINI;;;.
There are only three possibly two fields that you need to have consistent to use Documaker in the RP configuration: Key1, Key2 and KeyID. The Key1 and Key2 drive the group selection you can omit one if you only have one group - KeyID is used as the transction ID to track the transaction in the system (consider if there is an error). I would suggest that you possibly use sample MRLS that are available the Oracle Delivery Cloud (https://edelivery.oracle.com/EPD/Download/get_form?egroup_aru_number=15238196) part number V33403-01 as a example the DMS1 sample is fully running and may give you some better insight into how to implement.