8.2. Platform Functions¶
- 8.2.1. Setup / Environment Build
- 8.2.1.1. There are remarks when building intra-mart Accel Platform as a distributed system.
- 8.2.1.2. Deployment process of WAR file may take time depending on the hardware specifications.
- 8.2.1.3. There are remarks for users connecting intra-mart Accel Platform to SystemDatabase, TenantDatabase, and SharedDatabase.
- 8.2.1.4. Screen will not be displayed correctly unless you select one or more screen themes.
- 8.2.1.5. Trial Version (product for trial use) cannot be installed in operations environment.
- 8.2.1.6. If the time to session timeout is short when setting up the tenant environment, 404 error will occur when the process is completed.
- 8.2.1.7. When intra-mart Accel Platform is started, it is assumed that Database has been already started.
- 8.2.1.8. Compilation option should be specified if intra-mart Accel Platform is built on Linux environment.
- 8.2.1.9. Operation in the mixed Windows/Linux environment is not possible.
- 8.2.1.10. Path of the shared directory which Storage refers to should be the same.
- 8.2.1.11. Only Japanese, Chinese (zh_CN), and English are available as OS on IM-Juggling.
- 8.2.1.12. User module cannot be placed directly in the modules folder of IM-Juggling.
- 8.2.1.13. Setting File and your own program should be set on IM-Juggling and created as WAR files.
- 8.2.1.14. It is required to do the operation after all the tenant environment setups are completed.
- 8.2.1.15. Environment which is built with the own certificate is outside the scope of warranty.
- 8.2.1.16. If integrated Windows authetication is enabled in Internet Information Services（IIS）, Web service cannot be used.
- 8.2.1.17. If integrated Windows authentication is enabled, some part of linkage function to external software cannot be used.
- 8.2.1.18. There is only 1 tenant that is resolved by integrated Windows authentication.
- 8.2.1.19. Character code which is used in intra-mart Accel Platform is UTF-8 only.
- 8.2.1.20. Error log is generated if mod_proxy is used.
- 8.2.1.21. If reverse proxy function such as mod_proxy or load balancer is used, it is necessary to always include the context root of AP server in the request.
- 8.2.1.22. Please do not delete the tenant master related material provided by intra-mart Accel Platform.
- 8.2.1.23. If tenant environment setup is made before tenant information setting is done, it will be outside the guarantee.
- 8.2.1.24. In case tenant auto resolution function utilizing request information is used, error may occur if the access is made by the request resolved as non existing tenant.
- 8.2.1.25. You are not allowed to create multiple schemas in the database for use by multiple tenants.
- 8.2.2. Common
- 8.2.2.1. Maximum length of key name available for PermanentData and SharedMemory depends on the file system.
- 8.2.2.2. If error page is customized, error page will be displayed in the IFRAME of IFRAME re-director.
- 8.2.2.3. If the data format for inputting account context is changed, date related process may not be performed correctly.
- 8.2.2.4. departmentByCompany and postByCompany in the user context may become undefined.
- 8.2.2.5. If log is generated at DEBUG level, account password may possibly be written.
- 8.2.2.6. On some search screens capital letter and small letter are handled separately during search.
- 8.2.2.7. If you access small letter URL with capital letters in Windows environment, invalid actions may result.
- 8.2.2.8. It is strongly recommended not to directly update or delete data without using API.
- 8.2.2.9. Session management by URL cannot be used.
- 8.2.2.10. It is necessary that account and profile are synchronized.
- 8.2.2.11. If setting for database log is made, error level log is generated when it is launched.
- 8.2.2.12. “%28” (encoded “(”) cannot be used for URL.
- 8.2.2.13. There are limitations about script development model.
- 8.2.2.14. If zip file is generated by Archiver4Storage, unzip operation may not be performed correctly because of different delimiter characters by OS.
- 8.2.2.15. In case Base URL is explicitly set, log-in will fail if it is accessed by the URL other than the Base URL which is set.
- 8.2.2.16. In case date/time of summer time is used in script development model, conversion of date object (Date) to character string is not performed accurately.
- 8.2.2.17. Prefix of table name will be a reserved word of intra-mart Accell Platform.
- 8.2.2.18. If multiple tenants are built by WAR file, it is recommended to separate the database for connection by each instance.
- 8.2.2.19. It should conform to the specifications and limitations of various Database and JDBC drivers.
- 8.2.2.20. It is always necessary to have 1 layer path for URL at which intra-mart Accel Platform is operated.
- 8.2.2.21. If UI tag is stated in the Loop process in JSP, the value specified by the literal may become effective only for the first one time.
- 8.2.2.22. Styles or APIs that are not published may be deleted without advance notice.
- 8.2.2.23. Tenant which is the target for process needs to be identified to access the resource in tenant.
- 8.2.2.24. Script may be executed twice if dom operation is made in jQuery.
- 8.2.2.25. If you customize the program source code provided on the product, related functions and modules will become outside the scope of our support.
- 8.2.2.26. Exception would occur at rare occasions, when the session is discarded.
- 8.2.3. System Management
- 8.2.3.1. Some user codes are not available for use, because they are reserved by system.
- 8.2.3.2. System Administrator can access all screens.
- 8.2.3.3. User code of system administrator should not overlap with the user code of general users.
- 8.2.3.4. If you click [Return to Home Screen] on system administrator’s authority error screen, you may transition to the home screen of general users.
- 8.2.4. Authentication Functions
- 8.2.4.1. URL of the screen intended for display in IFRAME cannot be set in the authentication confirmation screen.
- 8.2.4.2. Authentication confirmation screen may be displayed before process completion message is displayed.
- 8.2.4.3. If you leave the log-in screen with no action for a while, log-in cannot be made.
- 8.2.4.4. If password expiration change screen is accessed directly, inappropriate message will be displayed.
- 8.2.4.5. There are remarks about SSO (SingleSignOn) environment.
- 8.2.4.6. InvalidClassException error may occur when the screen is accessed.
- 8.2.4.7. When the tenant auto resolution function utilizing request information is enabled, access may not be possible if the log-in by system administrator fails.
- 8.2.4.8. In case integrated Windows authentication is used, authentication dialog may be displayed on the system management screen.
- 8.2.4.9. Some authentication processes are outside the scope of double login pevention function.
- 8.2.4.10. Double login check may not be performed correctly, if the same user logs in from multiple browsers at the same time.
- 8.2.4.11. Login may fail during Integrated Windows Authentication.
- 8.2.4.12. URL for authentication confirmation target should not be set to the one that assumes access by Ajax.
- 8.2.4.13. OAuth Authentication Module cannot be used in the environment where IM-SecureSignOn for Accel Platform is installed.
- 8.2.5. Client Browser
- 8.2.5.1. If you do the reload while getting data in Ajax communication, error may occur.
- 8.2.5.2. Input form and search condition input form may be displayed differently depending on the browser.
- 8.2.5.3. If you display the tree screen from the menu, memory leak will occur at the client side.
- 8.2.5.4. Please disable the pop-up block on browser.
- 8.2.5.5. Screen behavior may be sometimes incorrect because of the browser cache.
- 8.2.5.6. Horizontal scroll may happen on some particular theme.
- 8.2.5.7. Browser will get slower if you write huge volume of text to imuiRichtextbox.
- 8.2.5.8. With regard to UI components in general, if you specify a character string that starts with “%” for an internationalized attribute, it will be displayed as “undefined”.
- 8.2.5.9. We do not guarantee the operation of “Back” button which is a standard browser function.
- 8.2.5.10. If you combine the resizable components, resize start position of outside component will have some limitations.
- 8.2.5.11. We do not guarantee the operation if the same type of browsers are used in multiple number or on multiple tabs on the same computer.
- 8.2.5.12. If you drag the tab with CLOSE icon, layout may be corrupted.
- 8.2.5.13. ListTable display in the sub-role search dialog on role registration screen will be changed.
- 8.2.5.14. Display of layout may be corrupted depending on the browser type.
- 8.2.5.15. Display of layout may be corrupted depending on the browser, if compatibility theme is used.
- 8.2.5.16. You cannot send undefined or null as a parameter in imuiPageDialog.
- 8.2.5.17. Character size of message boxes placed under imuiAccordionItem will get smaller.
- 8.2.5.18. If you place imuiDropdown under imuiAccordionItem, drop down menu will be displayed hidden under the accordion.
- 8.2.5.19. If you place imuiRichtextbox under imuiAccordion, display may be corrupted.
- 8.2.5.20. In imuiToggle its size cannot be changed even if height is specified by style attribute.
- 8.2.5.21. If you implement the program to receive uploaded file by SAStruts, you may not be able to limit the upload by file size.
- 8.2.5.22. If you specify the same name attribute to multiple input elements, imuiValidate will not work properly.
- 8.2.5.23. If script tag is stated in imuiDialog, the process will be called twice during the loading.
- 8.2.5.24. On Internet Explorer 11 and Firefox ESR 24, dotted line is displayed when input[type=”file”] button is focused.
- 8.2.5.25. Tab should be pressed twice to move the focus in imuiFileUpload.
- 8.2.5.26. If you display the dialog with modal option set to true inside the dialog with modal option set to true again, event propagation will stop.
- 8.2.5.27. CSS (Style Sheet) cannot be specified for optgroup attribute depending on the browser in use.
- 8.2.5.28. If the display area of imuiTabItem is an element cretaed by iframe, drag operation does not work properly.
- 8.2.5.29. Style of the characters entered in imuiRichtextbox may not be reflected depending on the font of the browser.
- 8.2.5.30. Flash screen sometimes does not work properly on Google Chrome.
- 8.2.5.31. On Internet Explorer 8 only, layout will be corrupted if max-width is specified in imuiSelect.
- 8.2.5.32. On Internet Explorer 8 and 9, multiple files cannot be selected at the same time in imuiFileUpload.
- 8.2.5.33. On Internet Explorer 8 and 9, placeholder cannot be displayed.
- 8.2.5.34. Compatibility mode option of Internet Explorer is out of scope for support.
- 8.2.5.35. Error may occur when you download the attachment file.
- 8.2.5.36. When Internet Explorer is used, security zones should match in order to display external site in IFrame.
- 8.2.5.37. If Internet Explorer 8 is used in SSL environment, you cannot download the file.
- 8.2.5.38. On Internet Explorer 10 only, if you focus on and release the right-aligned text box, characters are displayed as buried.
- 8.2.5.39. If you log in using Internet Explorer, 403 error may sometimes occur.
- 8.2.5.40. When Internet Explorer is used, first letter of the download file name may be lost or corrupted.
- 8.2.5.41. On Internet Explorer 10 or later, you cannot upload the 0-byte file by imuiFileUpload.
- 8.2.5.42. On Internet Explorer 8, favicon.ico sometimes may not be displayed.
- 8.2.5.43. On Internet Explorer 8 and 9, if you upload files that exceed the limit value, the message unrelated to the file size will be displayed.
- 8.2.5.44. On Internet Explorer 8 or later, if you register the page of the site that has different security zone and open it by pop-up, the page will be displayed on the parent screen.
- 8.2.5.45. On Internet Explorer 8, horizontal width of imuiButton will be displayed larger than usual.
- 8.2.5.46. On Internet Explorer 8, horizontal width of imuiToggle will be displayed larger than usual.
- 8.2.5.47. On Internet Explorer 11, Japanese input may not be possible to elements for which maxlength attribute or contenteditable attribute is specified.
- 8.2.5.48. On Internet Explorer 11 of Windows 7, if you are using Office IME, single-byte KATAKANA mode is entered by specifying ime-mode: active.
- 8.2.5.49. On Internet Explorer 11 of Windows 7, display font will become MS PGothic or MS Gothic.
- 8.2.5.50. When imuiFileUpload is used, files that exceed 4GB in size cannot be uploaded on Internet Explorer 10 or 11.
- 8.2.5.51. On Internet Explorer, status bar may continue to work even after the screen display is finished.
- 8.2.5.52. When a single-byte alphabetic button and a Japanese button are placed side by side on Internet Explorer, a vertical gap of about 1px would appear.
- 8.2.5.53. On Firefox ESR 24, if the icon of the size bigger than the button is specified for imuiButton, it will exceed the area.
- 8.2.5.54. On Firefox ESR 24, the vlaue of label in optgroup tag of imuiSelect is shown in italic.
- 8.2.5.55. On Firefox ESR 24, if you place imuiRichtextbox in imuiDialog, characters may not be entered into imuiRichtextbox.
- 8.2.5.56. On Firefox ESR 24, double frame lines are displayed when input[type=”range”] is focused.
- 8.2.5.57. On Firefox ESR 24, margin may be generated at the lower part of the portlet.
- 8.2.5.58. On Firefox ESR 24, search operation does not take place while IME entry is being made to imuiAutocomplete.
- 8.2.5.59. In case Mac OSX(10.7.0 or later) is used, tree for tree display may not open.
- 8.2.5.60. On smart phones error may be generated if the process time is too long.
- 8.2.5.61. On smart phones, the name of the downloaded file may possibly be corrupted.
- 8.2.5.62. On some particular smart phone types, retry process (sending request again) may be performed.
- 8.2.5.63. Operations on smart phones sometimes do not work properly depending on device types and browsers.
- 8.2.5.64. Screen layout may sometimes be corrupted if you switch the screen vertical/horizontal orientation.
- 8.2.5.65. In case Android 4.x standard browser is used, you may not be able to upload the file if the file name contains symbol characters.
- 8.2.5.66. You may sometimes not be able to download files on smart phones.
- 8.2.5.67. If you specify autofocus to long text or input element of invisible position, screen layout may be corrupted.
- 8.2.5.68. On Android OS 2.3.6 standard browser, if you tap the “following” button of profile dialog, button character will be corrupted.
- 8.2.5.69. On Android standard browser, multi-byte character in the download file name will be corrupted.
- 8.2.5.70. On Android standard browser, if the pop-up window is opened by another pop-up window, the button on some error screens displayed inside the pop-up window does not work.
- 8.2.5.71. If iOS8.0.x or 8.1.0 is used, screen does not close even when [x] icon is clicked.
- 8.2.5.72. If the screens for PC are displayed on Safari of iPad/iPhone, some functions are limited depending on the browser specifications.
- 8.2.6. Internationalization
- 8.2.6.1. There are limitations about time zone.
- 8.2.6.2. It is not recommended to change the default locale of tenant after system operation has started.
- 8.2.6.3. Descriptions and comments in the setting files will not be internationalized.
- 8.2.6.4. Message which is generated by IM-Propagation will be only in English.
- 8.2.6.5. It is not recommended to reduce the system locales during the system operation.
- 8.2.6.6. Locales of the messages generated in the log could be mixed.
- 8.2.7. IM-Common Master
- 8.2.7.1. There are limitations about specifying time zone in case today is handled.
- 8.2.7.2. Some screens are not correctly displayed on Internet Explorer.
- 8.2.7.3. All the language data you intend to use in IM-Common Master should be registered.
- 8.2.7.4. Memory leak problem may occur when IM-Common Master screen is used on Internet Explorer 8 and 9.
- 8.2.7.5. Mac safari is outside the scope for support for IM-Common Master Management screen.
- 8.2.7.6. While executing import of IM-Common Master, other operations/import should not be performed.
- 8.2.7.7. About condition specification (AppCmnSearchCondition)
- 8.2.7.8. Maximum number of subject groups that can be used for authorization control (access authority) for Company is 1000.
- 8.2.7.9. The only subject resolver that can be used for authorization control for Company is DeclaredSubjectResolver.
- 8.2.7.10. On Firefox ESR 24.5 [OK] button in the calendar pop-up sometimes does not work.
- 8.2.7.11. Scale of the term is contracted in Term Display Scroll Bar.
- 8.2.7.12. Number of implicit conditions that can be specified on the search screen are limited.
- 8.2.7.13. Synchronization from Application Common Master to IM-Common Master is not made.
- 8.2.8. Web Service
- 8.2.8.1. There are limitations about Web services in general.
- 8.2.8.2. This is about the contents of Axis2 - 1.4.x current specifications.
- 8.2.8.3. This is about the contents of authentication/authorization for Web service.
- 8.2.8.4. This is about the contents of Web service provider.
- 8.2.8.5. These are the limitations about Web Service client.
- 8.2.9. TERASOLUNA Global Framework on Accel Platform
- 8.2.9.1. Only Web Application Server that is supported by [TERASOLUNA Global Framework on Accel Platform] is Resin.
- 8.2.9.2. Unique correlation between the URL of menu setting and the value of @RequestMapping should be set, if menu display and authorization are enabled in TERASOLUNA Global Framework linkage.