Appendix 2. Restrictions
SVF Cloud Designer Version 9.2 has the following restrictions:
Restrictions
When you are editing a form layout with SVF Cloud Designer, an error may occur if another account:
Edits the same form layout with SVF Cloud Designer
Imports a form layout on the Resource screen in SVF Cloud Manager
Additional restrictions apply when outputting forms to an Excel file. For details, see "Notes and Restrictions" - "Form layout creation tool" - " SVF Cloud Designer" - "Output to Excel file" on the next page.
https://repo.svfcloud.com/manual/release/en/manager/index.html
The following are proportional fonts, so you need to design items in the graphic mode. Also, they cannot be output on models that do not support the graphic mode.
MSP Mincho
MSP Gothic
IPAmj Mincho
Arial
Times New Roman
Arial Unicode MS
SVF Cloud Designer Version 9.2 cannot be installed on a computer that has any of the following products installed:
SVF Designer Version 6.X
SVF output engine version 9.1 and earlier
SVFX-Designer Version 9.2 and earlier
The items of "Move field" and "Batch field creation" that could be created with SVF Designer cannot be designed with SVF Cloud Designer. If you upload the FRM form file containing "Move field" or "Batch field creation" item set with SVF Designer into SVF Cloud Designer, the items are processed as follows:
Move field: The items are deleted when the file is uploaded.
Batch field creation: The fields are placed as individual fields but the batch creation attribute is deleted.
SVF Cloud Designer does not have the item grouping feature, which is available in SVFX-Designer.
Therefore, if you upload an XML format file in which items are grouped with SVFX-Designer into SVF Cloud Designer, the grouping is canceled.
If you upload an XML form file that contains flow chart items created with SVFX-Designer into SVF Cloud Designer, the flow chart items are converted into spline curves and static text items.
When you open the XML format file with a text editor and confirm the coordinates of the item, the values after the fourth decimal place may be rounded off.
This does not affect output results.
Example) If you place a field "Field1" in an XML form file
X coordinate when the item is saved in SVFX-Designer: x="3879.9999999999995"
X coordinate when the item is saved in SVF Cloud Designer: x="3880"
"3880" is the coordinates confirmed by opening the XML format file downloaded to the client machine with the text editor after saving in SVF Cloud Designer.
If more than one user edits one form definition simultaneously, the edited content of the last saved user will be reflected.
The following restrictions apply when using an embed form:
Font
When a font name added to a child form does not exist in the parent form, items specified with that font in the child form have their font changed to the first font in the parent form font list.
Color palette
When a color added to the child form does not exist in the parent form, items specified with that color in the child form have their color changed to white.
Additional layer
When a layer added in the child form does not exist in the parent form, items placed in that layer are not shown.
When the settings information is different for parent and child forms, the following parent form settings apply:
Show/hide layer settings
PDF layer settings
Paper properties
Font setting
Color palette
Page color
Barcode element size
Resolution
When the resolutions of the parent and child forms are different, output is matched to the parent form resolution.
Having items with the same name in both a parent and child form is not supported.
Parent and child forms both including form copies are not supported.
A parent form with a child form configured cannot be referenced as a child form.
Up to ten form definitions can be added to an embedded form.
SVF Cloud Designer cannot be installed in a file path that includes full-width characters.
See the support site for combinations of server and client Windows OS locales that are guaranteed to operate.
If you create an XML form file in Korean using SVFX-Designer Version 1.1 and then upload and open it in SVF Cloud Designer, the notation of the font list is changed.
SVFX-Designer Version 1.1: Alphabetical notation ("BatangChe, DotumChe" and so on)
SVFX-Designer Version 8.1 or later: Hangul notation
In SVF Cloud Designer launched on Windows Vista or Windows 7, Thai characters in the following combination are not displayed correctly due to JRE problem.
Consonant + U+0E33 + tone mark
Consonant + tone mark + U+0E33
When you use an XML form file that contains two or more combined 2D barcodes in an SP1 environment or an environment where no support package has been applied, the operation proceeds as follows:
When the XML form file is opened in SVF Cloud Designer, the settings for 2D barcode name to append to are deleted.
If one source 2D barcode can accommodate the output data, when used in the SVF output engine, the source 2D barcode is output. If one source 2D barcode cannot accommodate it, no 2D barcode is output.
When you use an XML form file that contains a 2D barcode "DataMatrix" in an SP1 environment or an environment where no service pack has been applied, the operation proceeds as follows:
When the XML form file is opened in SVF Cloud Designer, 2D barcode type changes to "QRcode" and Version changes to "0". To use it as another 2D barcode, specify 2D barcode type and Version again.
If you set 2D barcode type to "DataMatrix" in Set Default Values for an XML form file and open it in SVF Cloud Designer, you cannot create a new 2D barcode. You need to open the file after setting 2D barcode type to other than "DataMatrix" in Set Default Values in SVF Cloud Designer Ver.9.2 SP2 or later.
When it is used in the SVF output engine, no 2D barcode is output.
If you clear the check box of "Use the numeric data editing symbols from SVF output engine" in the paper properties for an XML form file and use the file in an SP1 environment or an environment where no support package has been applied, the operation proceeds as follows:
When the XML form file is opened in SVF Cloud Designer, the settings of edit symbols specified for each form file are deleted. In this case, the symbols already set in an edit-formula or chart labels will remain as they are.
When it is used in SVF output engine, data will not be output correctly as numeric data.
When you use an XML form file that contains search fields designed for invoiceAgent Documents (cloud version) in an SP1 environment or an environment where no support package has been applied, the operation proceeds as follows:
When the XML form file is opened in SVF Cloud Designer, the settings for search fields are deleted.
When it is used in the SVF output engine, a PDF with no information for search field is created.