2.2.6 Notes on creating the Operational Content for iPad

(1) Parts that cannot be used for the Operational Content for iPad

Do not use the parts described below for the Operational Content for iPad. If any of the parts are used, operation of the Operational Content is unpredictable.

• HTML parts

• Automatic Operation Window URL Creation Plugin part

  This part, however, can be used to access the window to confirm task status for the Operational Content for iPad.

• JP1 Event Status Change Plugin part

• JP1 Event Information Output Plugin part

• Service Support Window URL Creation Plugin part

To Page Top

(2) Parts not to be used for the Operational Content for iPad (recommendation)

The parts describes below are subject to restrictions on setting and operation. Therefore, you must pay special attention to and check whether these parts are displayed normally on an iPad. We recommend that you avoid using these parts if you can substitute other parts instead.

• Text box part

• Text area part

  In a text box or text area, you cannot move the cursor to a position that is not currently shown. Therefore, the text box or text area must be big enough for the assumed number of characters to be input. You might have to set a maximum string size for the text box or text area.

• Inline frame part

  The buttons and links displayed in an inline frame are ineffective even when they are tapped. Also, because the file content displayed in an inline frame cannot be scrolled, the inline frame must be big enough to display the entire file content without scrolling. Note that an inline frame cannot display a Web site specified for it if the settings of the Web site do not suit the Operational Content.

To Page Top

(3) Parts that appear differently on the iPad

The appearance of the following parts will vary in size and design depending on whether Microsoft Edge or Google Chrome is used, or Mobile Safari.

• Image part (including the image displayed for a Process Node)

  • When an image is displayed by Mobile Safari, the image quality might deteriorate. If this occurs, disable the change of image size, or specify an image that is twice as large as the original image.

  • When the image file at a specified URL cannot be accessed, Microsoft Edge or Google Chrome displays an icon indicating that there is no image. In the same case, Mobile Safari displays only borders of the image part.

• Text box part

• Text area part

• Radio button part

• Check box part

• Drop-down part

  Drop-down parts displayed by Mobile Safari are larger than those displayed by Microsoft Edge or Google Chrome. Make sure there is enough space between drop-down parts and other parts.

• Inline frame part

  • Even if you specify the setting to display frame borders for an inline frame, the right and bottom borders of the inline frame are not displayed by Mobile Safari. Also, inside the inline frame, a 3-pixel wide area is hidden at the right and bottom edges.

  • If the file at a specified URL cannot be accessed, Microsoft Edge or Google Chrome displays a page indicating that the specified Web page is not found. In the same case, Mobile Safari displays nothing.

    Be particularly aware that if you specify the setting to hide frame borders (in the Attribute Setting window by clearing the Insert frame border check box), nothing will be displayed at the inline frame part.

To Page Top

(4) Part setting that is ineffective for browsing on iPad

You can set tooltips for image and hyperlink parts. Note, however, that tooltips are not displayed when the Operational Content is browsed on an iPad.

Use only images that do not require tooltips. For hyperlinks, you need to take measures to enable the link destination to be known from the anchor string alone.

To Page Top

(5) Characters that are displayed on the iPad

MS PGothic characters displayed in Microsoft Edge or Google Chrome are displayed as Hiragino Kaku Gothic characters on Mobile Safari. Hiragino Kaku Gothic font character widths and line spacing are generally larger than MS PGothic font. Therefore, design character display areas that are large enough to display these fonts. As an approximate guide, such areas must be double the width and height of the same part created for browsing by Microsoft Edge or Google Chrome.

To Page Top

(6) Setting required when creating the Operational Content for iPad in an environment that allows direct transitions between nodes

When you create the Operational Content for iPad in an environment that allows direct transitions between nodes, you must specify a value less than 70 as the setting of Front/back order for each Process Node. If 70 or more is specified, clicking Process Nodes might be ineffective when the Operational Content is browsed on an iPad.

To Page Top