8.8.1. Compatibility¶
8.8.1.1. It is necessary for the master to be synchronized for the use of compatibility module.¶
If compatibility module is used, it is necessary to do the migration from the state in whichIM-Common Master and Application Master are synchronized in version 7.2.Please refer to the Migration Guide for detail.
8.8.1.2. There are differences in the set of characters allowed between old and new masters.¶
If the data that are migrated from Application Common Master contain characters that are not permittedin IM-Common Master (such as user code), the data cannot be handled.
8.8.1.3. Limitations on Document Workflow (BPW) conform to the limitations on intra-mart Web Platform 7.2.¶
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)].¶
If [,(single-byte comma)] or [#(single-byte sharp)] is included in the process definition name or task name, error will occur on the Delegation Setting Screen.
8.8.1.5. If the screens created by iWP / iAF do not support the standard mode of Internet Explorer, screens may not work properly.¶
Internet Explorer has the following specifications:a. On Internet Explorer, if the uppermost page is displayed in the standard mode, all the IFrames in the page are displayed in the standard mode.((Reference: http://blogs.msdn.com/b/ie_jp/archive/2011/11/01/10231935.aspx (Japanese))b. On Internet Explorer, some HTML functions and DOM functions have been modified to keep consistencies with the latest standard support and browsers other than Internet Explorer.(Reference: http://msdn.microsoft.com/ja-jp/library/ie/dn467850(v=vs.85).aspx (Japanese))c. Only the ID attribute is searched by document.getElementById(). (In the older versions of Internet Explorer the name attribute was searched as well.)(Refereonec: //msdn.microsoft.com/ja-jp/library/ie/ms536437(v=vs.85).aspx (Engilsh))intra-mart Accel Platform assumes that Internet Explorer is operated in Standard Mode.Moreover, if the screens of iWP / iAF are operated by utilizing external menu linkage or by porting to intra-mart Accel Platform, it is assumed that the screens of iWP / iAF are usually displayed inside IFrame for operations.Because of these factors stated above, if the screens created by iWP / iAF do not support the standard mode of Internet Explorer, screens may not function properly.Concrete examples of screens that do not work :(1) Left and right angle brackets (<>) are used to create an element in createElement.Left and right angle brackets (<>) are used to create an element as shown in document.createElement("<div id='foo'/>").(2) In case an element is obtained by getElementById(), name attribute of the element is used for the search.The element such as <input type="hidden" name="foo" id="bar" value="baz"/> is obtained by document.getElementById("foo").In order to circumvent this symptom, please either use FireFox or modify the screen so that it works in tht standard mode of Internet Explorer.