Chapter 2: configuration and security-intellimorph

This article is only for ax practitioners and enthusiasts to learn and exchange. Due to copyright issues in the original article, do not repost it
Although ax is an international product that supports multiple countries, languages, companies, and industries with the same deployment, it is also a highly productive development platform, it makes the layout easy to configure and automatically arranges the layout of application functions. The unique rendering technology is based on modeling element attributes, configuration and Security Settings, and personalization. It allows every user to convert forms, reports, menus, the layout of the corresponding web elements of the menu display control is integrated. This technology is called intellimorph. It supports the fat client and Web Client types in ax.
The primary requirement for intellomorph technology design is to prepare for international release, but unlike other EPR products, intellimorph must be deployed in the same way to prepare for multiple countries in multiple languages, the same user experience must be provided regardless of the language of the user interface. This makes the metadata-driven and property-driven user interaction interfaces necessary. Forms, reports, menus, and menu items take into account both global and local configuration and security settings. One positive side of this design is that users can customize user interfaces in multiple ways. The personalized settings are further extended in ax4.0. You can reference all the fat client forms as your favorites and bind them to any queries.
Intellimorhp Automatic Sorting Function Based on license Code , Configuration and security keys and personalization, no need to change any code. Figure 11-1 shows elements, such as forms, reports, menus, web, and layout filtering structures.

Figure 11-1: intellimorph presentation structure
This layout includes the license code, which enables the configuration key, with the key containing the security key reference or security key sub-configuration key.
The security key controls the access to menu items. Menu items reference available functions provided by user groups or individual users. A single user can belong to multiple user groups, and the complete set of permissions constitutes the largest security level. The last factor in the interface experience is personalization, which allows users to modify the user interface by hiding, displaying, and configuring the display controls.
The next section will describe more details about the interaction and dependencies between these elements and them, including personalized discussions.
Note:
The presentation of the user interface is not limited to support intellimorph technology, but also provides a rich set of design options for the development of various control types, such as ActiveX and listview controls. Mircrosoft Windows Forms. Ax reports also have their own designer, which allows you to visually design a report during the arrangement and formatting of X ++ and attribute forms, haha .).
Best practices
Understanding how intellimorph works can help develop the runtime presentation of Application Extensions. If you follow the best time design rules and patterns, You can optimize the use of intellimorph technology to ensure a unified application runtime interface. The best practice principle is to use the default attribute settings of the render control, which determines how to render elements and functions. It also includes general use of tags, field groups, extended data types, automatic groups, security, configuration keys, and menu items. The standard application of ax adopts all the best practice rules and models for development. This provides a unified way for applications to interact with the underlying business logic. Chapter 4, "morphx development tools", describes the best practice tools. Details of rules and modes can be found in the ax SDK.
Form Principle
If you always design an application form from the beginning, designing an application form is very time-consuming, especially when the application must run in multiple languages. This is why best practices require you to create a report and manually set very few attributes by dragging as much as possible. Sometimes the default attribute values of the system may not be suitable for the current situation. This is why almost all attributes can be customized.
When designing a table or view as the form layout of the underlying data source, you can use the same field group and field structure as the original table and view in AOT, if you drag it from these nodes to the data sources node of the form. These data sources should be configured to use the ax autojoin system, which ensures data synchronization when two forms are connected. When processing layout and attribute settings, retain the auto or default settings. This can optimize the use of the Automatic Arrangement technology and limit the need to move pixels to unify and arrange the display of forms with other applications.
When designing a form, follow the recommended practices in the following list to optimize the use of the field arrangement technology as much as possible. Most modes are the attribute settings of form design.
1. Try to use the default settings, especially left, top, width, height, frame, ssresize, windowtype, and hidetoolbar.
2. When using tables or views as data sources, use the rule roup attribute.
3. When the automatic roup attribute is used, set the autoscaling roup attribute to yes, so that all behaviors will be adjusted based on the data source behavior.
4. Use tags instead of hardcoded strings.
5. Use tags as help text (status bar help) instead of hard-coded strings.
6. Using the titledatasource attribute provides a better and more visible data experience for users.
7. If you want to use controls in X ++ Code, set the autodeclaration attribute to yes.
8. Try to use the autojoin system.
If the customer requires a special user experience, there is no design restriction to prevent all user interfaces from being modified again. The only drawback is training. Flexibility and upgrades become complicated to some extent.
Principles of reports
Intellimorph is even more important to a report than a form. The best practice of a report is to retain the default settings of attributes. When designing a report, the environment in which the report will be executed is generally unknown. This type of information includes the following:
1. Size of the paper used by the user's printer
2. Depending on the user's installation settings and language, the tag length or content may be different
3. Which fields are disabled through the security and configuration key settings?
4. User-Defined field (Extended Data Type) Length
5. sorting order of data sent to reports
6. Does the user system use subtotals to set printing or use totals to set printing?
7. default font and font size settings
8. Number of records in the table in which the report obtains data
You can create two types of report designs: auto (autodesignspecs) or generated (design ). Most common reports can use auto, and generated design cannot be implemented through auto design due to special functional requirements. You can also use generated to design reports that are determined by external sources. For example:
1. The layout of the report is determined by the outside, and the report must be displayed in a very specific position.
2. Adjust the design report according to your needs during deployment. An invoice is an example. Most controls need to have a fixed position (not set to auto) and move them with the report designer.
Follow the following design pattern as much as possible:
1. use default attribute settings, especially orientation, width, label, and label width and format information. Due to fixed settings, the report control does not consider the available intellimorph Automatic Arrangement Technology in the attribute form.
2. Use Auto Design Report Type whenever possible
(Note: The real ax report platform is too sad for reports with high requirements on the format ).
Use intellimorph
Intellimorph provides many options for personalized ax forms. These options allow you to move controls, set control properties, and add additional fields to the form. The form is customized when the application is running and set to be saved by each user. Depending on the personalized type, personalized options can be called in many places. Whether you move the cursor to form, hide a column through the menu command, or rename a column through the advanced personalized form, the same framework is used for personalized options.
Advanced personalized form, as shown in Figure 11-2, provides personalized options for users:

Figure 11-2: Advanced personalized forms
With this tool, you can change the order of tabs, move elements, remove fields, add additional fields in the form data source, rename fields, and prevent the field content from being edited, you can change the default field length or even select one of multiple versions of the form. Personalized settings can be shared. For example, if a department wants to adopt a general appearance, the appearance is different from the standard appearance of the company, but it does not want to modify the global form layout. You can set it like this.
In order for users to work in a personalized manner, they must use form design attributes. Allowusersetup And allowadd defines different levels of personalization. There are four levels of personalization, as shown in table 11-1:
, therefore, the content in the following Table 11-1 is not translated for the time being, so we will discuss it later ).
the use of X ++ code in form can also change the personalization level. If the method of the control location is overwritten, the core automatically limits the level set by the user.