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

Add term UI.UserInteraction #61

Draft
wants to merge 100 commits into
base: main
Choose a base branch
from
Draft

Add term UI.UserInteraction #61

wants to merge 100 commits into from

Conversation

HeikoTheissen
Copy link
Contributor

No description provided.

@HeikoTheissen HeikoTheissen marked this pull request as draft October 7, 2020 13:17
vocabularies/UI.xml Outdated Show resolved Hide resolved
Copy link
Member

@ralfhandl ralfhandl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

vocabularies/UI.xml Outdated Show resolved Hide resolved
vocabularies/UI.xml Outdated Show resolved Hide resolved
vocabularies/UI.xml Outdated Show resolved Hide resolved
vocabularies/UI.xml Outdated Show resolved Hide resolved
@ralfhandl ralfhandl changed the title Update UI.xml Add term UI.UserInteraction Dec 8, 2020
@HeikoTheissen
Copy link
Contributor Author

Why are all .md files now added to this branch?

@ralfhandl
Copy link
Member

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

Copy link

@SNairVinod SNairVinod left a 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?

@HeikoTheissen
Copy link
Contributor Author

HeikoTheissen commented Dec 9, 2020

@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

  • the action has other parameters that users must fill before the value help can be triggered
  • the action may sometimes succeed without additional user interaction (product exchange is not a good example for this, but think of order creation with quote reference: if there is more than one matching quote, the user must choose, if there is one matching quote, the user must confirm, if there is no matching quote, no user interaction is required).

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 _AlternativeProducts, but there could be others).

I have extended the example so that it contains both a choice and a confirmation.

Conflicts:
	vocabularies/Common.json
	vocabularies/Common.md
	vocabularies/Common.xml
	vocabularies/UI.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants