LOL. It is working now. I must have had some very minor typo or something. After looking at the XSL file associated with the manifest file, I suspected that it should work.
The data field is in the HistoryItems node (the repeating node/section) in the XDocument.DOM. The rule's context is the repeating node and therefore it works as I wanted it. I might say that a person could edit the rule and reference any of the sibling nodes and do something a lot more sophisticated.
Thank you for the reply.
P.S. My apologies for the following rather verbose commentary:
I am especially enjoying working with my InfoPath form. I am using more than 1500 lines of vbScript to manipulate the data and behavior of the work flow.
My form is a request for a new item in our content management system with a workflow that goes from the requestor to Admin and two more levels of approval. It can be rejected at any point in the workflow and go back to the requestor to be restarted.
I use a couple of SharePoint lists for setting some form behavioral parameters and names of approvers and also for some dropdown lists.
By way of the underlying vbScript, the form can be moved/republished at either of two SharePoint libraries (development or production) and the form will automatically know which site it comes from and perform the Save, Email and other such tasks in different ways.
I can open it from the development site or from locally saved exported files (manifest.xsf, template.xml, vbscript.vbs, etc.) for testing and then republish it to the production site when development is complete.
Thank you, again.
Regards, Jim