When different people with different roles within APEX can view the same report, you need to ensure they can only access the information they are privy to. Sounds straightforward, but in some situations, a simple right-click and “inspect” could represent a security risk. In this week’s Instant Tips, Anton and Hayden each present their way of building conditional edit links when creating a report. After all, you can’t rely on CSS to enforce your security.
The episode also includes a cool off-topic tip on how to move a link from your computer to your phone using Chrome!
Enjoy!
View Past Episodes
Full episode list on YouTube here.
Past Episodes
APEX Instant Tips #148: Protect Ajax Callback processes from hacking
Last week, we made it easy to use Ajax Callback processes. This week, we show how...
Read moreAPEX Instant Tips #147: Why are Ajax Callback processes so hard to use?
Ajax callbacks are hard to use: Learn the javascript and be careful about syntax. Marwa and...
Read moreAPEX #146: APEX Instant Tips #146: Extending Faceted Search
Hosts Anton and Marwa talk about how to make a page item look and behave like...
Read moreAPEX Instant Tips #145: How to know if the data in your Interactive Grid row changed
:APEX$ROW_STATUS is a pseudo column that can be used in PL/SQL, just like any other interactive...
Read moreAPEX Instant Tips #144: When to_date
To_date, To_number, and To_timestamp stem from how APEX stores and treats Session State. Anton and Marwa...
Read moreAPEX Instant Tips #143: Javascript and css from pl/sql
In this episode, Marwa and Special guest Eglé describe how to add javascript code and CSS...
Read moreAPEX Instant Tips #142: LOV additional columns
Michelle sits in for Anton this week as Marwa shows you how to leverage additional columns...
Read moreAPEX Instant Tips #141: The APEX qAsk application
The APEX qAsk application can be used for live surveys. Anton and Marwa demonstrate and point...
Read more