I am trying to retrieve Forms that were issued during a transaction, Sections that triggered on those Forms, Variable fields used within those sections, and Data that populated those variable fields in a PostTransDal.
I am currently using Documaker Studio 11.3.
Are there any DAL functions that will allow me to gather that information?
Can you tell me what you are trying to do with that informaion? Asking because depending on what you are trying to do with the infromation, there may be other options to access this information (i.e. like a table of contents). Or are you trying to do this a runtime for other purposes? Or can it be done after execution?
I am trying to compile this information at runtime.
I want to validate the data within a Form after processing has occurred, based on some business defined rules, and stop printing if the data was not correct.
Ex. A zero premium is passed and Rp processes a Form that displays the zero premium. I would like to error out that transaction because a zero premium should not be displayed to the customer.
Ok, I would recommend that you do this at the form level/each form instead of as a PostTransDAL. The overhead in doing this might have some minor impact on process, where as if you do it in the form the data is already there and easily checked. You can do this specific to the form and not have to write a DAL that covers everything - long term maintetance of this could be a challenge if you do it as a PostTransDAL. Even better, you could also do it specific to the image, much easier to acces the variable field level.
Assuming that you do it on a single image at the end of the form, create an image that has no height and < teh wdth of your form and put it at teh end of every form that you want to check. Do a Post or Pre-Image DAL call on the section. If you put the CALL("XXXXX.DAL") on the form not the section you can call a unique DAL for every form.
Alternatvely if you know that there are certain varaible fileds that you always want to check, you can do the DAL from the XDD and error the form out way in adavance avoiding it being processed at all. In your example, your map the field and call it (without formatting) to check if its > 0.