- Excel Desktop Client new !
Our new Excel Desktop Client interface (or simply Excel Client) is a temporary Excel spreadsheet instance running locally on a User's desktop with database-persistent named ranges.
An Excel Client enabled EASAP allows rapid creation, development and deployment of a powerful, enterprise Excel application with a familiar user experience.
An Excel Client derives its form and function directly from a master spreadsheet and thus requires very minimal Author effort from a first prototype to a final production release.
For a comparison of the Excel Client and browser-based user interfaces, read Excel Client vs. in-browser EASAP.
CASE VIEWER is a new EASAP object to search for and select a 'case' record from a database table.
A FILTER may use case data or metadata to restrict which cases are visible in a CASE VIEWER.
An EXTERNAL FILTER has the same role as FILTER but more flexibility allowing arbitrary SQL on Author specified database tables.
To create a new case or once a case is selected a DATABASE TO EXCEL DESKTOP ACTION will retrieve the case record and initialize a live Excel Client session to edit and analyze the record within a temporary Excel instance.
A User completes the analysis in Excel and then clicks the EASA→Save button on the EASA Ribbon to save the updated case record from an Excel Client back into a database.
An EXCEL SAVED EVENT may trigger other ACTION's in an EASAP.
SET CASE STATUS may update a case record status field, perhaps after some other validation or management approval.
For more details and instructions see EDC → Excel Desktop Client.
Each of the above objects allow Colspan: and Rowspan: options for their Child GUI objects, below:
|IMAGE||TABBED PANE||SUB PANE|
|LAYOUT PANEL||SPACER||DATA TABLE|
|CASE VIEWER||TABBED PANE LIST|
Each of the following objects have a Style to Child: parameter:
Set Style to Child:→YES to apply the Parent→Style: settings to any Child GUI object(s) as long as Child→Style: is left blank.
The EASAP Builder uses a 64-bit Java Virtual Machine by default
Larger and more computationally intensive Excel cell dependency tree calculations are now supported.
The Builder now uses Jacob as the Java↔Excel bridge by default.
When EASA 6.0 is run in application mode there is no potential for harmful interaction with a local Excel Server running Jacob.
The new implementation is faster, more scalable and 'Excel thread safe'.