Uniface 10: Discontinued Functionality

Some functionality is no longer available in Uniface 10.

The Buildozer service for building mobile apps

You can now develop a responsive mobile app using Uniface and use your choice of hybrid app framework to package it into a deployable mobile app. For more information, see Developing Mobile Apps.

Classic deployment mode

Uniface itself, and the applications you build with Uniface, are now delivered as deployment archives (.uar). USYSANA.TEXT and ULANA.DICT tables have been removed from the Repository and .dol and .urr files can no longer be generated.


Projects can be used to organize components into logical modules or subsystems.

Component Integration Workspace

It is no longer possible to model signatures and component integration. It is still possible to define third- party signatures in the Signature Editor.

Application Generation functionality

In Uniface 8 and 9, it was possible to automatically generate components based on component subtype entities.

Uniface Deployment Environment

This tool was also known as the Runtime Administration Environment (URMA),

Permissions System

The Permissions system was used to control access to objects in a shared Uniface Repository.

Repository Viewer

The Repository Viewer was used to view and report cross-reference data, which identifies where objects are used and referenced in application sources. The Repository Viewer is not available in Uniface 10, but the facilities for generating cross-reference data are still available, as are the $ude ProcScript functions for creating your own cross-reference utilities. For more formation, see Cross-Reference Data and Facilities.

The following platforms and databases are no longer supported

  • Platforms

    • OpenVMS
    • HP-UX Unix
    • Windows Mobile / Windows CE
  • Databases

    • RDB
    • RMS
    • SolidDB
    • Embedded Database, DB2 Embedded, Microsoft SQL Server Mobile, Oracle Lite