Request to the Steps involved in Arabic Language Enablement for Web Version – Axpert 10.9

Request to the Steps involved in Arabic Language Enablement for Web Version – Axpert 10.9

Utilize Axpert desktop to define the language via Tools->Define Language.
Once a language defined, we will be able to export all menus and options to excel template. We can provide the alternate text for each item in the respective language and import back.  Before that needed to ensure your db is Unicode support enabled.



    • Related Articles

    • Axpert Licensing

      10.x  (9.8 - 10.8) Following are different type of license editions available to use for Axpert versions between 9.8 to 10.8. Evaluation Edition– Allows users to develop and use an app. The app will allow entry of only 500 records in any form in the ...
    • Test Mail through Axpert Properties over web not displaying any message

      If there is no message or trace, when setting up the office 365 email account through Axpert Properties in web then the following can be tried out. Open the Microsoft 365 admin center and go to Users > Active users. Select the user, and in the flyout ...
    • Error Unable to connect Redis server, when clear In-Memory DB in 11.2.1 Axpert Web

      If you experience the below issue when you clear In-Memory DB. It may be due to redis connection not available in axpert configuration. In web config.file, EnableAxpertConfiguration value as "true" For axpert Configuration setting, in web url change ...
    • Signature Capture Issue in Axpert Mobile v10.9

      The issue is with the signature capture functionality in the latest version of Axpert Mobile (v10.9). There is no default feature to draw signatures on the input field. If it is referred to saving through an image field and using it on fast report, ...
    • Postgres 14 version has an issue in establishing connection from Axpert

      PostgresSQL 14 uses “scram-sha-256” method for authentication by default (as per pg_hba.conf file), which is causing the connectivity issues in Axpert. Solution for the issue : The method “scram-sha-256” needs to be replaced as “trust” in pg_hba.conf ...