You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No single function/API to remove the Complete trigger from all places within a Creator UI.
If you do not run the first piece of code but remove the Complete trigger using the Serialization API, the Complete trigger remains available in the Logic tab and the following exception is thrown on an attempt to setup a Complete trigger:
Uncaught TypeError: Cannot set properties of null (setting 'survey')
at e.createNewObj (survey-creator-core.min.js:2:303575)
at t.createElementPanelObj (survey-creator-core.min.js:2:531707)
at t.updatePanelElements (survey-creator-core.min.js:2:534457)
at t.onLogicTypeChanged (survey-creator-core.min.js:2:546334)
at Array.<anonymous> (survey-creator-core.min.js:2:535901)
at e.fire (survey.core.min.js:6:173545)
at t.dynamicPanelItemValueChanged (survey.core.min.js:6:831104)
at t.setPanelItemData (survey.core.min.js:11:72322)
at e.setValue (survey.core.min.js:11:26336)
at t.setValueCore (survey.core.min.js:6:363357)
The text was updated successfully, but these errors were encountered:
RomanTsukanov
changed the title
Introduce a public API for hiding the Complete Survey trigger from the Logic tab
A public API for hiding individual triggers from the Logic tab is missing
Nov 20, 2024
RomanTsukanov
changed the title
A public API for hiding individual triggers from the Logic tab is missing
A public API for hiding individual triggers from the Property Grid and the Logic tab is missing
Nov 20, 2024
Implemented
Since Survey Creator v1.12.11, you can use the following code to hide triggers from the Property Grid and the Logic tab:
History
https://surveyjs.answerdesk.io/internal/ticket/details/T20546
The following code hides the Complete Survey trigger from the Logic Tab:
The following code hides the Complete Survey trigger from the property grid:
Demo
Issues with this:
The text was updated successfully, but these errors were encountered: