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

Field's mandatory flag is not considered #188

Closed
teosarca opened this issue Feb 25, 2017 · 2 comments
Closed

Field's mandatory flag is not considered #188

teosarca opened this issue Feb 25, 2017 · 2 comments

Comments

@teosarca
Copy link
Member

Is this a bug or feature request?

bug

What is the current behavior?

If the field is configured as:

  • IsMandatory: true
  • MandatoryLogic: null
    => field is considered not mandatory

Which are the steps to reproduce?

What is the expected or desired behavior?

Field shall be considered mandatory in that case

@teosarca teosarca added this to the 2017-09 milestone Feb 25, 2017
@teosarca
Copy link
Member Author

NOTE to IT: full webui regression is needed

@metas-lc
Copy link

metas-lc commented Mar 6, 2017

All looks fine, besides an issue in orderline - created follow-up #215
other issues like, you can create a new bpartner or cu-tu in product with mandatory fields not filled, we have metasfresh/metasfresh-webui-frontend-legacy#437

@metas-lc metas-lc closed this as completed Mar 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants