Clarity

Hi All,

We recently added 2 new fields to a portlet and added them to the Filter section and the list section.

All the users are able to view it in the List Section.

The newly added fields are available in the filter section only for few users.

Others are not able to view the newly added fields in filter and unable to configure manually as well.

While configuring the fields manually the users are not able to save after the new field is added.

Thanks in Advance

Regards,

Anusha

Hi Anusha,

Did you publish the portlet?

Regards

Suman Pramanik 

Hi Suman,

It is actually visible to few users.

Do we need to publish the portlet when we add new fields as well.

I was under the impression that we need to publish it only when we update existing fields.

Regards,

Anusha

if you make any changes to the portlet which needs to be cascaded to other people needs to be published. Its same for object/views too 

I am able to view the newly added fields when i login using another account.

If the portlet has been customized by any user, those users will see their customized version of the portlet instead of the object version.

If you make any changes on the object side, those users will not see the change unless:

• User "Restore Defaults" for the portlet (Options > Configure > General > Restore Defaults
• Admin "Publish" the portlet for every user. All user will now see the version that has been published.

Regards

^  A user with the pre-configured version of a portlet should still be able to add (i.e. "Configure") any new fields into their personal configuration of that portlet (and Anusha stated that they could not).

Often "Restore Defaults" and/or "Publish" on a portlet view is undesirable because of users' personal configurations.

You're right, if this is the case, I would suggest to open a new case with CA Support...

Regards

users generally get quite grumpy if they com into the office and see that their portlet configuration has changed.  We updated a portlet at work and had to publish the changes. About 800 PM's were quite unhappy.

XOG out the portlet and XOG in back. This works sometimes. Please try if not done already.

That typically works when you have the filter figured on the admin side, but you cannot see the same in the application no matter whether you publish or restore defaults. Though sometimes you can see those fields in the list of all filters fields while you cannot see them as selectable.

If you are in a multi-app-server environment, then the changes might not have propagated to the other app servers (they should do if everything is configured right, but everything isn't always configured right!).

Restarting the app services (the ones where you don't see the portlet changes) would correct that.

The users who do not have the new fields could also try restore defaults in  the portlet configuration of the the user.

That is if they have made user modifications to the portlet.

We have had to raise several cases with CA support where we were experiencing multiple issues related to 'broadcasting' between the app servers (14.4).

A couple of patches had been released (I am not sure whether it is covered in patch 4, 5, or 6) to address these issues. Once we had deployed patch 6, we saw this issue pretty much go away.

This was extremely frustrating as there was no monitoring being triggered through OnDemand to say that this issue with the infrastructure had occurred. It was only after we published updates to our configuration and numerous users complained that they could not see this config that we discovered there was an issue, and investigations through CA Support narrowed it down to 'broadcasting' between app servers. 

This is known issue in clarity. The newly added column may not available in Filter section but available in List Layout.

Please xog-out entire portlet and rexog in again. The newly added column should be available in the filter section

Thanks

Senthil

Thank you. I was unaware it was a known issue.

See

Issue adding filter columns to portlets 

Georgy 

posted another solution, but I cannot locate it now.