- Excel Desktop Client new !
EASA 6.0 contains two technologies that allow an Excel spreadsheet to be deployed into production as an enterprise application.
A User may interact with Excel via two very different interfaces,
To determine which technology to use, an Author should consider the four P's below:
Below we briefly compare the two technologies in these four domains,
|Excel Client||EASAP in browser|
|1.||Very little Author effort to deploy a prototype with full Excel functionality and the possibility of immediate release to production||Initially run the Excel Range Wizard then make manual adjustment for GUI objects, output and 'results' documents. Not every Excel feature is supported, see Supported Excel functionality for an in-browser EASAP.|
|2.||Automatic and auditable database persistence in the cases table||DATABASE READ's and WRITE's require SQL code and testing.|
|Complete flexibility about how data is stored.|
|3.||Local Excel Client instance performs at full native speed within a single Excel process.||Multiple Excel processes in an Excel Server may create a resource bottleneck. RAM and CPU requirements add to production costs.|
|A supported version of Microsoft Excel must be installed on any potential User's local machine.||A supported version of Microsoft Excel is installed centrally on an Excel Server and shared by many simultaneous User's.|
|Excel is not supported for mobile phones.||A mobile phone browser is a valid EASAP interface.|
|4.||Data is erased upon close, macros and formulae can be hidden with VBA||By default, no spreadsheet intellectual property is exposed.|
|Security in Excel is limited by the strength of protection that Excel provides.||A remote Excel Server provides no direct User access to a spreadsheet, an Author explicitly specifies every cell to be linked to an EASAP GUI object.|
The diagram below demonstrates this functionality.