Liquid UI - WS Reference Library

1.2 Architecture and Deployment

Workbench is a development tool and as such, it is used to create the scripts that you will deploy to your Liquid UI environment. The architecture of how Workbench fits into the various Liquid UI deployments is shown below.

The way Workbench functions is that you will record the transactions directly in SAP and then generate the scripts needed for each individual implementation from included script templates. Once generated, these scripts can then be stored as desired, save in the case of Offline. Offline scripts must be stored in the actual device. Once generated, the Workbench scripts can be used with the various Synactive solutions, as follows:

Standard scripts

Typically used with SAPGUI in a direct connection where the local system communicates directly with SAP and the scripts reside on the local system itself.

Excel scripts

Used with SAPGUI and Microsoft Excel spreadsheets to perform bulk data transfers from the spreadsheets to SAP. As is the case with Standard, these scripts require a direct connection to SAP.

PDF scripts

These are used to perform data transfers from PDF forms or from HTML web forms to SAP through Web services. These scripts require the use of GuiXT Web Server.

Offline scripts

There are two different types of Offline scripts that Workbench can generate. In order to successfully execute a data transfer between an Offline device and a SAP application server, both types are needed. They are explained as follows.

  • Offline Synchronization scripts: Used on the GuiXT Server, these scripts execute the transfer of data between the GuiXT Server and SAP.
  • Offline UI scripts: These are used to paint the Offline upload and download screens and are used to transfer data between the device and the GuiXT Server.
Access scripts

These are used to paint screens on the Access smartphone client. As Access also communicates with SAP through a Web-based interface, it requires the use of the Web Server.

The Workbench has as its core the same WS platform that drives all of Synactive's next generation products. However, as described earlier in this document, Workbench in combination with WS Office gives SAP users the ability to perform mass data uploads by means of Excel spreadsheets or PDF forms. In addition, WS Office brings to SAP users the power of Microsoft Office tools such as spell-checking.


The deployment of Workbench is the same regardless of what type of scripts the user wishes to generate. In all cases, the Workbench should be installed on the user's local system. However, in the execution of the generated scripts, there is a difference in how the functionality is implemented. In order to execute the Excel and standard script functionality, no components are necessary to save for SAP and the WSOffice.dll. The WS Office extension for WS communicates by way of ActiveX protocols and therefore once the WSOffice.dll is installed on the user's computer, data integration between Excel and SAP is enabled. Scripts can also be deployed to a Windows-based mobile device via the use of GuiXT Server.

However, if you want to do PDF data entry, to create Offline scripts or to deploy Access scripts to smartphones or tablets, additional components are necessary. On the GuiXT side, this component is the GuiXT Web Server for PDF and Access deployments. For Offline deployments, the Liquid UI Server is required, as well as the GuiXT Mobile client. The Liquid UI Web Server is required in order to enable the POST-ing of PDF forms, whether these forms are created in Adobe's PDF products or a third-party solution. For instructions on installing and configuring the Web Server, please consult the Web Server page. Users must have either Adobe Acrobat Pro 9.0 or above (including Adobe LiveCycle Designer) in order to create the PDF forms. The Web Server is also required for the use of Access scripts on smartphones of tablets.

For using the scripts generated from the Offline and Access templates, users will need to have Synactive's Offline or Access solution deployed. Please consult the Offline and Access documentation for additional information on using these solutions. Offline requires the use of Synactive's Liquid UI Server. Liquid UI Access, like the PDF forms generated from the PDF template, requires the use of Synactive's Web Server.