January 2011 Archives
Clients commonly ask support why they need to confirm things like their application version or a wide variety of other environmental details whenever case is opened. I can understand why someone might be frustrated when they open a case with support and are requested to provide information that they had provided just a few weeks before when opening their last case, so why do we ask?
There is a very straightforward reason we ask for this information each time someone opens a case, and that is to ensure everyone is on the same page. A great deal can change in a few weeks, or even a few days, and heading down the wrong path because a support consultant is out of sync with a client's environment is in nobody's best interest. We want to ensure that when a support case is opened it is resolved as quickly as possible. Making sure that everyone has a clear understanding of the application and environment is an important first step.
This week we ran into an issue with a client who is using Safari on a MAC running OS X 10.6 as his desktop client when accessing Adobe LiveCycle. This particular issue resulted in the client not being able to properly render dynamic interactive forms as part of a process.
As it turns out there are some limitations when using either Adobe LiveCycle ES or ES2 in Safari. In particular you must run Safari 3.x or 4.x in 32-bit mode when using LiveCycle WorkSpace. To change Safari to 32-bit mode perform the following steps;
- Open the application folder
- Select the 'Safari' icon
- Select 'Get Info'
- Check 'Open in 32-bit mode'