Salesforce

Differences Between Magic xpa 3.2 and Magic xpa 3.3 (Magic xpa 4.x)

Printable View
« Go Back

Information

 
Created BySalesforce Service User
Approval Process StatusPublished
Objective
Description

Differences Between Magic xpa 3.2 and Magic xpa 3.3

Here are some prominent points by which Magic xpa 3.3 is different from Magic xpa 3.2:

New Functionality

  • You can now define the latest persistent data to which a form is compatible with, by using the new Persistent Form State Version property. If at runtime the persistent data is of a different version then this property value, the runtime persistent data will be removed. This is useful if you changed your program and you want to clear the user’s persistent data of that program.

  • Context Menu event – This event is raised when the right button of the mouse is clicked (before the context menu is displayed), or when the context menu key is pressed. You can use this event to hide the default Edit control context menu by setting the Propagate property to No.

  • The Browser control is now also supported for GUI Display forms.

  • You can set a different color for each row in a table using the Row BG Color table property. For this purpose, the Set Table Color property was renamed to Set Table BG Color and the Color property was renamed to BG Color. In addition, a Row option was added to the Set Table BG Color property.

  • In 3.3, two new functions CXMDI() and CYMDI() are introduced to return the X and Y locations respectively of a specified control relative to the MDI.

  • In 3.3, it is possible to change the security file settings using functions GroupRightAdd(), GroupRightRemove(), GroupRemove(), and RightRemove().

  • In 3.3, it is possible to use an expression to evaluate True/False condition of an Edit control's password property.

  • There was no keyboard shortcut to align the form controls to the Right. The Ctrl+Shift+R keyboard shortcut is now assigned to Align-Right in the form designing.

Java Integration

  • Magic xpa 3.3 studio provides Java integration. It is possible to define a new Field/Model of type Java and interact with Java code.

  • Magic xpa 3.3 studio supports interaction with Java code for ease of working and productive functionality in the same way it interacts with .NET code.

  • Magic xpa 3.3 supports an additional WS consumption capability via Apache Axis2 Component. It compiles a Web Service in to a JAR file (a web service client), and automatically inserts it into Composite Resource Repository (CRR) by creating an entry with name and description. It is possible to use new Java integration functionality to consume the web service. Magic xpa also supports reloading of Axis2 component.

  • The xpa 3.3 supports Java 8.0 for Java integration capabilities.

Changed/Improved Functionality

  • The functions LastClicked(), ClickCX(), ClickCY(), ClickWX() and ClickWY() now work when using the right mouse button.

  • In xpa 3.3, the CallProg() function now also takes the arguments in decimal-point format with x.yy convention.

  • In xpa 3.3, it is possible to use the components recursively.

  • Magic xpa 3.3 now uses an SHA2 set of hashing functions to provide strong hashing for RIA cache files synchronization. It ois possible to select a key size from the options of 224, 256, 384, and 512 bits. Earlier, Magic xpa 3.2 used SHA1 set of hashing functions, which didn't offer selection of key size.

  • Before 3.3, it was possible to select an algorithm from DES (56bits) or AES (128bits). Now Magic xpa 3.3 supports the option of AES algorithm with 128bits key size is by default.

  • In xpa 3.3, it is possible to lock the parent task’s record while manipulating Subform’s child records. It can be done by using ‘Lock’ property of Subfrom control.

  • Magic xpa 3.3 offers easy object navigation from version control.

  • Magic xpa 3.3 supports installation of open source Apache products Axis2, ANT, and Tomcat.

  • In xpa 3.3, it is possible to reload the form/control images even if any external tool has changed them. A new function 'ImageReload()' supports it in Online and Batch tasks as of now.

  • Magic xpa 3.3 now enables the developer to indicate the change in form so that the persistent data of the form is ignored and removed.

  • In xpa 3.3, it is possible to catch the context menu event.

  • In xpa 3.3, you can now inherit the Height and Width properties from a model defined for GUI control.

  • In xpa 3.3, the Systinet (SSJ) is discontinued and is replaced with Apache Axis2.

