Skip to Main Content
Feature Request FR-3920
Product Area Shared Components
Status OPEN

22 Voters

Shared Component to Create a Common Page and Subscription

aschultz Public · Jul 23 2024

Idea Summary
I wish there was a section in Shared Components that allowed users to create a page that any app could add or add and subscribe to.

Use Cases

  • A workspace that contains 20+ apps for a manufacturing company
    1. There are apps to manage inventory, pick and place stock, review completed parts for quality assurance, etc…
    2. There is a page that is created and used for every app.  This page allows users to search for parts to get more information.
    3. To fulfill this request, we are currently creating the page in one app, and then copy that page into each app.  However, whenever a change is required, we have to add that change to every app.
  • A workspace that contains 15+ apps for tracking donations and their associated funds
    1. Similar to the manufacturing example, there is a common page used for all the apps.  The difference is that there are 4 common pages (with subtle differences) used to search funds and gifts.
    2. The subtle difference include different levels of access, different data sets, different search criteria, etc…
    3. We know that in the future, more apps will be needed, and it would be great to have pages to subscribe to in Shared Components to help manage existing apps and add a common page to new apps.

Preferred Solution (Optional)

  1. I would imagine an extra link (called Common Pages) added to Shared Components in either the User Interface section or Other Components Section.
  2. When the link is clicked, it brings the user to a screen similar to the Authentication Schemes report.
  3. A user can view / edit the pages that already exist or add a new page.
    • Clicking on a Create Page button brings the user to page designer
    • Clicking on an existing page brings the user to a page that gives users the option to edit / delete the page, view / edit the subscriptions, and publish changes (similar to when you click on an Authentication Scheme).
This idea is open.

Comments

Comments

  • steff017 OP 12 months ago

    Are you suggesting a “Workspace Shared Components” which houses components & pages that can be accessed by any app in a workspace? If so, I'd be in favor of this. This would be particularly useful for common js/css files that are loaded for every app in the workspace. I won't even consider putting common js/css files into an app's Static Application Files. If I need to edit a file that is referenced amongst all applications in a workspace, I want to do it  in one place, not in every single app's Static Application Files. Thankfully, I get around this limitation by loading the files from a designated assets/resources directory on the server.

  • fac586 OP 12 months ago

    This would be particularly useful for common js/css files that are loaded for every app in the workspace. I won't even consider putting common js/css files into an app's Static Application Files. If I need to edit a file that is referenced amongst all applications in a workspace, I want to do it  in one place, not in every single app's Static Application Files.

    That's why the ability to create static workspace files has existed for 20 years.

  • andrea galizzi OP 11 months ago

    I ran into the same problem with a group of 5 pages (1 dashboard, 2 modals for editing data and 2 detail pages) that I had to include in 3 different applications.

    At the moment they are normal pages created in app 1 and then copied "by hand" into apps 2 and 3. Keeping all the changes aligned is quite complex, and so I was considering moving everything into a region-type plugin.
    In this way, synchronizing the changes in all the apps would become a breeze, but at the same time I could no longer use native components (such as Cards and forms) but would have to implement everything by hand in JavaScript and via AJAX calls.

    If there was the possibility of reusing pages or entire regions (with related items, dynamic actions and processes) in a native way, everything would be so simple

  • joseph fuda OP 10 months ago

    There is another approach that may meet your requirement today, without waiting for a new feature. Assuming all 20+ apps in the workspace use a similar authentication method, you can set the Authentication Scheme's “Session Sharing Type” to “Workspace Sharing”.  The help text describes the feature this way.

    “You can use this attribute to share the same Oracle APEX session between multiple applications in a workspace. With session sharing, users can seamlessly navigate between applications without logging in multiple times.”

    By doing this, you can, for example, create application 100 with all your commonly used pages and then, in applications 101, 102, … 120, add links, buttons, branches, etc. that open pages located in app. 100.

  • fac586 OP 10 months ago

    @andrea galizzi If there was the possibility of reusing pages or entire regions (with related items, dynamic actions and processes) in a native way, everything would be so simple

    This has been requested as FR-1733.

  • aschultz OP 6 months ago

    @fac586 I'm sorry I didn't see your reply for the related APEX Idea.  I tried to do my diligence to avoid a duplicate submission.  With that said, I think this idea was needed to be brought up again.  APEX is now a much more mature project and more widely adopted.  Anything that can ease development, maintenance, and reusability is worth revisiting.