How to add other documents to an Empower Fullfillment
Currently we have an Empower driver includes both empower and non-empower documents which impacts Empower performance. Is there a way to add documents to the Empower fulfillment path to reduce what is loaded into the empower editor and thus improve performance? For example, given Empower customer driver, is there a way to connect data to the Empower driver from the edit process to be used in fulfillment process, or will it require leveraging sorting and bundling or scripting to call PDF output files from the earlier edit application job?
0
Categories
- All Categories
- 123 Developer Announcements
- 54 Articles
- 156 General Questions
- 149 Thrust Services
- 57 Developer Hackathon
- 37 Thrust Studio
- 20.6K Analytics
- 4.2K AppWorks
- 9K Extended ECM
- 918 Core Messaging
- 84 Digital Asset Management
- 9.4K Documentum
- 33 eDOCS
- 190 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management
- 10 XM Fax
- Follow Categories
