Idea Summary

Passing multiple parameters to a Popup LOV on an APEX page can be cumbersome. Currently, we often rely on shared components and pre-defined LOVs, which:

Makes reuse difficult when we need context-specific filtering.

Requires multiple dynamic actions and page items to differentiate LOV behavior in regions with similar structure.

Leads to maintenance challenges and page bloat when overused.

Use Case

When a page has two regions (e.g., "Customer Details" and "Guarantor Details"), and both require a Popup LOV with slightly different filters, it becomes challenging to reuse the same LOV efficiently. This forces developers to duplicate lists or overload dynamic actions.

Suggested Improvement:

Enable the definition of dynamic, inline LOVs with the ability to bind multiple page items as parameters directly within the LOV configuration.

Allow parameter passing based on region scope or DOM context, reducing conflicts when similar LOVs exist in multiple regions.

Introduce smarter LOV templating, where one LOV definition can serve different contexts dynamically via conditional filters.

Benefits of  Solution (Optional)
Streamlined development and better reuse of LOVs.

Fewer shared components and reduced page overhead.

Easier to maintain and debug region-specific behaviors.