nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Hide one new web form option in my web forms portlet

MAK

Hi All,

TeamSite 6.7.2 / Win 2k3.

I have few web forms (templates) specified in templating.cfg and as expected visible on My Web Forms portlet on the standard interface.

My requirement is to hide one of the web form entry in the My Web Forms portlet. Any ideas ??

Help much appreciated.

Regards,

Find more posts tagged with

Comments

Jamik

why do you want to hide it?

MAK

That is a business requirement.

We do not want people to add new content but use the existing conent.
So they can go the data folder and edit the DCRs but cannot create new from the my web forms.

nipper

Well an easy way is to use FormAPI to prevent a new DCR from being created.

MAK

Well an easy way is to use FormAPI to prevent a new DCR from being created.

thanks for response, yes we can do that so that no new DCR is created.
But the requirement here is to hide the option at the home page to avoid confusion Smiley Sad

Jamik

Personally, I think that's terrible IA if you have templated content that users can edit but not create new. I would push back on this requirement if it were me.

If they really want to do this still, about the only way you're going to get this done is by restricting those users to CCStd interface and removing the OOTB template portlet and creating a new one to replace it with that you can then specify how it's going to display. Of course, you'll also have to either remove all links for the create new templated content as well and/or replace them with a custom one. To me that sounds like an awful lot of work for a business requirement that is severely flawed.

If they really need this you're better off doing the nipper approach and live with the confusion.

MAK

Thanks all for your feedback.

As this cannot be done easily and definitely not worth doing the custom portlet thing, best thing is "Train the users to avoid confusion".

Regards,

AlternatingCrosstabRowHighlight.rptdesign