8. Limitations¶
- 8.1. Web Application Server
- 8.1.1. Resin
- 8.1.2. WebSphere Application Server
- 8.1.3. Oracle WebLogic Server
- 8.1.3.1. Database error may occur when the application is stopped in Oracle WebLogic Server 12c (12.1.1).
- 8.1.3.2. Please specify the same database for system database and tenant database in Oracle WebLogic Server 12c (12.1.1).
- 8.1.3.3. Only 1 tenant can be created on Oracle WebLogic Server 12c (12.1.1).
- 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 operating 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. Compile otion would be needed if intra-mart Accel Platform is built in 64-bit 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. There are remarks about 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, linkgae 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.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.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. Size of imuiToggle cannot be changed by setting the style such as height and width.
- 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. On Internet Explorer and Firefox ESR 24, focus will not move unless you hit the tab key twice after moving to the File Add button by the tab move of 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 downlaod 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 maxlengthh 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 Safari 7 some items cannot be set on some management screens.
- 8.2.5.61. On smart phones error may be generated if the process time is too long.
- 8.2.5.62. On smart phones, the name of the downloaded file may possibly be corrupted.
- 8.2.5.63. On some particular smart phone types, retry process (sending request again) may be performed.
- 8.2.5.64. Operations on smart phones sometimes do not work properly depending on device types and browsers.
- 8.2.5.65. Screen layout may sometimes be corrupted if you switch the screen vertical/horizontal orientation.
- 8.2.5.66. 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.67. You may sometimes not be able to download files on smart phones.
- 8.2.5.68. If you specify autofocus to long text or input element of invisible position, screen layout may be corrupted.
- 8.2.5.69. 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.70. On Android standard browser, multi-byte character in the download file name will be corrupted.
- 8.2.5.71. 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.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 out of 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 right) 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.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.1. Setup / Environment Build
- 8.3. Tenant Management
- 8.3.1. Menu
- 8.3.1.1. Display items of menu may not be updated until user logs in again.
- 8.3.1.2. If you register the page that uses IFRAME to My Menu and opens it, the page may not be sometimes displayed.
- 8.3.1.3. You cannot edit My Menu on the launcher.
- 8.3.1.4. After you register the page that uses session to My Menu, you may sometimes not be able to open the registered page from My Menu.
- 8.3.1.5. On the menu structure setting screen, if the “URL” of menu item includes ”./” or ”../”, no authorization will be made to the menu item, and it will be always displayed on global navigation or site map etc.
- 8.3.1.6. There are remarks about screen transition in IFRAME re-director of Menu.
- 8.3.1.7. If you specify the icon outside the predefined screen size as a menu item icon, it will not be displayed correctly.
- 8.3.1.8. Menu items you can register to My Menu will be the ones that are on the site map.
- 8.3.1.9. On the menu setting screen of tenant management, drag and drop operation of node sometimes does not work.
- 8.3.1.10. If you set the Home URL to something other than /home, you cannot transition to global navigation from the smart phone screen.
- 8.3.1.11. Please set the number of display menu groups in global navigation to the ones that fit into the size of window.
- 8.3.1.12. If you update the sort sequence of menu group by either importing via the job or using API, sort sequence of authorized resource is not synchronized.
- 8.3.2. HybridSSO / External Menu Linkage
- 8.3.2.1. Single Sign On authentication is recommended in order to use the external menu linkage function.
- 8.3.2.2. User code at the destination of external menu linkage must be the same at the origin of external menu linkage.
- 8.3.2.3. Latest menu may not be displayed in external menu linkage function.
- 8.3.2.4. Automatic log-in function does not support the log-out linkage of iAP-iWP SSO Linkage Module (IM-HybridSSO).
- 8.3.2.5. Log-in by IM-HybridSSO cannot be made if accessed by Short-cut URL.
- 8.3.2.6. If Web Server or Load Balancer is used, context path of Request URL and context path of iWP / iAF should be set the same.
- 8.3.2.7. SSO Connection is released if you change the password of iWP / iAF while IM-HybridSSO connection is in place.
- 8.3.2.8. Configuration in which multiple SSO authentication providers have linkage with the same SSO service provider is not supported.
- 8.3.2.9. Access may not be successfully established if the session failover occurs while using the external menu linkage function.
- 8.3.2.10. Configuration in which SSO authentication provider has SSO linkage with multiple log-in groups in the same iWP / iAF is not supported.
- 8.3.2.11. Servers that make up IM-HybridSSO must be built on the same domaion.
- 8.3.2.12. iWP / iAF may not be used as [SSO Authentication Provider], and intra-mart Accel Platform may not be used as [SSO Service Provider].
- 8.3.2.13. IM-HybridSSO provides simple Single Sign On functions on intra-mart Accel Platform and iWP / iAF.
- 8.3.2.14. In the environment where iAP-iWP SSO Linkage Module (IM-HybridSSO) is installed, you cannot change the transition destination screen after the log-out.
- 8.3.3. Authorization
- 8.3.3.1. Policy setting on Authorization Setting Screen will be in effect immediately.
- 8.3.3.2. There are remarks about add/update/delete of authorization subject.
- 8.3.3.3. Validity check of Authorization for the router path will not be performed on the dynamic routing.
- 8.3.3.4. Authorization setting for “/home” is defined as separate resources. Care should be taken when the authorization is changed.
- 8.3.3.5. Latest authorization setting may not be always in effect.
- 8.3.3.6. Addition or deletion of access/control authorization of menu group category in authorization setting would not affect the display of menu setting screen.
- 8.3.3.7. If the authorized resource of the page registered in the menu is deleted, system error will occur when the screen is accessed.
- 8.3.3.8. Authorized resource provided by intra-mart Accel Platform should not be deleted.
- 8.3.3.9. On the authorization setting screen, resources and conditions are filtered by the display name of locale of log-in user.
- 8.3.4. Calendar
- 8.3.1. Menu
- 8.4. Application
- 8.4.1. IMBox
- 8.4.1.1. It is not recommended to re-utilize the user code that was used in the past.
- 8.4.1.2. If character code for displaying OpenGraph is not specified, it is converted to UTF-8.
- 8.4.1.3. Sorting sequence of Tag List depends on the internal sort of Apache Cassandra.
- 8.4.1.4. When responding to DirectMessage, users who do not belong to the company will also receive the response.
- 8.4.1.5. There is upper limit of characters used for tag.
- 8.4.1.6. There are following limitations about tag.
- 8.4.1.7. There are limitations about users using IMBox.
- 8.4.1.8. There are limitations about newly arrived messages.
- 8.4.1.9. There are limitations about messages that are not displayed on timeline.
- 8.4.1.10. Posting destination (company name) displayed on the timeline is displayed by tenant locale.
- 8.4.1.11. Mandatory error message on the server side when the posting fails is inappropriate.
- 8.4.1.12. There are limitations on the available characters for user code and tag.
- 8.4.1.13. If posting with attachment file is made to IMBox using a smart phone, Back process is not executed on standard browsers of Android OS Version 3.0, 4.0, and 4.1.
- 8.4.1.14. If user information is deleted, questionnaire information posted would remain.
- 8.4.1.15. Only 9160 is allowed to be set to Cassandra client connection port (rpc_port).
- 8.4.2. IM-Workflow
- 8.4.2.1. There are limitations when system locale is added.
- 8.4.2.2. Master data is required for each system locale.
- 8.4.2.3. Sizing of storage region is necessary depending on the master setting of workflow.
- 8.4.2.4. It is necessary to adjust the server setting etc. depending on the master setting of workflow.
- 8.4.2.5. Process time will increase proportionate to the number of nodes that are set in the route definition.
- 8.4.2.6. Target users will be removed depending on the contents of route setting.
- 8.4.2.7. There are remarks when operating matters in the route definition that includes synchronous node.
- 8.4.2.8. There are items to be noted about the display of flow reference.
- 8.4.2.9. In some cases 2 process request emails are sent to the delegated user.
- 8.4.2.10. Sometimes normal email transmission fails depending on the mail server used.
- 8.4.2.11. Mail address which is set in the user profile will be used for mail destination.
- 8.4.2.12. Sometimes branch route (line) may not show up on the display.
- 8.4.2.13. Saved node setting may not be sometimes reflected correctly on the Matter Handle - Node Edit screen after application is made.
- 8.4.2.14. Standard process name will be displayed as process name of process history that was processed before redeployment.
- 8.4.2.15. Automatic approval will not be made for the node where re-process automatic approval is set for arrive process.
- 8.4.2.16. If you click the status confirmation icon of process target plug-in for the predecessor process of node setting screen, HTTP500 error may result.
- 8.4.2.17. If the process time limit automatic process batch is executed on Hanko imprint project, automatic process will fail.
- 8.4.2.18. Asynchronous Client object cannot be used for the process on standard screen.
- 8.4.2.19. Since the node setting information remains in the copied flow definition, the message “Setting is removed.” will be displayed if you do the import.
- 8.4.2.20. There are reminders about the asynchronous process on standard screen.
- 8.4.2.21. There are reminders about references to HTTP objects in Asynchronous Action Process and Arrive Process on standard screen.
- 8.4.2.22. If the PC-version user contents are displayed on iPhone, Android smart phone, or Android tablet, operations may become unstable.
- 8.4.2.23. We do not guarantee for operations if URL is directly specified.
- 8.4.2.24. In case spWorkflowOpenPage tag is used, it should be placed inside the element that specifies data-role=”page”.
- 8.4.2.25. There are limitations about the User Contents Screen ID.
- 8.4.2.26. If the attachment file is displayed on the matter detail screen, you cannot return to the matter detail screen, because there is no Close button.
- 8.4.2.27. On the flow reference screen, scroll bar of the table that shows process date/time, node name, and so on is not displayed.
- 8.4.2.28. User contents cannot be set for each node in case of smart phones.
- 8.4.2.29. For the selection of process target user, items “Role” and “Public Group+Role” cannot be selected, because they do not exist in the IM-Common Master smart phone version.
- 8.4.2.30. Negotiation mails for process and pull back cannot be sent.
- 8.4.2.31. With regard to the attachment file, only the file types that the device browser supports can be downloaded and displayed.
- 8.4.2.32. In case iPhone is used, workflow matter number is recognized as a telephone number.
- 8.4.2.33. If the process that does not use user contents is made on smart phones, user parameters cannot be passed to the action process.
- 8.4.2.34. Attachment file of application screen cannot be deleted on NTT Docomo GALAXY SⅡ LTE SC-03D.
- 8.4.2.35. After the confirmation process, same matter is displayed in the list as not confirmed.
- 8.4.2.36. There are remarks when registering the user contents with [Apply] screen type to My Menu.
- 8.4.2.37. If system error occurs while processing [Matter End Process/Arrive Process/Mail Send], memory may not be released.
- 8.4.2.38. Subject department on the Standard Process Screen may not be initially displayed.
- 8.4.2.39. If the node is restored by Pull Back after Send Back, process target user will resume to the one before replacement.
- 8.4.2.40. If PC version standard screen is used on iPad(Mobile Safari) or Android smart phone, attachment file cannot be downloaded.
- 8.4.2.41. IM-Workflow does not support the operations on multiple browsers or multiple tabs, and does not support browser back.
- 8.4.2.42. Matter Number Allocation Process (DB Sequence Version) is not available on SQLServer 2008.
- 8.4.2.43. Destination field of negotiation mail is displayed as [0 item] on iPad.
- 8.4.3. Portal
- 8.4.3.1. If the site for embedding internet portlet returns X-Frame-Options, internet portlet is not displayed.
- 8.4.3.2. Width adjustment of portlet may not function properly.
- 8.4.3.3. If you build the environment using long context path and perform tenant environment setup, setup will fail.
- 8.4.3.4. Excess scroll bars are displayed on the edit screen of link collections.
- 8.4.4. ViewCreator ・TableMaintenance
- 8.4.4.1. If you change the column type on the query edit screen, operations may not be performed correctly.
- 8.4.4.2. SQL statement that is generated in [View Creation] may not be executed as it is.
- 8.4.4.3. In case Internet Explorer 9 is used, header line on record edit screen may be shifted.
- 8.4.4.4. In case Internet Explorer 8 is used, 2-byte characters in SQL display on query edit screen are corrupted.
- 8.4.4.5. In TableMaintenance and ViewCreator, only UTF-8 is supported for input/output to CLOB-type field.
- 8.4.4.6. If image icon is selected in the display setting of ViewCreator, it may not be displayed on smart phones.
- 8.4.4.7. There are limitations about thhe table names, view names, and fields names that can be handled by ViewCreator/TableMaintenance.
- 8.4.5. Event Navigator
- 8.4.5.1. If the surrogate pair charactes are used in volume for editing event flow in the event navigator on Internet Explorer 8, warning dialog may be displayed.
- 8.4.5.2. On Internet Explorer 6 and 7 if the transition is made from the link of navigation result to the other tab, URL of address bar is not displayed correctly.
- 8.4.6. ZIP Code Search
- 8.4.1. IMBox
- 8.8. version 7.2 Related
- 8.8.1. Compatibility
- 8.8.1.1. It is necessary for the master to be synchronized for the use of compatibility module.
- 8.8.1.2. There are differences in the set of characters allowed between old and new masters.
- 8.8.1.3. Limitations on Document Workflow (BPW) conform to the limitations on intra-mart Web Platform 7.2.
- 8.8.1.4. Process definition name and Task name should not include [,(single-byte comma)] or [#(single-byte sharp)].
- 8.8.1.5. If the screens cretaed by iWP / iAF do not support the standard mode of Internet Explorer, screens may not work properly.
- 8.8.2. BackwardSync (master synchronization with version 7.2)
- 8.8.3. Migration
- 8.8.3.1. Contents of migration has been verified only for Resin.
- 8.8.3.2. In case of SQL Server, every character string type will be NVARCHAR.
- 8.8.3.3. Migration module is necessary at the tenant environment setup time for the tenant that has upgraded the version from intra-mart WebPlatform to intra-mart Accel Platform.
- 8.8.3.4. Term information in several data will not be adjusted by the system start/end date.
- 8.8.3.5. Data in FormatCreator/IM-VisualDesigner cannot be migrated.
- 8.8.3.6. Information in IM-ContentsSearch is not migrated.
- 8.8.3.7. IM-ContentsSearch template needs to be corrected.
- 8.8.3.8. UI support is needed for the contents screen of IM-Workflow.
- 8.8.3.9. Integrated workflow is not supported.
- 8.8.3.10. Related data for corporate in IM-Common Master is not migrated.
- 8.8.3.11. Currency and currency rate data in IM-Common Master are not migrated.
- 8.8.3.12. Setting data in TableMaintenance is not migrated.
- 8.8.3.13. Some data in ViewCreator is not migrated.
- 8.8.3.14. There are changes in the authority information of ViewCreator.
- 8.8.3.15. Web service access right is not migrated.
- 8.8.3.16. Part of account attribute information is deleted.
- 8.8.3.17. Part of calendar data is not migrated.
- 8.8.3.18. Sort keys for the migrated date information will be automatically numbered.
- 8.8.3.19. Data name of calendar data is not migrated.
- 8.8.3.20. Specifications of screen display based on display colors of date information will vary.
- 8.8.3.21. Calendar ID may need to be changed before migration.
- 8.8.3.22. Maintenance of date information data is necessary after migration.
- 8.8.3.23. Short-cut URL will not be migrated.
- 8.8.3.24. Batch is not migrated.
- 8.8.3.25. Password history is not migrated.
- 8.8.3.26. Export file of menu should always be placed.
- 8.8.3.27. Menu ID is set for the Resource ID of the authorization generated in menu migration.
- 8.8.3.28. If the menu with same URL exists in the menu to be migrated, migration cannot be performed correctly.
- 8.8.3.29. If the migration source has a role that has the same role ID with the role of intra-mart Accel Platform, its contents will be overwritten.
- 8.8.3.30. Information Update Management is not migrated.
- 8.8.3.31. Group Management Authority User Menu is not migrated.
- 8.8.3.32. Please refer to the Compatibility Support Table for Application Common Master API.
- 8.8.3.33. Please refer to the Compatibility Guide for the compatibility functions of Application Common Master.
- 8.8.3.34. Theme setting for the contents screen of document workflow is required.
- 8.8.3.35. Document workflow is not available on smart phones.
- 8.8.3.36. Role of document workflow is to be set again.
- 8.8.3.37. Access right setting for portals is not migrated.
- 8.8.1. Compatibility