As an example, most records management solutions use content organizer rules to route incoming records to a particular document library or folder so they can be associated with specific information policies and retention schedules. But configuring the content organizer requires that the site columns, content types, document libraries, folders and other components are constructed beforehand. The situation is even more challenging when working with target locations external to the site collection being configured.
Note: You can download the code for this solution here:
In this slide presentation, I show how InfoPath 2010 can be leveraged to reduce the complexity of records center configuration by capturing all of the required elements in one place, and then pushing them out in various ways, depending on your overall information architecture strategy.