BICs are primarily used to provide a means of automating business processes in a flow. After the BIC is registered with the local iteration of the EPX Application Server, you can use that BIC any number of times in any number of flows. For more information on how to register BICs, refer to the Administration guide.
Like participants, BICs can create, receive, and modify work items; return work items to the flow; or interface with external systems. BICs can also:
listen for specific Application Server events and take action accordingly
make calls to other BICs
make calls to external systems
call the public API of the Application Server
When a BIC checks in with an iteration of the EPX Application Server, it indicates what event subjects it is interested in listening for. When a server event occurs that matches one of the subjects, the server notifies the BIC by making a callback. For instance, a BIC would typically need to be notified when a work item has arrived at an activity in a process flow in which the BIC is the assigned actor. It is important to note that when a participant sends a work item to a BIC, the participant does not experience any wait time while the BIC processes its events.
BICs interface EPX to external systems using files, messages, or public interfaces. For more information about a specific BIC, refer either to that BIC’s guide or online help.
Note: Online help becomes available for a BIC After the BIC has been registered.