Working with XAS

After configuring XAS, update the DB of the target application to register business objects and modules used by XAS as described in Initial Configuration and Preparation topic.

XAS prohibits to modify business objects of the application via the GUI. Such approach protects the user data from possible issues. Due to the fact that some parts of the target application business logic are unavailable in XAS, it is strongly recommended not to change the target application business objects.

The set of functions provided by XAS depend on a particular target application. For instance, this topic describes the configuration of XAS, which is intended to administrate the BCDemo application installed with Xafari. This application uses a most of the framework's features, which is convenient and expedient to configure via the XAS.

xas_1

Target Application General Info

Application info Navigation Item activates the Detail View containing the general information about the target application.

xas_2

  • Name shows the name of the target application, its value comes from the "ApplicationName" key in the <appSettings> section of the configuration file of the target application (for instance, the Xafari.BCDemo.Win.exe.config file). This value used in the DB and it is a part of the AppModules names for the target application (<app_name>.AppModule).
  • Path shows the location of the catalogue or folder with the target application. The path is extracted from the full path of the configuration file.
  • Connection String shows the string specified in the configuration file of the target application (for example, the Xafari.BCDemo.Win.exe.config file).
  • Config File shows the exact path to the configuration file of the target application. Its value is stored in the "TargetAppConfigFilePath" key in the configuration file of the XAS application (xas.exe.config). The "" button in the right side of the Property Editor provides the opportunity to open the file with the default application used by the operation system for *.config files.

Application Model Editting

To edit the target Application Model, XAS provides the appropriate Model group in the navigation system, which includes the Model Differences DB, Application Model Editor and Business Model Editor items.

The Application Model Editor item invokes the DevExpress.ExpressApp.ModelEditor.vNN.M.exe tool for the target application. Invoked Model Editor loads only the modules of the target application. XAS modules do not load for this action. Therefore, only the target Application Model is visible when using this editor.

xas_3

Note

By default DevExpress.ExpressApp.ModelEditor.vNN.M.exe is installed in c:\Program Files (x86)\DevExpress 15.2\Components\Tools\eXpressAppFramework\Model Editor\ folder, this location is specified by the ModelEditor key of the xas.exe.config file. It is important that this directory is the system and the average Windows user has no write permissions. This may give rise to various errors when starting Model Editor (see image below). One way to avoid such situations is to move the DevExpress.ExpressApp.ModelEditor.vNN.M.exe to a more appropriate directory. For instance, it is c:\Users\Public\Documents\Xafari Framework v15.2.9010 Demos\BCDemo\Win\, then we have to change the ModelEditor key value: <add key="ModelEditor" value="c:\Users\Public\Documents\Xafari Framework v15.2.9010 Demos\BCDemo\Win\DevExpress.ExpressApp.ModelEditor.v15.2.exe" />.

xas_4

The Model Differences in DB item invokes the XafariModelDifference List View allowing to work on the model changes stored in the database. This function is available only in case the target application uses the Xafari Model Differences Storage technology included in Xafari.ModelDifferencesDb.dll.

xas_5

The Business Model Editor item invokes the Project.xafml.Editor.exe tool to modify the Business Model of the target application. The name of the main Business Model file is specified by the  "MetaDataRuntimePathXafari" key in the <appSettings> section of the configuration file of the target application.

Note

To edit the XAS Application Model itself, navigate to the Tools|Edit Model.

xas_6

Security

XAS uses the same security system as the target application. The access to the security settings is provided by the Security group of the navigation system.

The Role and User items provide access to the corresponding standard List Views.

xas_7

To familiarize yourself with the Complex Security Strategy, follow the https://documentation.devexpress.com/#eXpressAppFramework/CustomDocument112647. To examine the advanced features of the Xafari Security, refer to the Xafari Security section.

Other Components

Security and Application Model management is implemented in XAS by default. XAS provides the configuring of more different functional components according to the composition of the target business system, the navigation bar will be extended with the corresponding elements. Xafari framework includes a number of solutions that can be configured and managed via the XAS, they are listed in the Xafari Components with XAS Support topic and described in the specialized documentation.