Skip to main content

Configuration Pre-Requisities

The supporting dynamic action plug-in allows Rich Text Editor Pro customization using Oracle APEX dynamic action interface. This document covers topics related to changing plug-in settings before plug-in initialization on page load.

A dynamic action changing plug-in settings can implement multiple true (or false) actions. This feature allows having all plug-in customizations in one dynamic action and make it conditional due to PL/SQL logic or Oracle APEX authorization schemes.

Oracle APEX Global Page 0

The dynamic action plug-in can be implemented on Oracle APEX Global Page to customize cross application plug-in instances. Learn more in guide Oracle APEX global page.

Dynamic Action Attributes​

The supporting dynamic action integrates the following dynamic action attributes:

  • Event
  • Wait For Result
  • Stop Execution On Error
  • Initialization JavaScript Code

Event​

A dynamic action customizing the plug-in settings must be must be listening to the plug-in event UC Froala Before Initialization. Dynamic action triggered on other events has no effect on the plug-in settings.

Triggering Element​

A dynamic actions customizing the plug-in can be triggered by DOM node as long, the triggering event is UC Froala Before Initialization.

Recommended triggering element

The recommended triggering element is JavaScript Expression document. Use dynamic action affected elements to filter page item(s) to be customized.

Client-side Condition​

The plug-in monitors which dynamic action branch (true or false) is not rendered due to evaluation of dynamic action attribute client-side condition.

Server-side Condition​

The plug-in monitors whether dynamic action is not rendered due to evaluation of dynamic action attribute server-side condition.

tip

Using server-side condition allows building custom plug-in customization based on PL/SQL logic.

Authorization Scheme​

The plug-in monitors whether dynamic action is not rendered due to evaluation of dynamic action attribute authorization schemes.

Action Control List

Using authorization schemes allows building custom plug-in customization based on user's role in an application. Learn more in guide Action Control List support using dynamic action server-side conditions and dynamic action authorization schemere.

Action Attributes​

Wait For Result​

The plug-in dynamic actions supports dynamic action attribute Wait For Result allowing a developer to create custom success flow using dynamic actions.

  • When Disabled - a next true (or false) action is executed immediately.
  • When Enabled - a next true (of false) action is executed only after the plug-in action is finished.

Stop Execution On Error​

The plug-in dynamic actions supports attribute Stop Execution On Error.

  • When Disabled - when the plug-in action raises an error, a dynamic action execution continues, and next true (or false) action is executed
  • When Enabled - when the plug-in action raises an error, a dynamic action execution is terminated.

Affected Elements​

The supporting dynamic action plug-in supports the following affected elements:

  • Not set
  • Item(s)
  • jQuery Selector

Not Set​

When action attribute affected elements is not set, the dynamic action affects all page items implementing the Rich Text Editor Pro.

Item(s)​

When action attribute affected elements selection type is set to Item(s), the dynamic action affects only named page items implementing the Rich Text Editor Pro.

jQuery Selector​

When affected elements selection type is set to jQuery Selector, the dynamic action affects page items implementing the Rich Text Editor Pro matching a given jQuery selector.

For example, jQuery selector can be page item class name defined in page item attribute Advanced \ CSS Classes.

Initialization JavaScript Code​

Check each plug-in dynamic action whether it uses the dynamic action attribute Initialization JavaScript Code.