Altova MobileTogether 8.0

Released: Jun 1, 2022

Aggiornamenti in 8.0

Funzionalità

  • Added the option to create a no-code database app with Altova RecordsManager - Altova RecordsManager is a brand new solution for creating custom database apps in MobileTogether.
    • Starting with this release, when you open MobileTogether Designer you will have the option to create a classic MobileTogether solution, or start with Altova RecordsManager. RecordsManager has a visual interface for quickly building business database apps for desktop and mobile users.
    • One of the biggest advantages of RecordsManager is that app creators don’t need to build the database backend themselves. They simply focus on the objects they want to model, and RecordsManager takes care of the rest. This saves an incredible amount of time and work and allows system administrators or developers of all skill levels to easily create effective apps.
  • Added a new Database Wizard and support for hierarchical DB read/write - Previously, working with backend data in relational databases required quite a bit of hand-written SQL work to perform commonly required tasks. As such, saving the same data back to the database was also complicated. This release lets developers more readily build a query that returns hierarchical data and write the data back in hierarchical form.
    • The new Database Wizard provides an easy way to build SELECT statements visually, and any parameter to the SQL query can now be directly expressed using an XPath statement, i.e., there is no longer a need to explicitly declare parameters.
    • The Database Wizard also lets developers add tables connected via foreign keys to the result – all in a single step. This means an entire hierarchy can be retrieved at once.
    • Any changes made during app execution will be intelligently written back to the relationally linked database at once. When saving hierarchical data, the app developer can choose whether to save modifications only or to replace all the data for the current record. This decision can be made on each level independently. Data replacement is the preferred option when multiple users are allowed to edit the same record at the same time.
  • Added support for modularization
    • Added the ability to modularize the app design file so that multiple developers can work on the same project. This also adds the ability to reuse parts of projects in other projects.
    • To facilitate refactoring of existing projects, there is a new option to extract part of an existing project as a new sub project. This enables a wide range of components that are defined in a project to be re-used across multiple projects. One subproject can include another subproject.
    • A new Refactor menu provides options for working with subprojects. Subprojects included in a particular design file are displayed in the Files pane.
    • Modularization has also been implemented with a new Modules pane, which organizes design components into logical parts.
    • The Modules pane provides a single location for managing modules, which are grouped automatically based on their names. This way, you can tell at a glance which functions and actions go with which pages, and you can navigate to them automatically from the modules listing. Modules are organized by name using dot notation ( i.e., ModuleName.ComponentName, etc.).
    • You can move unassigned items into modules by renaming them. Or, you can move or re-assign items manually, and MobileTogether Designer will automatically rename them accordingly and update all references across the project.
    • Adding a custom color to a module highlights the module items in that color across the project for easy identification.
    • When a subproject is extracted from a project, all components of the project will, by default, be exported to the subproject. If you want to export only a subset of components, then you can group them in a module and set the Export property of the module to either Exported or Not Exported, as appropriate.
    • The Modules pane automatically organizes large projects and helps you find things more easily to immediately understand how and where each item is used. Items that belong together are grouped together logically, making the entire project easier to understand. This is also extremely helpful when a project is inherited or worked on by multiple developers.
  • Server Libraries
    • Server Libraries are a new type of MobileTogether design file. When an app or solution utilizes a Server Library, the library can be exchanged at any time without needing to redeploy the app. This allows for much quicker roll-out of app updates and changes, especially for complied apps, which no longer need to be recompiled and sent through the app store approval process.
    • A Server Library is a MobileTogether design file that contains one or more Action Groups, and its functionality is limited to processing these Action Groups. At runtime, a solution can send a call to a Server Library with or without parameters. The Server Library processes the specified Action Group and returns the result to the calling solution.
    • Advantages of using Sever Libraries include:
      • Since its purpose is limited, a Server Library is smaller and simpler than the main solution and can be changed easily and quickly.
      • The modified external data structure can be processed entirely within the Server Library so that data is retrieved from the external data structure and sent to the main solution in a structure that the main solution uses.
      • The modified Server Library can be deployed to the server in a simple deployment procedure. The main solution, which is also deployed on the server, does not need to be modified in any way. This also means apps and solutions already downloaded to clients won’t need to be updated.
    • Use of Server Libraries requires MobileTogether Server Advanced Edition.
  • Added the ability to restrict logging in MobileTogether Designer - When simulating an app in MobileTogether Designer, it is now possible to restrict logging functionality to reporting only errors. This allows the app to function much as it will in the real world, giving developers a better idea of how fast their app or enterprise solution will perform.
  • Server-side solution files - It is now possible to add a list of files to be deployed with a MobileTogether design to the MobileTogether Server directly in the design file itself, instead of copying the files manually. On deployment, the developer can choose to overwrite the files if they already exist on the server. Server-side solution files are specified on the Files tab.
  • Added a new lock/unlock Action - This new Action enables clients running a solution to be locked from access to the MobileTogether Server while critical server-side changes are being carried out on the Server. After that, the developer can simply unlock server access and let clients continue their work or require all running clients to restart. Please note that this Action requires MobileTogether Server Advanced Edition.
  • Added a new Action to rename file/folder - This Action renames the selected file/folder on the client/server when the Action is executed.
  • Added the option to move deleted files to the Trash - The Delete File/Folder Action has been extended with the option to move deleted items to the Recycle Bin/Trash for systems that support this. This option is only available for the Server file system.
  • Added a new option to switch theme via an Action - MobileTogether apps and solutions support switching themes, such as between dark and light displays, either defined during development in the project settings or based on the device’s default setting. Now there is a new Action for changing themes that will allow the end user to select the desired theme inside the app itself.
  • Comments in page sources - MobileTogether developers can now add comments for elements and attributes in page sources. This is very helpful for efficient app maintenance, especially within large projects.
  • Switching database connection during execution - It is now possible to choose the database file behind your app at runtime using a new Action called DB Switch Connection. This gives the developer the option to let the end user decide which database to use. The connection can be changed as many times as required. This feature requires MobileTogether Server Advanced Edition.
  • Added support for additional database versions - This release adds support for the newest versions of several databases, including:
    • IBM DB2 11.5.7.
    • MySQL 8.0.28.
    • MariaDB 10.6.5.
    • SQLite 3.37.
    • PostgreSQL 14.1.
  • Added support for Android 12 and Apple iOS 15 - Apps built in MobileTogether can take advantage of all the features and functionality in the latest versions of the Android and iOS operating systems.
  • Added support for Microsoft Windows 11 - Both MobileTogether Designer and MobileTogether Server now support running on Windows 11.
  • Added support for Apple macOS Big Sur, macOS Monterey, and Linux Debian 11 (MobileTogether Server) - MobileTogether Server is now available for macOS Big Sur, macOS Monterey, and Linux Debian 11 in addition to previous versions.