I have enabled fast checkin on WCC through adding useFastCheckin=1 as an addition configuration variable.
However, now when users upload documents to WCC through the Siebel Iframe, the documets are not displaying on the Iframe after being uploaded.
The document is available in WCC if you search for it but no documents are visible in the iFrame.
Then when removing the useFastCheckin=1 on WCC, the documents display on siebel iFrame as normal.
Does anyone have a solution for this to allow for WCC to use fast checkin and show the documents on the iFrame?
I managed to find a solution to the issue that I was facing in my above question.
I added the following two additional configuration variables to WebCenter Content General configuration:
UseSearchCache=false
SearchCacheMaxItemAgeInMinutes=0
and voila problem solved.
Related
Background Information
Content Search Web-Parts supports a caching feature as described here: https://support.office.com/en-us/article/Make-pages-load-faster-with-caching-in-the-Content-Search-Web-Part.
This should bring enhanced performance.
Problem
When configuring caching as described in the article the Content Search Web-Part does not return any results.
Steps to reproduce
Insert a Content Search Web-Part into a page
Edit the query (for testing purposes here: Recently changed items)
Under Settings activate the option caching for everyone except external users
After saving and publishing the Content Search Web-Part does not return any result. This is reproducable in multiple tenants.
Solution
If you want to enable caching for a security group, this security group requires permissions on the site collection (min. read permission).
In my case "Everyone, except external users" had no read permissions on the site collection.
I have a plugin that fires on PreOperation of RetrieveMultiple and adds a query condition that the view name does not begin with HIDDEN_ . In the web client this works perfectly. In my on prem Outlook client (for my sandbox) it also works perfectly. However when I am using Outlook 2010 with an online environment it still displays the hidden view in the drop down (but not if you open an advanced find).
On top of this issue I also am unable to prefix my dashboard views with HIDDEN_. If i do then the dashboards display no information. I haven't been able to get it to work properly with the dashboard views, but I need to hide them as I have two entities that have a dozen views each that are only used for the dashboards.
In short these are the two questions:
1. How do I hide views for an online 2011 environment in the outlook client?
2. How do I hide the dashboard views and still use them for the purpose of creating dashboards?
Thanks,
Nick
Try registering your plugin on the PreValidation step.
Of course, all clients should show exact similar behaviour, so to me it seems you have found a bug.
I have developed a website which runs at SSL (https). I want to open some SSRS reports at the website in an iframe. But it is not opened since browsers say that "Blocked loading mixed active content" in the browser's console.If I hit report's URL in another tab or another browsers window then it opens.Also if I run my website at http only then browser opens the report in the iframe perfectly at the website.I think this problem is arises since website runs on https and report url is http only.
What can I do to resolve this issue without change in any of the URL.
Thanks in advance.
What version of SSRS are you using? It is possible to install multiple instances of SSRS on the same machine. They may not have access to the same sets of reports, but I'm not sure if that would even be an issue for you. The configuration you are attempting seems a bit messy. Personally I would try to get all of the sites on SSL to be consistent, but that sounds like you may not be able to achieve that, politically.
Anyway, here's a link to get you started with the multiple SSRS instance approach, if you'd like to try it.
http://technet.microsoft.com/en-us/library/ms403426(v=sql.90).aspx
I have a Liferay portal custom theme, which is embedding a portlet in the left-side section through some standard Velocity code in portal_normal.vm. When I first embedded the portlet, I set the property portlet-setup-show-borders-default to "false", which caused the portlet to render without the title bar or other "chrome" (which is not what I wanted).
I changed the property value to "true", but what I found is that on the pages where I had already loaded the portlet, it continued to render without the borders and "chrome". If I loaded a different page, however, the portlet then rendered correctly.
How do I force Liferay to re-draw the portlet correctly on those first pages that I had visited? I can't find anything in the Admin GUI (which is what I'd prefer) that might force some cached copy of it to be cleared, and a lot of Google searching hasn't showed anything that works, either. I had found one article that looked like it might work ( http://www.liferay.com/community/forums/-/message_boards/message/772138 ), but the code posted by Artur in the second comment doesn't work for a general portlet, just the Web Content portlet and articles.
Has anyone else run into this and found a solution? Please let me know ASAP!
Thanks in advance
-- Joe --
Finally found the information I needed on Liferay's community forums site, though it required a very specific search term in Google to locate it. Sharing the information here so others will have it more readily (I hope).
When a portlet is embedded in a theme, each page that's loaded for that theme has the VelocityPortletPreferences settings stored in the PortletPreferences table of the database. Even if you change the preference settings inside the template code for your theme, Liferay will ignore the change and use the stored preference values from the DB. The only way to clear out these stored values is to delete the rows in the PortletPreferences table corresponding to your portlet's ID.
delete from PortletPreferences where portletId = '<your-portlet-id-here>'
Once you've done this (no restart of the Liferay service is needed), you can reload the pages that were not displaying properly and they will now pick up the updated preference settings.
Note that the updated preferences will once again be stored in the database after you reload the pages, so if you need to make another change, you'll have to delete the rows for that portlet once again.
I'm having a strange problem and no luck debugging.
I was tasked with writing a JSR168 compliant portlet to search a database. When you open the portlet, you're given 6 search boxes for different criteria to search several thousand records. Once you press search, it brings up another page (it keeps the first page and uses <jsp: include> for the second page so users can see/change their search terms) with the search results. From the search results page, the user can click on one of the results (which redirects to a new page) and get more detailed information about it.
All of that works. The problem is when the user wants to search again.
When I developed this, I used LifeRay installed on my local machine. Everything works perfectly in IE, Firefox, and Chrome. However, when I deploy it to our development portal (IBM WebSphere), it doesn't quite work in IE. In Firefox/Chrome, when a user is on the detailed information page, they can hit back on their browser and it loads a cached version of the search results. Perfect, because this content rarely changes.
However, in IE, when they click the back button on the detailed view, we get a "Webpage has expired message". I've tried every caching setting in the portal settings for the portlet as well as the page, but haven't had any luck.
Anyone have any ideas?
There are settings at the portal level too.
Check out following link
http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/index.jsp?topic=/com.ibm.wp.ent.doc/wps/adbakbut.html
You could try tweeking some of these paramters as required by your portlets
The "Webpage has expired message" in IE indicates that you did a POST. You could try using a GET, which should not have this problem on "back" command.
You should install WebSphere Portal on your developer machine and test locally before going to another environment.