Hello Developers/ @Pradeep Sharma / @Ankur Bawiskar / @jaheerhattiwale
This is regarding one of the issue I am facing from the portal side.
I am calling a flow action using "GlideFlow.startAction('action_name', inputs)" from the catalog client script (onChange)
My changes are working fine if I am testing the catalog request form via "Try it" button which is available on catalog backend form.
But if I am testing the same catalog form from the portal end , my changes are not getting reflected on the portal view and when I inspect the page , it says "GlideFlow is not defined"
I have referred this solution provided by Pradeep in this thread - https://www.servicenow.com/community/now-platform-forum/how-do-i-add-the-glideflow-library-as-a-depe...
But I can see my platform is already having these records but still I am receiving the glideflow error.
Only thing is field" Portals for page load (optional) " not having any value added.
@Pradeep Sharma : your solution is not working provided in the above mentioned thread.
I have not tried the other approach suggested in the same thread by other developer i.e.
Step 1: (as per Pradeep)
a. Navigate to sp_js_include.list
b. Create a new record with the below parameters.
Display name:/scripts/GlideFlow.js
Source: url
c. JS file URL:/scripts/GlideFlow.js
d. Submit
Step 2:
Go to Portals > Select portal you are working with > Theme (Click through and go to the Theme record) > Related Lists > JS Includes > Add the above file GlideFLow.js which we created in Step 1.
Final screenshot where you have to add a JS include
Can someone let me know the best solution for this issue and why it is not working on the portal side while on the other hand the same changes working via "Try it" option.
Thanks !
@Rahul84 Select UI Type as All in client script
Please mark as correct answer if this solves your issue.
