>>>I've never seen anything released even *close* to as buggy as this system is...so, we're back to the old hardcopy-method to get our tasks done.
>>
>>Scary... one question - is it PeopleSoft or a VAR that is implementing the client-side app(s) (which is where I assume you're seeing the problems)?
>
>We have a custom client version of the generic financial app, done by onsite Peoplesoft developers. I think the DB/server side is still generic. My hunch is that they committed to a deadline for the client-side, and had to get the Procurement part of the app up by a certain recent date or lose some big contract bucks. They chose to put the app up, and take the consequences of it not working, and try to repair the bugs while the app is in active use (or non-use, as the case is :). I don't think they've implemented the Payroll part of it yet.
>
>They may get away with it, if they can fix the worst bugs in our spending off-season, which is from now until about October. I knew the app was buggy from the training, so I wasn't surprised when it crashed on me - but I'll tell you, my chief manager was absolutely furious today. He spent more than 1/2 hour entering detailed financial data, and lost it all when the app crashed (I did warn him about it, but he was still impressed by the great sales pitch they put on). Anyway, you should've seen the email he sent to the Peoplesoft Team :)

This sort of thing must make companies like PeopleSoft cringe. It's a classic example of the old observation: if you get good service, on average you tell 1 other person about it. If you get bad service, on average you tell 4 or 5 other people about it.

Although nowadays, with the Internet, online forums, etc. it's more like 50 or 1,000.