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.