by
benW » Wed Jun 20, 2012 6:18 pm
Hi,
Interestingly, it appears Waters are working on mobile apps for their Empower software… perhaps not such a bad choice?
Whilst I agree with some of Unmgvar’s post earlier – mostly that you need a very good trainer for Empower, some points are not so accurate…
Oracle is good, but expensive to purchase and complex to maintain.
There are no additional costs for the Oracle database with Empower as the Oracle database is embedded in Empower as standard and preconfigured by the installer (therefore not complex to maintain). However you could use your own Oracle license and configure it to suit your enterprise environment – this has made it very powerful for larger enterprise sites.
also empower has only recently made the effort to move to citrix.
Not correct, as Empower has been supported on Citrix for over ten years!
oracle tables, and empower data is in there also. so big labs actually waste time re-allocating table space to the different projects as they get filled.
Empower data is not stored in the database and does not contribute to filling up the projects. The metadata is stored in the database. The behaviour of projects constantly reaching their quota limit is at the hands of the project administrator and how the projects were initially created. Some administrators use project quota as a way of limiting project size and agreed, this is very disruptive and not to be recommended.
the most annoying bug ever from millenium to empower is the password login window.
for every single opened window you need to retype the password, just because.
This is not a bug, but the consequence of how your system policies where configured. Your system policies were set to lock inactive windows after a set number of minutes period of inactivity (or the user chose to do this when closing down) and so you needed to unlock them when you came back.
To accommodate for users that did not like the multiple windows of Millennium, Waters created the QuickStart single window interface - available as standard in Empower.
but you still wasted the time for that second mouse click.
Actually for one fix, I believe an additional mouse click was removed due to the amount of extra time it would add to all users' workflow
Just thought I would set the record straight