Skip to main content

Home/ BI-TAGS/ Group items tagged javascript

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
cezarovidiu

Saving Current Values with Cascading LOVs - 0 views

www.danielmcghan.us/...ent-values-with-cascading.html

apex cascading lov

shared by cezarovidiu on 05 Jan 14 - No Cached
  • cezarovidiu on 05 Jan 14
     
    "Saving Current Values with Cascading LOVs A friend, Monty Latiolais, recently asked an interesting question regarding cascading LOVs: Say you've got two LOVs...STATES and CITIES. They both default to 'ALL' and 'ALL'. Since CITIES is dependent on STATES, as soon as STATES is changed, CITIES is blanked out. What should happen is that CITIES gets re-evaluated as in the following example... let's say STATES is ALL and CITIES is "Houston". If one then changes STATES to "Texas", CITIES should remain "Houston" as that is a valid value for CITIES. So basically, is it possible to maintain the selected value of an item if that same value exists in the list of values after refreshing? That's a great question! Thanks to new events in the APEX framework and Dynamic Actions the solution is far easier than it would have been in the past! Click here to see the demo but continue reading to learn how it all works… There are a three main events you need to be concerned with when it comes to cascading selects: change apexbeforerefresh apexafterrefresh The change event is a standard part of JavaScript and the DOM. This event fires when the user manually changes the value of the select list but can also be triggered programmatically via JavaScript. The apexbeforerefresh and apexafterrefresh events are custom events in the APEX framework. They fire just before and just after AJAX requests refresh something on the page. The events work with many items and regions that utilize this technology. In this example we have two select lists: parent and child. If you change the value of the child select list then the change event will fire and that's it. But if you change the value of the parent select list a lot more happens to the child select. Here are some of the highlights: The current LOV values are cleared out The apexbeforerefresh event is triggered An AJAX request brings back new values. This only happens if optimize refresh is set to false optimize refresh is set to true and
cezarovidiu

Adding Extensions to the Layout Editor - 11g Release 1 (11.1.1) - 0 views

docs.oracle.com/...layout_ed_ext.htm

obiee setup extensions

shared by cezarovidiu on 08 Oct 13 - No Cached
    • cezarovidiu
      cezarovidiu on 08 Oct 13
       
      /middleware/user_projects/domains/obi/config/bipublisher/repository/Admin/Plugins
  • To implement a plug-in: Code the JavaScript plug-in using the guidelines described in Section 11.3, "Coding the Custom Plug-in." Place the JavaScript (.js) file in the following location <BI Publisher repository>\Admin\Plugins. Reload the Layout Editor. Your plug-in icon appears in the layout editor Insert menu.
cezarovidiu

Add colors or images to your select list | Inside Oracle APEX by Patrick Wolf - 0 views

www.inside-oracle-apex.com/-or-images-to-your-select-list

apex javascript list

shared by cezarovidiu on 14 May 14 - No Cached
  • cezarovidiu on 14 May 14
     
    "style="background-color:red'"
cezarovidiu

Main - 0 views

apex.oracle.com/...f

apex blog examples tabular-form

shared by cezarovidiu on 20 May 14 - No Cached
  • Tabular Tabular Column Validation Limit Length of Text Field Entry Tabular Form's Column Read-Only and No Duplication Tabular with Popup When Hovering Over Column Identify Column ID of Tabular Form Javascript News Ticker Popup Window Checkbox to toggle show/hide a region Tooltip APEX Built-in Tooltip Box Over Tooltip Page Page Load Time
cezarovidiu

Difference between CRM lead and an opportunity - Pipeliner CRM Blog - 0 views

blog.pipelinersales.com/...en-crm-lead-and-an-opportunity

CRM documentation blog

shared by cezarovidiu on 31 Mar 15 - No Cached
  • Any individual fish or pod of fish in your sea represents one lead.
  • Your Nemo will not be the first or the second fish that you catch. At the beginning, you will have very little information about the Nemo you would like to catch. You will start to examine your fish and create some criteria as to how Nemo should look like. In other words, you are qualifying your fish.
  • Lead = Any Fish in The Sea. Opportunity = Nemo
  • ...6 more annotations...
  • The process of examination and adding the criteria represents your sales pipeline strategy. It’s always true that: “Without a commitment to pursue working together (something that results in this company potentially buying from you) there is no opportunity.” - Anthony Iannarino
  • At the end of your examination ie. of your sales process, you will either let the fish swim back into your sea (lost opportunity) or you will put Nemo into your aquarium (won opportunity). Won Opportunity = You have found Nemo Lost Opportunity = You have not found Nemo
  • A Lead – is a contact or an account with very little information. It could be just a person who you might have met at a conference. You will need to retrieve more information regarding this lead in order to create (qualify) an opportunity in your sales pipeline.
  • A old sales rule says: “If you have never contacted your contact, it’s a lead.”
  • An Opportunity - is a contact or an account which has been qualified. This person has entered into your buying cycle and is committed to working with you. You have already contacted, called or met him and know their needs or requirements. The old sales rule says: “The opportunity is a deal that you have the possibility to close!”
  • “Think about the difference between a lead and an opportunity as an evolving process i.e. each lead needs to be qualified to an opportunity. There will always be plenty of leads in your sales territory, but only few of them will qualify to become real sales opportunity.”
1 - 11 of 11
Showing 20▼ items per page