Cloning Widgets scoped vs. global
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2017 07:42 PM
Hi Everyone,
I have a general question regarding cloning widgets and being in the correct scope. I've tried cloning several out of the box widgets and have gotten a couple different results. Our team is working in a scoped environment, so when we clone ootb, global widgets, we will clone them in our scoped application. Widgets such as KB Category Page and KB Categories KBv3 don't appear to work when cloned in our scoped environment. When we switch to the Global scope and clone those apps, they work perfectly fine.
Conversely, the ootb breadcrumb widget can be cloned in either the scoped or global application and it works great. It's even possible to edit the ootb breadcrumb widget so cloning isn't even necessarily required to make changes.
My question is really about cloning best practices. For those of us working in a scoped environment and need to make some changes to ootb widgets:
1) Should ootb widgets work in scoped applications?
2) If so, what are we doing wrong for our scoped clones not to work as mentioned above?
3) If not, is it best practice to clone them in the Global scope and go from there?
4) Are there other ootb widgets that allow for editing like the breadcrumb widget?
5) Is it best practice to edit the ootb version of breadcrumbs or clone it to make modifications?
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2017 09:11 PM
Hello David,
To answer your question from my knowledge,
1) yes, they will work when you clone the widgets in your application scope.
2)The widgets may contain methods which may not work in application scope, You need to go through are there any methods which are not working in application scope.
3) I don't think if you clone them in global scope and you can use them in your application scope service portal unless the service portal created is a global scope.
4) there are only very few where you can edit OOTB widgets.
5) I believe when ever we want edit OOTB widgets, it's better to clone them and use from that. It's better we keep the OOTB as they are.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2017 06:30 AM
Hi Surya! To follow up on #2, how can we debug to see which methods do not work in a scoped environment? When I clone in a scoped app, the code returns without any problem so I'm not sure how to identify which portions need to be revised. Thanks again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-24-2017 07:44 PM
I dont have any document for that at this moment or in google. May be the best option would be writing log statements and test it from there.
If my reply assisted, please dont mind to answer it as correct.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2017 01:46 AM
Hello David,
If my reply assisted, Kinldy don't mind to mark my answer as correct.