Interface with IDX Flowcast

We have.

The interfaces are straight forward and relatively easy to install.

My only complaint is that you would think that they get paid for each transaction they send out cause they’ll dump on you.

While the users are running through the screens, IDX(GE) can’t tell whether the information they file is different from what’s already on the database. So for everytime someone hits F10, an A08 or A31 gets generated. We also have the IM module so we get an inssurance update message in addition to the demographic update.

There are A LOT of duplicate transactions that come out of that system!

-mh

We can confirm the excess A08’s and A31’s.  That’s true here, too.  We set up a batch interface, so that batch jobs send to it and we lower the priority going through the engine.  Additionally, only certain IDX userid’s can be used to run some of the jobs and we kill all transactions using those user id’s.

The only other “problem” is having to do what we call the IDX 2-step.  The interfaces have to come down and up in a particular order.  That is, the client always has to come down first and back up last.