If you have a comment on this topic, contact Aptify Documentation. If you want to return to the Aptify Community Site, please click here.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Current »

Note About Aptify 5.5.5

Note that these steps are no longer applicable starting with Aptify 5.5.5 if the appropriate culture is selected at the time the Aptify web interface is installed. See Installing Aptify Web for Aptify 5.5.5 for more details.

 

By default, Aptify supports the Month Day Year (MDY) format. Perform the procedure below if your environment uses either Date Month Year (DMY) or Year Month Day (YMD) date formats. 

The examples in this topic address the process for configuring an Aptify environment to use the date format used in Australia (DMY).

  1. Set server Region and Language setting to the required culture.

     

     
     
  2. Set the Server SQL to the desired default language.
    • For example, in an Australian environment, you would Open SQL server by right-clicking on SQL server and select Advance > Default Language > Select British English



      SOA Pool User Default Language can be English or British English.
       
  3. Download or create different Kendo cultural files for the desired culture in the C:\inetpub\wwwroot\Aptify\script folder
  4. Open the C:\inetpub\wwwroot\Aptify\script\Aptify\framework\ Aptify.Framework.Bootloader.js file for editing.
  5. Search for the getThirdPartyResourcelist() function and add the name of the Kendo culture file to the list of files for the results variable.

    For example
    function getThirdPartyResourcelist() {
    var results; 
    results = [
    //"/log4javascript/log4javascript.js",
    "/jquery-1.10.2.min.js",
    "/kendo.all.min.js",
    "/jquery.Jcrop.min.js",
    "/knockout-2.2.1.js",
    "/adapter.js",
    "/jquery.signalR-2.0.2.min.js",
    "/Ace/src-min-noconflict/ace.js",
    "/Ace/src-min-noconflict/ext-language_tools.js",
    "/dom.jsPlumb-1.7.2.1-min.js",
    "/jszip.js",
    "/kendo.culture.en-AU.min.js"
    ];
    return Aptify.framework.bootloader.getAbsolutePathForAptifyThirdParty(results);
    } 
  6. Save and close the Aptify.Framework.Bootloader.js file.
  7. Open the Aptify.Framework.Configuration.External.js file for editing.
  8. Add following values based on the required culture:

    Aptify.framework.configuration.cultureName = "<culture>";
    Aptify.framework.configuration.calendarDateHeaderFormat = "<date format>"; 

     

    • The following values would be used for an Australian environment: 

      Aptify.framework.configuration.cultureName = "en-AU"; 
      Aptify.framework.configuration.calendarDateHeaderFormat = "ddd dd/MM";



  9. Save and close the Aptify.Framework.Configuration.External.js file
  10. Open the Aptify.Framework-<version_number>.min.js file for editing.
    • For example, if you are running Aptify 5.5.4, you would open the Aptify.Framework-5.5.4.min.js file for editing.
       
  11. Find the shortDateFormat and longDateFormat settings and update the date and time format to the format required for the desired culture. 
    • The following values would be used for an Australian environment:

      Aptify.framework.configuration.shortDateFormat = "d/MM/yyyy"; 
      Aptify.framework.configuration.longDateFormat = "d/MM/yyyy h:mm:ss tt";



  12. Save and close the Aptify.Framework-<version_number>.min.js file
  13. In the Aptify Desktop client, open the Cultures record for the desired culture. 
  14. Click the Culture Formats tab and update the DateFormat and DateTimeFormat settings to align with the shortDateFormat and longDateFormat values used in the previous step.



  15. Ensure that the Aptify user accounts are configured to use the desired culture.
  • No labels