Comparing the ExpressAddin with the Workplace Application
Integration Toolkit
Implementation of the ExpressAddin differs from development
with the Workplace Application Integration Toolkit in the following ways:
- The ExpressAddin provides developers with a much simpler
method for accessing the Application Integration framework than the objects
in the Toolkit. Less code needs to be written, the standard FileNet Office
style of application behavior and GUI is more easily leveraged, and a much
more rapid third-party integration can be achieved. Conversely, while the
COM APIs in the Toolkit require more time to implement initially, they ultimately
allow for greater flexibility in controlling application behavior.
- The ExpressAddin offers some features that are not
available from the Toolkit, such as document tracking.
- The ExpressAddin coalesces various Application Integration
functionality into a single operation, whereas the Toolkit requires that the
commands which correspond to that functionality be stacked in order to achieve
the same behavior. For example, using the Checkin command from the Toolkit
requires that the code for the CheckoutList and the Checkin command be stacked
in order to obtain the desired result. However, when developing with the ExpressAddin,
once the component interfaces and basic event handlers are implemented, any
FileNet Application Integration command may be selected with no further coding
required.