|
Data Providers
|
5.2.1120.3
|
|
MxAdapter enables the developer to access data and data objects from several different data source types. This tool provides full SQL Server data access, including all objects tables, views, stored procedures and functions. With all this, there is no limitation on using or implementing any business logic. Another data source type available is Oracle. Like in SQL, a full database object access is available also in Oracle. But MxAdapter also supports web service data sources. These are commonly used in exchanging data with different systems. When developing applications for process industry, the connection to devices through supported OPC and iHistorian data source makes your application really powerful and efficient. And if this wide variety of data source types is still not enough, you can simply create your own data source type and include it into MX-Developer. With this feature, connecting to data sources and retrieving data from them has never been easier. A developer can access and exploit the full functionality of data and data objects without writing a single line of source code.
|
|
|
|
|
|
|
Data Source Object Browser
|
5.2.1120.3
|
|
The data source object browser enables the user to see, browse and eventually use data source objects. This tool is integrated in the MxAdapter component. In case of a database, data source objects are tables, views, stored procedures and functions; in case of web services, objects are methods. With the data source object browser, it is possible to specify which object and which data from that object will be presented to the user. Individual data sources can be located on different sources and different databases. Another strong feature of the browser is also the fact that a connections string in design time can differ from the one in runtime. But the most important advantage this tool offers is the possibility to prepare data and data objects that can be displayed in the user interface, without any programming. Every action is achieved by simply selecting, clicking and dragging. This eliminates the possibility to generate bugs and therefore saves considerable time for eventual debugging.
|
|
|
|
|
|
|
Stored Procedure Support
|
5.2.1120.3
|
|
Stored procedures are completely supported in MX-Developer. They can be easily accessed in both SQL and Oracle database types. A stored procedure is a very efficient database object because it enables data manipulation on basis of input parameters. The stored procedure can also implement and execute business logic and thus represents the most appropriate database object for providing data to the application. Stored procedures can be used for defining schema or for specifying data source’s readable and writable statements. They are a very useful object and can contribute a lot to building reliable and efficient business logic quickly and with less effort.
|
|
|
|
|
|
|
Statements
|
5.2.1120.3
|
|
This feature offers the user the ability to select existing basic CRUD statements or to add customized statements for data manipulation. Statements are objects responsible for data exchange. MX-Developer allows an unlimited number of readable or writable statements. Individual statements include properties which can be configured to specify behaviour, fields mapping, input and output parameters, execute conditions and make notifications. Fields mapping and parameters setting can be done automatically or manually at any time. Each parameter has its own set of properties that can be used to customize its behaviour, appearance, default value, etc. Execution conditions dictate the time when a certain statement is executed. The user can set any kind of condition in the expression editor. Conditions can be related to the environment or to the data source information. The best characteristic of MX-Developer is that all mentioned above can be achieved completely without programming, which in other words means that syntax, content and other mistakes are not possible.
|
|
|
|
|
|
|
Master Detail
|
5.2.1120.3
|
|
The master detail feature enables the developer to define parent-child relations between two or more data sources of any type (SQL, Oracle, Web Services, OPC, etc). Data sources do not even need to be on the same server. Master detail feature is thus very useful especially when displaying two or more separate data sources in different controls. This functionality is achieved with the help of a foreign key feature. Master detail relationship is implemented simply by clicking and setting a few properties on the detailed data source. Usually, the implementation of such features demands the knowledge of a programmer but with MX-Developer’s master detail this can be done a lot quicker by any user, without worrying of producing bugs.
|
|
|
|
|
|
|
Field Editor
|
5.2.1120.3
|
|
Field editor has been designed to perform such editorial functions as rearrangement, modification and deletion of the data. It allows the user to enter, alter, format and store data in a more efficient and simple way. For this purpose, several different types of editors were developed. The type of editor used is determined with the data type of the field. Each type has its own editor. For easy data manipulation editors such as expression editors, lookup editor, calculator, date time, image, drop down editor, etc. were introduced. Each of them has its own set of properties that define its behaviour, appearance and data binding. Editors specify also the format of the entered value. This means that different formats of data can be standardized to make the whole application more uniform. Again, all this is available in the MX-Developer’s field editor without the need to write a single line of source code.
|
|
|
|
|
|
|
Consistency
|
5.2.1120.3
|
|
Consistency is usually implemented in systems which require real-time data presentation. Data is considered consistent if the data displayed is equal to the data stored in the data source. Consistency checking and managing is implemented in MX-Developer on basis of individual fields. Data consistency is periodically checked for any period desired. One of the strongest features of MX-Developer is the possibility to define an action that will be executed after the inconsistency has been established. It is possible to leave the data as it is, to reload it or to inform the user about corrupt data so that he can then decide about the next most appropriate action. This simple and easy-to-use feature requires only a few clicks for implementation.
|
|
|
|
|
|
|
Expression Engine
|
5.2.1120.3
|
|
Expression engine is a very powerful feature that executes any kind of expression created with MX-Developer’s Expression Editor. An expression is a combination of any field values, variables, operators and functions. Values of the expression can be used for default values, read-only conditions, calculated fields, execution condition, workflow logic, etc. The Expression Editor provides several environmental as well as system functions. Additionally, the use of general information about each data source, and exact and detailed information about individual fields and their values is possible. The functionalities of the expression engine can be used in number of situations to enhance the behaviour and the appearance of an application. This feature is one of the reasons why developing applications with MX-Developer is so easy.
|
|
|
|
|
|
|
Constraints
|
5.2.1120.3
|
|
MX-Developer’s Constraints feature enables the developer to specify conditions for individual fields, by which field values are limited. This feature supports several types of constraints such as expression, date, string, numeric and logic, which can be used to examine the value of a field. For example, constraints can be automatically retrieved from the data source when defining a schema, which reduces development time significantly. Manual adding of desired constraint is also possible with this feature. Specified constraints are then used everywhere in the application when manipulating with data. The user is elegantly warned when the edited value exceeds the constraint limits. This prevents the user to enter inappropriate data that could lead to major errors and unpredictable behaviour of the application. MX-Developer’s Constraints feature is a must for users who want to create simple-to-use, attractive and highly efficient applications.
|
|
|
|
|
|
|
Default Value
|
5.2.1120.3
|
|
The default value feature assists the user in the process of data entering by offering him valuable suggestions concerning data values. It is especially useful to automatically provide parameters value for a statement. A statement can be executed without the user actually entering any parameter values at all.
|
|
|
|
|
|
|
Read-Only Condition
|
5.2.1120.3
|
|
The read-only condition is a feature to be used when implementing more sophisticated business logic in an application. The read-only condition is defined as an expression and it is evaluated by the expression engine. This makes it possible to keep the field read-only and prevents further editing whenever the read-only condition is fulfilled. Conditions can be defined by using any of the numerous variables and functions in the expression editor.
|
|
|
|
|
|
|
Execution Condition
|
5.2.1120.3
|
|
The execution condition can prevent an individual statement from being executed. This feature is most useful when some data-, environmental- or system-variable influences the behaviour of a statement. The execution condition is defined as an expression and it is evaluated by the expression engine. This feature is very important because such functionality is usually developed by programmers, whereas here the functionality is already implemented and ready to be used.
|
|
|
|
|
|
|
Complex Editor
|
5.2.1120.3
|
|
The complex editor feature offers new, additional ways to customize user-interfaces. With it, the user can implement even the smallest details requested by a customer. Complex editor enables the user to create better-looking and more appropriate user-interfaces. It automatically creates editor functionalities based on the selected data source. The tool can be used as a part of the user-interface or as a pop-up editor in a workflow. The functionality of this feature can satisfy even the most demanding customer requests for user-interface appearance.
|
|
|
|
|
