intra-mart Accel Platform 2014 Winter(Iceberg) / Release Note Initial Version 2014-12-01

Table Of Contents ≪  8.4. Application 8.4.2. IM-Workflow  ≫

8.4.1. IMBox

8.4.1.2. If character code for displaying OpenGraph is not specified, it is converted to UTF-8.

  • In OpenGraph character code that was specified for META tag of the target site is obtained and converted.
    If character code is not specified for the target site, target site will be converted by fixed UTF-8.

8.4.1.3. Sorting sequence of Tag List depends on the internal sort of Apache Cassandra.

  • If the tags are created only with numeric values (1, 2, 3...etc),
    sorting method of tag list is based on the internal sorting of Apache Cassandra, and so it will not be displayed in the registration sequence.
    See [Sorting of Tag List] below.
  • Sorting of Tag List
    ../../_images/limitations_imbox_sort.png

8.4.1.4. When responding to DirectMessage, users who do not belong to the company will also receive the response.

  • When responding to DirectMessage, there is no checking performed for those who can access the threads if these users belong to the company.
    Response will be sent to users who do not belong to the company, and these users cannot be confirmed.

8.4.1.5. There is upper limit of characters used for tag.

  • Since tag is to be used as URL, error will occur if it exceeds the number of characters that can be used as URL.
    Therefore, its upper limit is set to 20 characters.

8.4.1.6. There are limitations about tag.

  • In case of tag-only follow, if there is a posting from a non-following user, new arrival notification will not be put to MyBox.
  • If the tag that you follow is added to the thread, the message will not be displayed unless you draw it again.
  • If the tag that you follow is deleted from the thread, the message will not be deleted from MyBox.

8.4.1.7. There are limitations about users using IMBox.

  • IMBox users should belong to the company.
    If someone belongs to multiple companies and there is no main belonging specified, your belonging department must be selected.
    Moreover, it is necessary that authorization to the belonging company is enabled.

8.4.1.8. There are limitations about newly arrived messages.

  • If there are 2 or more new messages posted at the same timing, new arrival notifications may be displayed twice.
    If all the messages are obtained by the first new arrival notification, only the new arrival notification is displayed.

8.4.1.9. There are limitations about messages that are not displayed on timeline.

  • If there are 3 or more responses to the message that are not displayed on the timeline within the same thread,
    new arival display would be only for 2 responses, and clicks on the displayed links are needed for displaying all the remaining new arrivals.

8.4.1.10. Posting destination (company name) displayed on the timeline is displayed by tenant locale.

  • Posting destination (company name) displayed on the timeline is dispalyed by tenant locale.
    It will not be displayed by the user selected locale.

8.4.1.11. Mandatory error message on the server side when the posting fails is inappropriate.

  • Error message which is returned from the server side when the message posting fails may include inappropriate character string (variable name).
    This happens when the message such as a blank character is sent to the server avoiding the client side validation.

8.4.1.12. There are limitations on the available characters for user code and tag.

  • Following character strings should not be used for user code and tag.

     [*] User Code
   `/\:*?"<>|#{}%&~`
   top underscore  example : _test
   consecutive period  example : te......st
   last period  example : test.
   top period  example : .test
   top and last single-byte spaces are deleted.
   top and last double-byte spaces are deleted.
   [setprofile]

 [*] Tag
   ?(/
   last period  example : test.
   top period  example : .test
   top and last single-byte spaces are deleted.
   top and last double-byte spaces are deleted.

 [*] companyCd
  top consecutive period  example : ..test

<*> Character string that includes period between characters may be used. Top and last single-byte/double-byte spaces are deleted.

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.

  • If the posting with attachment file is made to IMBox by smart phones, 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.

  • In case the function to delete user information on Cassandra, which was added in 2013 Winter(8.0.6), is used,
    user information can be physically deleted. However, information which the deleted user posted in the past would still remain.

8.4.1.15. Only 9160 is allowed to be set to Cassandra client connection port (rpc_port).

  • If any value other than 9160 is set to the Cassandra client connection port (rpc_port), error logs would be generated in volume.
    Moreover, new node would not be possibly detected. Please always set 9160 to the port.

8.4.1.16. For Mobile Safari on iOS7.x or before, it takes time to display the user search dialog.

  • For Mobile Safari on iOS7.x or before, only 1 connection is permitted at a time.
    Since commet communication (long polling) is used for IMBox, it takes time to display the user search dialog.
    This symptom is observed if the conditions below are met :
    • Devices with iOS7.x and before (not applicable for iOS8)
    • Mobile Safari is used
    • Client Type is PC
    • Setting is made to use Commet Communication (default setting)
    This problem can be avoided by turning OFF the use of commet communication.
    For the setting methods, please refer to [Configuration File Reference]-[IMBox Setting].

Table Of Contents ≪  8.4. Application 8.4.2. IM-Workflow  ≫

Copyright © 2014 NTT DATA INTRAMART CORPORATION

⇄ Sidebar ↑Top