Host Integrator fulfills SQL queries from client applications by navigating to the pertinent entities in a host application that contain the table data and either reading, modifying, or deleting the data. A procedure's definition must specify all entities and recordsets that contain table data.
In addition to defining the entities and recordsets that contain table data, you can also define branching entities, which give a procedure some flexibility when traversing through a host application, as well as error entities, which you can use to trap errors in a procedure.
You must add every entity to a procedure that contains the attributes and/or recordset field that the procedure will be able to query.
Learn more about inserting entities to procedures.
Recordsets are areas on an entity that contain dynamically changing information, usually scrolling sets of data that are a result of a data fetch.
Learn more about inserting a recordset to a procedure.
Use branch entities in procedures when an operation has alternate entity destinations. There are times when traversal is not deterministic, for example, when an operation has alternate destinations defined. These alternate destinations can be added as branch entities in a procedure. When the operation is executed at runtime, the path the procedure takes is determined by which branch entity is recognized once the operation completes. If none of the branch entities is recognized, the procedure fails.
Learn more about inserting branch entities to procedures.
Error Entities are screens containing patterns that tell you an error has occurred in the procedure. You can define error entities by purposely entering bad data in a host application and capturing the resulting screen as an entity. Adding one or more error entities to a procedure is a good way to build error checking into your model.
Learn more about inserting error entities to procedures.