Retire: Build a proof of concept to identify what the portal page needs from the back end to display
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hi Everyone,
Below is the requirement:
story: Retire: Build a proof of concept to identify what the portal page needs from the back end to display
-Define a sample of what the data looks like the script include needs to pass to the portal page
-Explain how the portal page will render the output
-Build a prototype script include that just returns some fixed dummy data, that has the proper format but doesn't mean anything (it is fake data). For example, see the JSON below
-Build a prototype portal page that can show the data. have the portal page invoke the script include to get the content it is showing.
-Explain whether the portal page can be invoked from an email or from a task
PFA below screenshots, does anyone worked on this kind of scenario? someone please suggest me how to proceed with this.
Thanks & Regards,
Abbas Shaik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hi @abbasshaik4
Check if these article/post helps:
1.
Understanding the data/input object in Service Portal widgets
https://www.servicenow.com/docs/r/zurich/build-workflows/workflow-studio/portal-playbook-widget.html
2. Dynamic rendering on Service Portal pages for Search Engine Optimization
https://www.servicenow.com/community/developer-forum/render-portal-widget-in-workspace/m-p/3458239
3. A Single Widget Portal Page
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti