Customer Portal

Get Involved. Join the Conversation.


  • Willie Eide
    Customer Portal 3.0, 3.1, 3.2 Deprecation Announcement105.0
    Topic posted August 19, 2016 by Willie EideGold Trophy: 10,000+ Points 
    Customer Portal 3.0, 3.1, 3.2 Deprecation Announcement

    Customer Portal 3.0, 3.1 and 3.2 have been deprecated as of May 2016.

    Customer Portal versions 3.0, 3.1 and 3.2

    The Oracle Service Cloud Customer Portal versions 3.0, 3.1 and 3.2 are deprecated as of May 2016. Customers on those versions, as well as the Customer Portal 2 version, are encouraged to migrate their Customer Portal implementations to version 3.3 or higher.

    How long do I have to migrate my customer portal implementation?
    The deprecation period for Customer Portal 3.0, 3.1 and 3.2 starts May 2016.  These deprecated versions will remain available in Service Cloud for at least 2 years prior to the actual removal of the functionality.  A subsequent announcement will be made that provides a limited time window to complete any in-progress migrations off the of the deprecated releases.

    Why are these versions being deprecated?
    In an effort to ensure Oracle provides high-quality releases it is necessary to deprecate older products so that we may be allowed to focus on new, exciting features. Oracle would like to encourage all Customer Portal users to obtain the latest release of the product.

    Are there new features in Customer Portal 3.3 and beyond?
    Customer Portal version 3.3 introduced a major feature called Community Self Service which is a native solution that allows users to communicate and collaborate via forum posts and gain insight from their peers. In addition, version 3.3 leverages responsive design principles to improve the user experience across multiple device types, adds product-based navigation and product landing pages, numerous cascading style sheet improvements and contains over 70 widget updates.

    What if I don’t migrate?
    As of this writing (May 2016) the End of Life has not been announced for any version of Customer Portal; however, we encourage all customers to consume the latest supported versions of Customer Portal as defects will not be addressed in older, deprecated versions and no new functionality will be ported back to those deprecated releases.

    Where can I go to find more information?
    In addition to your account team, the Customer Portal forum in the Oracle Service Cloud Community is a great place for questions on all Customer Portal products and functionality.

    Customer Portal 3.0, 3.1, 3.2
  • Willie Eide
    TLS 1.0 Announcement - Informing Your End Users625.0
    Topic posted September 29, 2016 by Willie EideGold Trophy: 10,000+ Points 
    TLS 1.0 Announcement - Informing Your End Users


    With the upcoming disablement of TLS 1.0 protocol for Oracle Service Cloud (see CX Answer this change, depending on your end user’s browser, may result in them receiving an error message stating that the browser they are currently using needs to support at least TLS 1.1.

    This, in the very basic form, would be confusing to most end users especially during a time when they are accessing your support site for a means to solve a particular issue. If your end users do not upgrade their browser, they will not be able to access your customer portal pages.

    The code snippet below works for CPv3 users. We are currently looking at solutions for CPv2 users.

    Therefore, the Customer Portal development team proposes that starting immediately, you modify customer/development/views/ templates/standard.php and place this code snippet (found below) at the bottom of the template file. This is needed in order to proactively address this situation before it becomes an issue. 





    TLS 1.0 protocol is known to be vulnerable to attacks and is widely considered to be an obsolete encryption method. Aside from Oracle, The Payment Card Industry Security Standards Council (PCI SSC) and the National Institute of Standards and Technology (NIST)  recommends transitioning from SSL and TLS 1.0 to a secure version of  TLS (currently v1.1 or higher).

    Additional information about TLS can be found under the "General Product Discussion" forum at

    Support for TLS protocol version 1.0 will be disabled in the Oracle Service Cloud production environments on the following dates:

    - PCI Environment: on January 31st, 2017.

    - Non PCI Environment: on May 2 - June 20th, 2017*.

    *TLS 1.0 will be shut down in Non PCI environments on a phased approach starting May 2nd and ending on June 20th, 2017.  All Customer Administrators will be individually notified on the specific date when their site(s) will be disabled from TLS 1.0 protocol.

    All versions of Customer Portal
    Code Snippet:
  • Lavish Kumar
    How to hide styling when chat is NOT available?48
    Topic posted June 2, 2015 by Lavish KumarGold Medal: 3,500+ Points 
    How to hide styling when chat is NOT available?

    So, I have added styling to chat conditional link and configured it to show only when someone is "online".

    Issue: when nobody is online, the styling is still showing up even when everything is in conditional widget, why?

    Any way to hide the styling when no one is online?

    Please see the code attached

    Feb 2014 - CP3
    Code Snippet:
  • David Saraha
    Configuring Dreamweaver access to the Customer Portal StudioAnswered47
    Topic posted August 5, 2008 by David Saraha 
    Configuring Dreamweaver access to the Customer Portal Studio

    Hello there, we're trying to configure Dreamweaver to access the ustomer Portal Studio. We've followed all the steps but get stuck when we have to log in. I'm not sure if our userid has rights to use the RightNow site?




  • Qing Liu
    Show/hide page content based on SLA37
    Topic posted August 10, 2010 by Qing LiuGold Medal: 3,500+ Points 
    Show/hide page content based on SLA

    Hi All,

    The manual of Nov 2009 indicates we can hide page content with an SLA condition. Cool, but I test rn condition tag; it does not seem to work for me.

     Here is my test code:

    <rn:condition sla="internal_US" >

    <p>The content is only showing to Agents who have internal US SLA</p> </rn:condition>.

    As I read from community (, the rn:condition SLA will only check SLA options, like  <rn:condition sla="selfservice">, <rn:condition sla="incident"> etc. It will not check SLA ID.

    If that is true, how we can show/hide contents on end users page based on SLA ID?  In my case, internal_US(17), internal_UK(18) both get different SLA ID.

    Is it some simply way to do like

    <rn:condition sla_id="17">,

    Show to US people


    <rn:condition sla_id="18">,

    Show to UK people


    I also look at SlaDiv widget, I found out that it also only reads SLA options

    Thanks you,  I am looking forward to your reply

  • Shiloh Madsen
    Filter on language?Answered345.0
    Topic posted April 10, 2009 by Shiloh MadsenBronze Trophy: 5,000+ Points 
    Filter on language?
    One of the fields in our knowledge conent items is Language. I would like to be able to use syndication to constrain on that, but I am not sure if that is possible. Are we limited to the few listed in the documentation, or can I filter by any field? If so, how do I do that? 
  • BillD415
    Creating an account from the Ask a Question pageAnswered33
    Topic posted March 27, 2009 by BillD415 Red Ribbon: 250+ Points 
    Creating an account from the Ask a Question page

    We are preparing for an upgrade to November '08 and will be switching to the Portal page set as part of that upgrade.  For 2 of our interfaces, we don't have Pass-Through-Authentication, so we need for visitors to easily create an account and log their question from the Ask a Question page.  I have followed the instructions on pages 89-91 of the Nov '08 Portal Guide to add the email field to the AAQ page so that it will create a new contact if necessary or add the incident to the current contact if it already exists.


    This appears to work in that it creates a new contact if the email address does not exist, but because it does not put anything in the "login" field in the contact record, the customer can not log in to the My Stuff pages to check on their previously submitted incident.  Is there any way to either:


    1. Have the login field added during the contact creation from the AAQ page

    2. Modify the login widget so that it looks at the email field rather than the login field?  We always use the email as our login and don't use a password for the sites in question.


    Any insight would be appreciated.


    Bill Dailey









  • Srinath Srinivasan
    Ability to view secondary contact's incident upon...31
    Topic posted October 3, 2017 by Srinath SrinivasanGreen Ribbon: 100+ Points 
    Ability to view secondary contact's incident upon logging into customer portal

    Hi Geeks,

    Can you kindly help me out with the below requirement,


     A contact after logging  in to the CP page  should be able to view the incidents where they are marked as primary contact

    and they should also be able to view the incidents where they are marked as secondary contact

    is there any way to do this?

    Your help in this would be much appreciated.

  • Kyle Snay
    Need help with my test widget31
    Topic posted August 21, 2008 by Kyle SnayGold Crown: 30,000+ Points 
    Need help with my test widget

    Okay, my widget doesn't work. I've gone through the PDF document for the Nov 07 version (see attached). The RightNow site we're using for the test is I'm just trying to create a very basic widget and that help document isn't very helpful.


    The test page for the widget can be found here: It's very basic, just a blank page with the widget. 


    I'm guessing the issue lies within the reader1.url statement but I'm following the example on page 1 of the PDF and that's what it says to use. 


    Any help would be greatly appreciated. 



  • Patricia Harvath
    incidents.created report based on user defined dates31
    Topic posted August 11, 2011 by Patricia HarvathBronze Medal: 1,250+ Points 
    incidents.created report based on user defined dates


    I need to create a report that lists all incidents created between two user defined dates.  Any idea how I go about this?



Filter by Date

< < November 2019 > >
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30

Filter by Type