Skip to Main Content
Feature Request FR-253
Product Area Application Builder
Status ROADMAP

83 Voters

Share Collections across applications

fac586 Public · Nov 16 2012

APEX 4.2 introduced global scope for application items to provide workspace-level, cross-application sharing of scalar values. Similar cross-application sharing of structured data through "workspace collections" should also be provided.

Use case:

A large system is implemented in modular fashion as several applications within the same workspace sharing the same session cookie/authentication scheme and some common authorization schemes. A per session user/module/role/organization unit look-up table should be created once on logging in to any module (app) in the workspace (for performance reasons we don't want to do this for every page view). This look-up table is used by authorization schemes, VPD, views etc to determine if users have visibility and privileges on organization unit data. Modules may have reason to use role information applying to other modules.

A per-session collection would be the easiest way to implement this, as it handles session management automatically, but it's not possible at present because the collections are on a per-session/application basis.

[Already logged as Oracle bug/ER #14196075]

This is currently on the roadmap for a future release of Oracle APEX.

Known Duplicates

Known duplicates

FR-1856
FR-1856 Make APEX_COLLECTIONS accessible globally across multiple applications sharing same session cookie
FR-3167
FR-3167 Allow to share apex collections between applications. Support apex collections at session level.
FR-2963
FR-2963 Make apex collections a shared resource among workspace apps in the same session

Comments

Comments

  • duncanmein OP 11.2 years ago

    This would be really useful.

  • bart.peeters-2 OP 9.8 years ago

    Excellent suggestion!

  • gabriel.diaz.arias OP 3.2 years ago

    This is a must. I have to copy, subscribe or centralize in apps many functionalities as apex doesn't support this. And every component you have to think a different way to do it. It would be really nice just having that cross application shared components without needing subscriptions.

  • raymond OP 2.3 years ago

    Ok we are now in September 2022. Is there any chance we are going to see this implemented?
    I understand priorities, but seriously 9 years…
    Maybe as an alternative solution you can pass the application_id as a parameter.

  • fac586 OP 2.3 years ago

    Ok we are now in September 2022. Is there any chance we are going to see this implemented?
    I understand priorities, but seriously 9 years…

    I'm still hoping to see it before I retire…although it is hard to see exactly where the difficulty in introducing it lies. 

    Regarding priority, it is worth noting that on the old feature request app this was blocked to new votes for several years, so its popularity is in fact understated.

    Maybe as an alternative solution you can pass the application_id as a parameter.

    How would that help? To maintain backward compatibility, the default behaviour would be for collections to be application-specific, and all existing code must continue to work on that basis. The change would be that collections could be declared to be session-wide on creation—presumably using a new p_scope parameter—but would then work seamlessly across multiple applications using existing syntax.

  • josepcoves OP 1.9 years ago

    Must have!

  • mohamed heba OP 3 months ago

    any update on this idea. it is there for more than 10 years, and no one knows when it is going to be released.

  • jayson hanes Admin OP 3 months ago

    If there was an update available, we'd have already posted about it or changed the status of the idea.

  • yuri.kfreitas OP 3 months ago

    It's really frustrating that this functionality is still unavailable