Removed Functionality

The Average Palette property was removed from the Output Form properties.

Mobile Changes

  • Push notifications are now also supported on Windows 10 Mobile devices.

  • You can define the title and message that will be seen in the progress indicator of mobile devices using the ProgressDialogSet function.

  • In xpa 3.3, it is possible to execute your applications even in low storage situations on iOS devices without losing your local data.

  • In xpa 3.3, it is now possible to activate URI scheme name on windows 10 mobile.

  • In xpa 3.3, now you can use images on windows 10 mobile on the Tab page in Tab control with BG color.

  • In xpa 3.3, for Android, iOS, and Windows 10 mobile devices, the progress indicator now displays a dialog with a title and a message along with a busy icon.

  • In xpa 3.3, for Android, iOS, and Windows 10 mobile devices, RIA cache files are encrypted using AES algorithm.

Space Middleware

The -Dcom.magicsoftware.xpa.HttpResponseMaxReuseTime= setting in the GigaSpaces-xpa\bin\setenv.bat file will be effective by default.

Compatibility and Related Features

  • Magic xpa 3.3 supports Oracle12c release 2.

  • Magic xpa is compatible to work with Microsoft SQL Server 2017.

  • Magic xpa is compatible to work with DB2 UDB 11.

New Special Flags

The following special flags are added into Magic xpa 3.3:

  • SpecialSha2DigestLength: This flag allows you to select the key size from the options of 224, 256, 384, and 512 bits.

  • SpecialKeyboardBuffering: This flag buffers the keystrokes for Rich Client and Online tasks when you are parked on a modifiable Edit control.

  • SpecialEditOwnderDrawBorder: This flag allows owner drawn border around an edit control when in focus.

Note - Please refer to the Release Notes 3.3 for details.

UI Enhancements

  • In xpa 3.3 the new UI enhancement ‘CenterdToWindow’ option given now opens a new form from a Subform, which appears centered to the window of the parent form.

  • In xpa 3.3, it is possible to modify the properties of an ancestor form.

  • In xpa 3.3 Expression Editor, the round and square parenthesis pairs, and the apostrophes get colors to increase readability of the expressions.

  • In xpa 3.3, it is possible to set a different color to each row and the title line of a table.

  • In xpa 3.3, Alpha Masks are supported in Online and RC tasks for Tab Control's Title color, and for the controls ImageButton, Edit, Label, GroupBox, Radio, Checkbox, Image, Table & Child form (WindowType = child). Alpha mask is not supported for Gradient color property. It is not supported for ListBox, ComboBox, Tree Control, and Tab Control.

  • In xpa 3.3, the password property of the Edit Control shows or hides the password. You can use an expression to evaluate True/False condition of the edit control’s password property. If the expression is evaluated to be ‘True’, you get to see the dots else you get to see the password characters that you had typed.

  • Magic xpa added a Browser control to GUI Display form and model, which supports all the magic browser functions and events as in RIA.

  • The look, feel, and sophistication of the Magic xpa 3.3 Studio forms now resembles the Visual Studio's format of forms.

General Changes

  • Magic xpa Supports MQCSP.AuthenticationType of type MQCSP_AUTH_USER_ID_AND_PWD in the messaging ECF while connecting to MQ. The two new functions, ‘OpenQueueAuthenticated()’ and ‘OpenDynamicClientQueueAuthenticated()’ and two new parameters, ‘WMQ.Open Destination Auth’ and ‘WMQ.Open Dynamic Auth’, are introduced for UserID and Password respectively.

  • You can now get to see the table thumb at the correct location by acquiring the total number of records in the range in Online.

  • In xpa 3.3, the support of a flag [MAGIC_SPECIALS]SpecialKeyboardBuffering = E now permits extended keyboard buffering for Online tasks.

  • In xpa 3.3, the timestamp is replaced with hash values while handling RIA cache files synchronization.

Reference
Attachment 
Attachment