View source for RPC HELP M Entry In RP File Documenting

[[RPC_Broker_Help| RPC Broker Help Home]]
<h2>Documenting RPCs</h2>
Each individual application development team is responsible for identifying and providing documentation for all object components, classes, and remote procedure calls they create. Other developers using these components will need to know what RPCs are called because they will need to register them with their applications.
	
RPCs should be documented in the DESCRIPTION field (#1) in the REMOTE PROCEDURE file (#8994) for those RPCs installed on your system. This gives you the capability of generating a catalog of RPCs from File #8994.

<h3>Delphi Component Library and Sample RPCs</h3>
In the future, the VistA Data Systems & Integration (VDSI) unit of VistA System Design & Development (SD&D) will make available a corporate library of object components, classes, and remote procedure calls that are in use and available to the development community at large. The essential benefit of this library is the promotion of object re-use, thereby enhancing development productivity, application consistency, and quality assurance. Therefore, it will contain a wide variety of components, classes, and RPCs from many VistA software applications.
	
The immediate intent is to classify and catalog all of the object classes in use (including the standard Delphi classes), and to make the catalog available to all interested parties via the VistA System Design & Development (SD&D) Home Page: http://vista.med.va.gov/index.asp