Agentry Features

New or changed features for Agentry development.

User Lockout After Failed Login Attempts

Within a mobile application, you can define a maximum number of failed login attempts on the client and to then define the required action to take when that maximum is reached.

Documented in:
  • Security > Overview of Security Features in Agentry
  • Developer Guide: Agentry Language Reference > Configuring User Lockout for Failed Login Attempts

Securing Attachments on iOS Devices

The Agentry Mobile Platform lets you attach documents to objects and to both download and upload them to and from the client application. When implemented for environments in which iOS devices are used, the default storage location of the attached documents on the client device results in those documents being accessible to the device via iTunes. A simple change to the storage location of the attached documents, made in the application project using the Agentry Editor, prevents these documents from being accessible through iTunes.

Documented in:
  • Security > Overview of Security Features in Agentry
  • Developer Guide: Agentry Language Reference > Securing Attachments on iOS Client Devices

Client-Side Data Encryption

When defining an  Agentry client  application, you can use the Agentry Editor to set whether to encrypt data that is stored locally in the application definition. An encrypted client encrypts all production data and application data stored on the client device.

Documented in:
  • Security > Overview of Security Features in Agentry
  • Developer Guide: Agentry Language Reference > Defining Client-Side Data Encryption

Public/Private Key Length Configuration

During initial synchronization between the Agentry client and Agentry server, a public key is provided by the server to the client. This key is a part of the public/private key pair used by the Agentry server and Agentry client to secure communications, and to encrypt data on the Agentry client. Security requirements for many environments dictate an increase in the length of this public/private key pair from the default length of 512. To do this, modify the configuration settings for the Agentry server and, for existing live implementations, also reset the Agentry client and force the Agentry server to generate a new key of a greater length.

Documented in: Security > Overview of Security Features in Agentry and Configuring the Agentry Server Public/Private Key Length .

Agentry Editor

New features supported by Agentry Editor for 2.3 SP03:
  • The Agentry Editor Visual Screen Editor (VSE) now supports Windows Presentation Foundation (WPF), which is the default mode for Windows Platform screens. The WPF-based client runs on Windows 7 and Windows 8 Professional, whereas the legacy Windows client runs on Windows XP. This works the same as Win32 screens, in that they draw to the same size as defined by the platform. You can continue to access the Win32 view as Windows XP. WPF supports these screen resolutions: 1024 x 600, 1280 x 1024, 1366 x 768, 640 x 480, and 800 x 600.

  • VSE supports these Win32 screen resolutions: 1024 x 600, 1280 x 1024, 1366 x 768, 640 x 480, and 800 x 600.

  • VSE lets you move controls up and down, and across columns with a VSE screen using drag and drop. For example, if the user drags a control over another, the other control moves down in the screen, assuming there is room available. This functionality is available for action buttons, toolbar buttons, and columns, but you cannot resize and align the controls, handle hidden controls and fields, and autoscroll while dragging a control.

  • VSE supports the calendar view component for iPad. VSE can display the current month, with no interaction for each platform. The Android and iOS control is available for tablet-sized and phone-sized screens.

  • Teamshare improvements in the Agentry Editor:
    • When a user commits changes, the version control number is updated in Share.ini.
    • If files associated with a Teamshare version are removed, the Compare feature allows you to select an export file for comparison.
    • Teamshare supports updates when different developers have added different platforms to the same screen set.
  • Teamshare performance improvements in the Agentry Editor:
    • To reduce network transfers, all repository files are now zipped together, and revisions are cached locally.
    • Teamshare changes now update the version number both in the share and within the project.
    • Issues that prevented export file comparison when the share was corrupted or manually changed have been corrected.

Agentry Client

New features supported by the Agentry Client for 2.3 SP03 (available in both Android and iOS, unless otherwise specified):
  • Users can change passwords after logging on.

  • Users can sort on a column in a list control.

  • Users can reorder columns in a list view, and save the changes in user preferences.

  • The client user interface now works with all navigation features in the Advanced wizard screens.

  • Branding support has been added for the demo databases; the branding script now picks up the product's branded databases.

  • (Android only) The Android client can now lock the application orientation (landscape or portrait) through branding.

  • Agentry WPF (Windows 8 Desktop) Client.