If you want to use Workflow Property placeholders, you have to take into account Document Composition user session, and possible later (asynchronous) sessions when a document is actually created. To facilitate the choice between various options, use the following.
Non-automated composition (Use Automated Document Generation unchecked) supports:
- Session Property Bag
- Scoped Property Bag
- Persistent Property Bag
Synchronous automated composition (Use Automated Document Generation checked, Synchronous Processing selected) supports:
- Session Property Bag
- Scoped Property Bag
- Persistent Property Bag
Asynchronous automated composition (Use Automated Document Generation checked, Asynchronous Processing selected) supports:
- Persistent Property Bag
Asynchronous automated composition must use the Persistent Property Bag in order for Document Composition to pick up Workflow Properties during the composition process. This is because asynchronous automated composition works in conjunction with the Unity Scheduler, which processes the contents at a later time. The Unity Scheduler will not use the same Session as the User who made the request and the composition will actually take place after the execution of the Compose Document Action, meaning that no other Property Bag option is available.