Idea Summary
List of Values with parameters
Use Case
Think of an simple application with companies and purchase orders. Companies can be active or inactive.
On the order page users can only select an active company in a LOV, which shows the name. Users are also allowed to set a company to inactive in the applicaiton on a different page.
Let's say a user sets Company A to inactive, but this company is linked to purchase order 123. On the page of the purchase order, the LOV fails to display company A and instead show the ID.
The workaround we use is to pass a bind variable, if :P100_COMPANY_ID is already filled, then always show that company in the query., even when inactive. However we cannot re-use the query anymore in shared components, without directly referencing that page item bind variable.
Preferred Solution (Optional)
Please extend the Shared Components LOV to pass bind variables so that we can re-use shared component LOV's and use generic bind variables in LOV queries