Hi, new to livecycle, question if I may:I am looking to find an example that I can model in our form. Our form needs to take a "last name" string, for example, and pass that string to a mainframe where our customer data resides. The mainframe should return all of the customers with that last name in...

Paul, thank you for your answer. My understanding is that schemas are also needed in workbench when designing your workflow - using process variables and form data and such. I understand that it's much easier to drill down to the particular fields that you need by binding the form to a schema. True?

Our instructor advised us to consider using a single master schema that will define our company data. However I have also seen two other ways schemas are used. Which of the three ways below is the best practice, or is there even another alternative? --Master schema--Schema per form--Schema per form ...

Greetings, we are in the early stages of deploying livecycle within our company. One of the things I have noticed is that we haven't put a strong case together for a "livecycle server administrator" role. As a result, the following questions have surfaced:1) What are the primary roles of an administ...

We are building forms in designer that were formerly in Lotus Notes. Our clients have become accustomed to having "routing history" and "modification history" fields as a document goes through its workflow. Is this information best being populated as a process variable using the set value service? O...

If a schema can be used to build out a form, or, if there is a common schema is used across multiple forms, is there a need for fragments?

I am new to livecycle, so please bear with me ;-)My question is about schemas. Since my company does not have a "master" schema, we will be starting from scratch. How does one begin? Do you create a schema first in a tool such as xmlSpy and then use that to create forms and bind the data? Or does on...