Skip to Main Content

Title region

  • Examples
  • Customize rich text editor using Oracle APEX global page

Breadcrumbs

Customize rich text editor using Oracle APEX global page

The plug-in supports cross-application customizations using dynamic action defined on Oracle APEX global page.

Learn more

All dynamic actions customizing plug-in can be found in Supporting Plug-ins \ Dynamic Action

Live demo

Configure live demo

Dynamic actions definitions can be previewed in the section . Dynamic actions are executed based on dynamic action sequences, not based on order in the shuttle item above.
Listed CSS classes are applied to the page item implementing the plug-in. You can preview an item attribute Advanced \ CSS Classes in the section .

Plug-in

Requirements

  1. Dynamic action must listen to the plug-in event UC Froala Before Initialization
  2. Dynamic action attribute When \ Selection Type must be set to JavaScript Expression or jQuery Selector.

 * jQuery Selector must be one singular class name. Otherwise, the customization won't work.

Dynamic action on JavaScript Script Expression

When dynamic action attributes are set as 

  • When \ Selection Type = JavaScript Expression and
  • When \ JavaScript Expression = document

the customized instances are defined by an action attribute Affected Elements. If affected elements are not defined, all page plug-in instances are customized.

Dynamic action on jQuery Selector

When dynamic action attributes are set as 

  • When \ Selection Type = jQuery Selector and
  • When \ jQuery Selector = .className 

then the plug-in instances triggering event UC Froala Before Initialization are customized.

Ideas

  1. Utilize dynamic action Security \ Authorization Scheme to restrict customization per end-user privileges.
  2. Group customizations as dynamic actions defined on the application's global page
  3. Customize plug-ins based on application logic defined in the database.