Is cloning Best Practice in Service Portal ?

[shaik_irfan]

Hi,

we are planning to clone a Widget for changes is it a Best Practise, how it effects in future upgrades ?

[Brad Tilton · Accepted solution]

OOB widgets should be read only by default, so if you have to modify a widget the only way to do that is to clone it. I would make sure that you have it documented any time you clone and use an OOB widget and examine your list of cloned widgets every upgrade to see if the base widget that was cloned has been updated.

[vinothkumar]

Hello Shaik,

Yes you can clone the widget and make changes according to the business neeeds. One thing is during every upgrade, widget will be upgraded automatically. In that situation, you have to clone the last updated widget and include your customization in that widget, so that it won't break other functionality

[Mark Roethof]

Hi there,

It depends on your purpose of cloning?
- If it's for example just because you want to change a message, often cloning is mentioned on the community. Though... in most cases not needed, so plz DON'T! sys_ui_message is the keyword.
- If it's for changing colors/read-only/etc., often cloning is mentioned on the community. Though... in a lot of cases not needed, so plz DON'T! just have a look at overwriting CSS, for example applying Page Specific CSS.

Also rethink if you really need to clone. You will miss out on future updates. The actual out-of-the-box widget will be updated, though your cloned version obviously not. For example, during London upgrade, a lot community topics where posted about the Multi-Row Variable Set not working... actually this was just because a lot people where using their own cloned version, and missed out on the actual needed update.

Etc..

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark

---

LinkedIn
Community article list