"This is truly amazing.
It is hard to imagine what else you could have provided that is not already
present."
"I don't understand why ASG did not tell
us about RoAccess when they were doing their sales presentations.
They knew we could not meet the schedule using their WEB Access.
I'm
sure glad we knew someone that happened to be using RoAccess."
"What amazes me is that it seems every
time we ask if RoAccess has a capability, the answer is yes."
"I can't believe how much we've gotten
done in two days."
Once you start seeing all the
capability that RoAccess delivers to you, you can focus on completing your
Repository. Too often with Rochade products, you spend your
time learning the intricacies of the product. With RoAccess, you
spend your time on your Repository development. After all, isn't
that why you buy tools? To make your life easier?
"I find it hard to believe that you
can be running RoAccess in one window in MSIE, and then do a FILE/NEW /WINDOW
and continue in both windows! From my experience, each window has
a session key, and session variables are tied to that key. If you
do a FILE/NEW/WINDOW, MSIE opens the new window with a copy of what is
running. That means you have the SAME session key in both windows!
The two different windows will start storing their own data with the same
key, overwriting what the other window is writing! The application
usually then starts crashing. I've seen this in several WEB applications
we have. The software vendors just say, "Don't do that. Only have
one window open or start another window from scratch, doing the login and
navigating from the top to wherever you need to be so you can have a separate
session key". But not RoAccess. I can open as many RoAccess windows
as I want whenever I want, and RoAccess never gets confused? This
is magic to me."
You will many times find that
you might need 5 or 10 windows up simultaneously all accessing different
info or even different Subject Areas or databases. With RoAccess,
that is very easy. Just do it, and RoAccess handles the details.
"I'm surprised that I can do
the presentation to the customer showing them how RoAccess can navigate
the Repository when I only started to use it yesterday. If I can
do this with no real training, then the customer can too."
After being on the market for
5 years, RoAccess has become so easy to use, that people pick it in a matter
of minutes. This didn't just happen. We had hundreds of user
feedbacks on how to improve the functionality and usability of the product,
and we listened!
"How can you add an application like
Document Management to standard RoAccess and not have to change a single
line of RoAccess code? This is important to us because any custom
changes would require documentation and subsequent special support.
Being able to automatically save every prior version of a document,
and toggling the SHOW/HIDE Versions, and have special buttons appear when
appropriate is obviously new code. RoAccess' ability to add new
applications with merely "configuration file entries" is really impressive."
The appearance of several buttons
on different standard RoAccess screens only when they were appropriate,
the code to display or hide Document Versions in the Item listing screen
and the code to automatically Document Version of blobs required absolutely
ZERO changes to RoAccess. This "Document Management user application"
was just an "add-on". Quick to create, and easy to support.
The RoAccess "configuration file" is a technical marvel that allows you
to provide customizations that you probably never thought possible.
I can change the wording on every screen to
what our customers use? Like not using ItemType, Items, RIM, Subject Areas
and such? And not have new RoAccess releases overwrite our custom
wording and labeling?
No one on the planet, except Rochade,
uses these types of terms. So for the typical business user, these
terms will have no meaning at all. RoAccess lets you customize the
wording on every screen to be what your users are used to. You can
change one word on a screen, or every phrase and button on the screen.
And subsequent updates or releases of RoAccess will not overwrite your
changes.
You mean I can see "Cobol Programs" instead
of SCN/PROGRAM everywhere in the Repository. That's good.
With RoAccess you can have "user
friendly ItemType names", instead of the cryptic, upper case only, 32 character
max internal ItemType names. You can also define which users see
them and which see the internal names, like perhaps DBAs.
"The Rochade FOCUS scanner needs a change,
and we have to get a 'C' compiler so we can make a change. So we're
waiting until we get the compiler in. This is wasting time. If
that scanner were written in RoAccess, we'd already be through."
RoAccess does not require compiling
and linking, because it uses scripting technologies. Also RoAccess
does not require WEB servers. It can create standalone applications,
like scanners. Making a changes involves only making changes to text
files, and hence no other tools or costs are needed. You always have
everything on hand to do whatever you need with no additional costs or
installations of other software products. Also if that FOCUS scanner
were written in RoAccess, it would run on ANY platform, not just the one
it was compiled on (because RoAccess does not need compiling!).
"For the Document Storage and user delivery,
I'm surprised RoAccess gives us the option to store the files in Rochade,
on shared drives, using our WEB file delivery system or custom file storage
systems. We don't want to have multiple copies of files, because
if the primary file changes, the copy will be out of date. Here we
can just keep on accessing our file storage systems as we did before, but
it all goes through the Repository."
Large companies already have document
storage systems on Unix, Windows shared drives, accessed by WEB front ends
or specialized document management products. They don't want
to change the way they do things if it isn't necessary because of the cost
and change that would be necessary. They also only want to have ONE
copy of each document. This is why RoAccess is set up to handle a
wide variety of file storage and delivery mechanisms.
"That's really nice. Having MSIE crash
in front of the customer during a demo would be bad. I'm glad you
already knew of MSIE's problems and had options to handle it."
When downloading documents from
any WEB server directly to the desktop, under many conditions relating
to the version of MSIE and the service pack of the operating system (like
NT 4.0 or Windows 2000 Server), MSIE will not communicate properly with
the helper applications, like MSWord or Excel, and the system will indeed
hang, sometimes requiring a reboot. This would be very irritating
to your customers. To handle this precise problem we have configuration
file entries to compensate for MSIE's problems, so the document gets displayed
in the correct program properly. These are the things RoAccess picked
up over the years having so many customers on so many platforms and versions
of browsers.
"This is really cool."
We heard this a lot. When
people start using RoAccess it's fun to watch. They immediately
start thinking of all the things they can do with their Repository, and
that really IS exciting.
"Can I really run RoAccess on my notebook?"
Being able to develop Rochade
applications or do RIM development at home of off-site (like at an airport)
on your notebook computer is really nice. It gives you so many options.
There is no additional cost for a RoAccess WEB server on your notebook.
Every one of your developers can have one. Also you don't have
to worry about getting a WEB server that needs a Java run time environment
or JSP engine and making sure the versions match. RoAccess doesn't
require any of these. However, a Rochade server for your notebook
may cost you, or you may have to "make a deal" with ASG because your Rochade
license is only good for one platform (like NT or Unix or mainframe).
You can run RoAccess on all your machines for no additional cost.
RoAccess knows that when you are happy, you tell your friends, and they
purchase RoAccess, too. This is exactly how the Department of Defense
found out about RoAccess. So we make sure we do the things that
helps you be successful. In the long run, that helps us, too.
|
