Hello Lori/Kevin,
As a potential workaround, in addition to Carolyn's suggestion of copying non-keyword values into a Worflow Property Bag, would be to use a "dummy" Unity Form and copying the non-keyword values using the Workflow action "Copy Property To/From Unity Form Field"
What you can do is create another Unity Form (a different Document Type, but possibly similar template to what you already have), but this time, the non-keyword field in the other Unity Form is an actual keyword field. You can then copy all the values from the original Unity Form that you will need for Document Composition (keyword and non-keyword) into this "dummy" Unity Form upon creation. Instead of generating the composed document using your orginal Unity Form, you will just generate from the "dummy" Unity Form where the values you need are in the keyword fields.
For Kevin, this is also helpful in your scenario of multiple Unity Forms. You can generate one "dummy" Unity Form" for all the Unity Forms that you would want to grab values from and generate your PDF document from the "dummy" Unity Form.
It might be a good idea to have a separate life cycle just for this dummy Unity Form to compose the document (since it's also a different Document Type). And you can have the "dummy" Unity Form deleted after the document has been generated siince you won't be needing it anymore.
I know it's a little tricky and a bit of an added work, but I hope this helps. If you have further questions, please feel free to let me know.
Regards,
Rance
