-
Notifications
You must be signed in to change notification settings - Fork 63
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
Add term UI.UserInteraction #61
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add an example file similar to https://github.com/oasis-tcs/odata-vocabularies/tree/master/examples.
Why are all .md files now added to this branch? |
Your branch was out-of-date with master. Merging master made the other .md files disappear |
vocabularies/examples/com.sap.vocabularies.UI.v1.UserInteraction-sample.xml
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I understood your use case & today I have to model this, I will have to create action which has a parameter and an associated Value Help. User should be able to select entry from the Value help and execute the action. Isn't it?
Did I get the use case correctly or I have understood this completely wrong?
@SNairVinod, in simple cases you could model this as an action parameter with value help. Users would then have to click twice: first to open the parameter popup, then to trigger the value help. User flow becomes even more confusing if
Such cases are better dealt with if we don't let the user pick a value help but let the server decide which navigation property to return (in the product exchange example, this is navigation property I have extended the example so that it contains both a choice and a confirmation. |
Conflicts: vocabularies/UI.md
Conflicts: vocabularies/Common.json vocabularies/Common.md vocabularies/Common.xml vocabularies/UI.md
Conflicts: vocabularies/UI.md
No description provided.