Hello:
I work for a governmental agency which is converting all their forms, which are generated using two tools; SAS and IBM's Script. This encompasses over 25K forms, the majority of which are generated in nightly batch files. I'm jumping in ahead of the team to navigate some of the information out here and dig out what is pertinent to our project and can be shared with the team to start the learning curve.
I have browsed around the Adobe Website and identified some key tutorials, but am also seeking any references to individual blogs from the "ground" perspective:
- Business Users - The business users will own the content. At this time, they have no concept of how a document generaton system works. What is the best resource to which they should refer? I found this on the Adobe Website: http://help.adobe.com/en_US/livecycle/9.0/designerHelp/index.htm?content=000007.html. Are there others?
- IT Team - The IT Team will consult with the business users to identify all the reusable fragments. This will be an arduous task given the number of forms and the breadth of the existing library and the limited resource pool whom can read the SAS and SCRIPT code.
- Best practices for optimal fragment library development.
- Our proof of concept will emcompass having the SAS and SCRIPT programs generate the XML output to be consumed by Adobe. There are lots of questions around how much of the conditional logic stays on the mainframe versus moves into Adobe. For the POC, I've suggested we be diligent to NOT move any of the logic to Adobe. We can, however, incorporate some of the field-level validation which doesn't rely on SOR data.
- I have encountered a lot of information about building an "application." I assume this has to do more with user-interactive forms. In our case, the number of forms which will require user interaction is less than 5%. Our work is more about merging with backend data during nightly batch files.
Grateful for gentle guidance on getting started.
Thank you!
DS
