Create an app details page

[bfekadu21]

Figma link: https://www.figma.com/design/vugKvKg8H3PUKYJdCG27xd/View-Model-Details?node-id=1150-14774&t=0C5GlUwwNVZCtJdq-4

Design Ticket for Reference: #951

Description

When a user clicks on an app, they should see the app details page. There are 4 tabs that should be created: Overview, Access Control, Reporting, and Dependencies. See Figma link for UI.

There are 4 different user groups and each will have a different view of the app details page. Authors will be able to view the following tabs: Overview, Access Control, Reporting, and Dependencies. Editors will be able to view Overview and Access Control. Read-only users will only be able to view the Overview tab. Discoverable users should be able to view the Overview tab.

[natdink]

hey @bfekadu21 ! don't forget to tag the appropriate team. in this case it would be "FE Other" - I added for you :)

[ehynd]

Make sure to incorporate this as well: SEMOSS/community#365

[KirthikaKumar-K]

Page Layout and Overview Tab:

[KirthikaKumar-K]

Hi @johbaxter, as discussed on call I have just added some placeholders for Statics and Similar Apps.
Labels are updated for all the screen based on the Figma for the Access Control Tab.
Overview:

Access Control:

[KirthikaKumar-K]

Hi @ehynd, as discussed in our call yesterday, please incorporate a checkbox beside the “Request Access” button for each listed dependency. Kindly provide the updated Figma design reflecting this change.

[ehynd]

^ @MohammadmansoorUX could you please update the Figma design?

[KirthikaKumar-K]

Settings Tab:

[KirthikaKumar-K]

Hi @ehynd, @johbaxter, to display the userRole and description for each dependency, we need to include both of these responses in the GetProjectDependencies Reactor. Please do the needful.

[KirthikaKumar-K]

Hi @ehynd, parking this ticket until the above-mentioned reactor is done.

[KirthikaKumar-K]

Hi @ehynd , @bfekadu21 ,
Could you please help clarify the following queries:

1. When should "Request Access" be used, and when should "Change Access" be shown throughout the App Details tabs?

In the old design: All users except discoverable users had the "Change Access" option. Discoverable users were shown "Request Access."
In the new design: "Request Access" is now shown for both discoverable and read-only users. The "Change Access" option is only shown for user with "Editor" access.

2. What is the intended design or behavior for the Filter icon at the Access Control Tab's Table?

3. Are the buttons in the Dependency tab determined by the user's access to the entire application, or by their access to each individual dependency?

[ehynd]

@KirthikaKumar-K here's what we're thinking:

1. I actually like the old design for request access for only discoverable users and everyone with existing access having change access. technically read-only users already have access, its just read only, so i think it makes sense for them to have change access instead of request. Therefore lets keep the old way: All users except discoverable users had the "Change Access" option. Discoverable users were shown "Request Access."
2. This filter should be permission level - opens a modal to select one or all of author/editor/read-only access. Can get a designer to take a look for a screen!
3. Access should be by each individual dependency, since those can be different. ie i could have author level at the app, but read-only for the model or database.