Frequently asked questions about the SkyVisualEditor V17.2 release are answered.

・The dialogue components used in SkyVisualEditor have been changed and the appearance of the dialogs has changed.
　There are no changes to the functional aspects.

・This means that the following native API dialogue components of the web browser are no longer used by SkyVisualEditor and are replaced by SkyVisualEditor's own dialogue components created with jQuery.

　　　window.confirm, window.alert, window.prompt

■For Example) confirmation dialogue in Free hand input item

・This is due to the planned end of support for cross-origin use of the native APIs of dialogs (window.alert, window.confirm, window.prompt) in various web browsers (e.g. Google Chrome and Safari).

・Although a detailed schedule for the end of support for each browser and the target version has not been announced If you use a web browser after the end of support without installing V17.2,

　it will affect the operation of the browser, so please consider installing it as soon as possible.

・The following is the official Salesforce page for reference.

　　- Prepare for New Alert, Confirm, and Prompt Modules and Components

　　- Preparing Your Components for the Removal of alert()/confirm()/prompt()

【During an upgrade operation】

・When upgrading to V17.2, if you are executing the display of dialogs (window.alert, window.confirm, window.prompt) in Page scripts,

　you need to rewrite the page script must be rewritten to call the SkyVisualEditor original dialogue components.

・Please refer to <(1) Rewriting of Page scripts in V17.2 >.

【After upgrade】

・As mentioned above, the appearance of the dialog will change as a result of the change in components,

　but There is no change in functionality, so there is no particular impact after implementation.

・The installation procedure is the same as before, but as mentioned above, it may affect the processes implemented in the page scripts.

　Please be sure to verify this in the Sandbox organisation before moving to the production organisation.

　　　1.  Upgrade of the installed package of the Sandbox organisation to version number 17.2.

　　　2.  For each page created in Studio, check & correct the impact on the page script implementation process and deploy to the Sandbox organisation.

　　　3.  Operational testing in the Sandbox organisation.

　　　4.  Implementing the transition from a Sandbox organisation to a production organisation.

・Yes. After the release of V17.2, you can continue to use V17.0 (package version 17.1) in the latest environment until the next major version upgrade (V18.0).

・It is possible to deploy from V17.2 Studio for Windows to a Salesforce organisation with V17.0 (package version 17.1) installed.

    Please deploy V17.2 at your convenience.

・The product version became V17.0 in the 2022/7/17 upgrade, but the version of the SkyVisualEditor VF AppExchange package became V17.1 in accordance with the Salesforce specification.

・The package and product versions have been unified at V17.2 in order to resolve the version numbering discrepancy in this release.

・Therefore, product version V17.1 does not exist.

・SkyVisualEditor LC is not affected.

* In V17.2, SkyVisualEditor LC has improved authentication settings for the Slack component.

　For more information, see the SkyVisualEditor LC help page.