Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to make Dynamic visibility of custom section in manifest.json with OData V2? #81

Closed
jberthe opened this issue Oct 11, 2023 · 8 comments
Assignees
Labels
follow-up-with/dev Clarification with development needed. not-doc-issue Reported issue is not a documentation issue. SAP Fiori elements

Comments

@jberthe
Copy link
Contributor

jberthe commented Oct 11, 2023

Issue description

Is there a way to dynamically control the visibility of a custom section, similar to custom actions using the "applicablePath" property?

Feedback Type (Optional)

content gaps

Page Title on SAP Help Portal (prefilled)

No response

Page URL on SAP Help Portal (prefilled)

No response

@KvM2
Copy link
Contributor

KvM2 commented Oct 11, 2023

Hi @jberthe, thanks for your contribution. Can you add a link to the documentation that is affected in this issue? thanks

@jberthe
Copy link
Contributor Author

jberthe commented Oct 11, 2023

Hi, here is the documentation (OData V2 part) :
Extension Points for Sections on the Object Page

@KvM2
Copy link
Contributor

KvM2 commented Oct 11, 2023

Thanks, @jberthe! We will look into this .

@Abhishek-Anand12
Copy link

From Fe side, there is no manifest settings available for the captioned feature. However, you can set the 'visible' property of the parent/first UI5 control which is used in the extension fragment to the path which determines the visibility of the custom section and based on the control's visibility, its parent section's visibility would be changed as well.

@mishuagrawal
Copy link
Contributor

Hello @jberthe,

Our expert has provided an update for your concern. Please confirm if this resolves your concern. If not, please feel free to write back to us.

Thanks and regards,
Mishu Agrawal

@jberthe
Copy link
Contributor Author

jberthe commented Oct 17, 2023

The solution provided, would works for content inside the section. But it will not hide the whole section.

@Abhishek-Anand12
Copy link

The solution provided, would works for content inside the section. But it will not hide the whole section.

Could you provide the application URL, its credentials and steps to replicate the issue. The proposed solution should have worked but if it doesn't, I could have a look.

@mishuagrawal
Copy link
Contributor

Hello @jberthe,

Since this is not an issue related with our documentation I will be closing this issue. You can create a ticket regarding your concern and reach out to Abhishek using the CA-UI-ST-OP component and he will get back to you with a resolution for your concern.

If you have any concerns, please feel free to reach out to us.

Thanks and regards,
Mishu Agrawal

@OlMue OlMue added the follow-up-with/dev Clarification with development needed. label Nov 22, 2023
@OlMue OlMue added invalid This doesn't seem right not-doc-issue Reported issue is not a documentation issue. and removed invalid This doesn't seem right labels Dec 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
follow-up-with/dev Clarification with development needed. not-doc-issue Reported issue is not a documentation issue. SAP Fiori elements
Projects
None yet
Development

No branches or pull requests

5 participants