×V5.1Ø
S |
A |
W |
WS |
|
|
ü |
|
SmartUI
SmartUI was introduced in version 5.1.1097. Based on our collaboration with Cerner, we developed a more robust way of scripting the user interface of Soarian Financials. This approach bypasses our traditional approach of working through the Document Object Model (DOM) to find elements based on their window, frame and attributes.
Cerner has backend API services that EMUE utilizes to access a library of controls on a given page in Soarian. The controls are identified by a single identifier we call the control array ID. These control IDs are mapped in our SmartName file. That means that SmartUI is only available by using SmartNames.
Benefits
Upgrades:
The main goal for this feature is to ease the burden of upgrades. The control array IDs are far less likely to change over different versions of Soarian unlike the element strings we have used in the past.
Speed:
Since we are not going through the DOM to locate elements there should be some performance improvements in your scripts. Keep in mind that EMUE will only run as fast as the hardware it is running on.
SmartName Enhancements:
SmartUI allowed us to map Soarian screens to SmartName screens. Finding the correct SmartName screen has never been easier. During script development EMUE can detect the current screen. While you are building a command in the editor you will be presented with a list of options for the screen you are viewing. The suggested options will be bold. EMUE must have opened Soarian and you must be logged in to get this functionality.
In this example, we are searching for a health professional. EMUE can detect this dialog and code completion will display the option to use on this screen.
|
|
Note: If you are using a SmartName that doesn't have a control array ID, EMUE will default to the element string.
See Also: