Spend some time considering how you want to design your e-form repository hierarchy. For example, suppose you use two human resources (HR) e-form documents, and that you also use two purchasing department e-form documents. For business purposes, you might like to keep these forms stored in separate areas of your repository, subject to separate access permissions.

In your repository, you can create a repository path to a folder that contains a separate instances folder for each of your HR forms. For example:

You can also create a repository path to a folder that contains instances folders for your purchasing department forms. For example:

In this case, you would need to create four different e-form environments, two describing the path to each of the HR e-form instance folders, and two others describing the path to each of the purchasing e-form instance folders. The environments will be identical except for the path to the e-form folders, which will be different for each environment. You then deploy the four environments to the Integration Server host.

When you create your business process models, you will configure the receive step for each process to monitor the related e-form instances folder, which you select from the list of instances folders from the e-form environment you deployed to the Integration Server host.

When you plan your repository structure, you should also take e-form environment creation and deployment issues into account; for more information, see Configuring and Deploying an E-form Environment, especially E-form Environment Considerations.