Sales

Get Involved. Join the Conversation.

Comments

  • Mohana Gopal Selvam

    Hi Jeffrey,

    What is the best practice to use OSN? Which license customer has to purchase to use this one? Please share any document link to see the more details about OSN.

    Thanks,

    Mohan

     

  • Judy Brocato

    Hi Hongzhi - Although you can relabel fields in Sales Cloud via App Composer,  I'd be very cautious in recommending how much a customer configures/customizes core features.  I don't know your customer's business but typically, you'd set it up "out-of-the-box" where the Contact has the relationship to the primary Account (*aka Business in your terms).  Relabeling this field almost seems redundant and would seem to be better served as a training item rather than customizing.   You can see the list of the Contact Names under the Account they belong to.   Additionally, there are downstream affects of relabeling core fields - i.e., when it comes to building reports and Admins searching for fields.  Make sure you document any changes you do make.

    #2:  relabeling the Opp to "Business Name," although can be done, does not seem like best practice either. An Opportunity has a relationship to the Account (aka Business).  So if you go to the Account, you can see the list of Opportunities. This seems like a similar training issue as above.  Would seem redundant. You could write a script to label your Opportunity Name to include the Business Name if that is what the customer is going for. Or add additional fields to the Opp layout with more detail is another option if that is what your customer is looking for. 

    If you decide to to relabel fields, you should create a sandbox in your test environment > go to App Composer > Fields and rename the Standard field.  There are all kinds of help materials on docs.oracle.com.  After you've tested, you can move changes to your Production environment.

    Make sure you think through relabeling core items as f you are integrated to other Fusion applications or plan to (I.e.,ERP,  SPM, CDM, etc.) as these changes could create downstream effects when it comes to data cleansing, reporting and analytics.  Again, make sure you document well any changes. I'd find out more from why these changes are required for your customer and determine if the changes really needed or if better-served by training.  Good luck!

  • Suellen Kohase

    Has anyone been able to create a List of Values to attach to one of the Address Attributes?

    For example, if a country has a set list of States, I would like to create a List of Values, so that when employees are selecting, the same value is stored accross without mispelling, etc.

  • John Wilson Cusi

    Excellent feature! Haven't tried it yet but I will explore on this!

    Thanks Erick!

  • Jonathan Eastwood
    • posted via email reply October 7, 2019
    • Permalink
    Its really Oracle not keeping up with their own name changes. Its actually not Engagement Cloud anymore either its Oracle Sales and Service Cloud. Think of Sales Cloud being the "Sales" aspects of the CRM being Leads and Opportunity Management and "Service" being Service Request and milestones.
    
    This should help
    
  • Erick Recio

    If your  objective is to monitor and report changes on values you can use audit trail, on a feature generally referred to as "In Context Audit". There is in fact a new sub-tab on common components that can be exposed per-object that is called "Change History" which lets you see exactly what have been the changes done. Check the video on cloud readiness

     

    1) As sales administrator ensure audit is enabled. Check the documentation

    2) optionally grant roles to the users that need access to it if the users have custom roles

    3) configure the layout on apps composer.

    Steps to enable:

    Enable the Change History subtab on the edit page of an object by using these Application Composer steps:

    1. Activate a sandbox and then navigate to Application Composer.
    2. In the Objects navigation tree, expand Standard Objects, then expand the object where you're adding the subtab.
    3. Click the Pages node.
    4. Click the Simplified Pages tab.
    5. In the Details Page Layouts region, select a layout. You can select the standard layout and click the Duplicate Layout icon to duplicate it, or select another layout. Click the layout name to edit the layout.
    6. On the Edit Simplified Details Page, scroll down through the Subtabs region and, at the end of the subtabs, click the Add Subtab icon.
    7. On the Create Subtab page, select the Common component subtab type and click Next.
    8. Select the Change History checkbox in the Add common components as subtabs to an object's details page region.
    9. Save and close to save the changes.
    10. Publish the sandbox.

     

  • John Thomas

    Hi Petr,

    The Oracle University (Learning) content in my experience has always had difficulty keeping up with the software releases.  My company had an issue where we subscribed to the Sales Cloud content, the content names were updated to indicate that the it was updated to a current release (I think it was R12 at the time) but the underlying content was still for a prior release.  More specifically, there was a fairly significant change in how Security was managed, the videos were for R11, but the links/labels indicated that they were for R12.  My advice is to just make sure that the content is current/appropriate for your release.  Updating the name Engagement vs Sales seems like it should have been done to eliminate confusion, but the critical part is to make sure that whoever is consuming this information is getting the right training.  I guess the naming confuses this a bit right out of the gate.

     

  • Mohana Gopal Selvam

    Any inputs?

  • Reghu

    We need not worry much on that name.  We just have to keep in mind they are not two different applications rather one and the same. 

  • Petr Sponer

    Thanks Reghu,

    but why is the learning missleading then?

    Thank for answer

    PSp

  • Reghu

    Dear  Peter,

     

    Oracle Engagement cloud encompasses both Sales and SErvice modules.  Sales Cloud was former name of it (with only sales module), now its Engagement cloud.

     

    Regards

    Reghu

  • Justin Scherrer

    Hi Kyle, 

    You can import update the Effective Date (user managed "Close Date" calendar on the opty page) and the Actual Close Date (system managed) on your opportunities. There is a fair bit to consider when importing data, Oracle's "Import and Export Data" guides can be found in the Help Center here: https://docs.oracle.com/en/cloud/saas/engagement/19c/administer.html

    Edited to add: You'll need to update the actual close date on the associated revenue records as well as the opportunity effective date. 

  • Krishna M S

    Support for external/mashup content in cx mobile is not supported as of now. We have an ER approved for future release but do not have ETA on the same.

  • Krishna M S

    SUI displays opportunities in the current fiscal quarter by default.
    CX Cloud Mobile application is designed to display open opportunities in next 90 days (from today).
    This is the out of the box filter on which the list of opportunities is retrieved (my open opportunities for next 90 days). If you add in the saved search will filter/restrict these results even further.
     

    Thanks

  • Fernando Paes

    Hi Rohit,

    once you add the tab in app composer, you need to use Edit Pages functionality to make it visible.

    Kind regards