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

Second form activation entry criterion is not saved #805

Open
samsontu opened this issue Mar 19, 2024 · 0 comments
Open

Second form activation entry criterion is not saved #805

samsontu opened this issue Mar 19, 2024 · 0 comments
Labels
Status: Needs Triage Should be the default status for issues that have been acknowledged, but not yet processed. Type: Bug Indicates that WebProtege is not working as expected

Comments

@samsontu
Copy link

Describe the bug
When a Form activation has two (presumably >= 2) activation criteria, after clicking "Apply" and "OK", then the 2nd criterion is not save and the form behaves as if there is only one activation criterion

To Reproduce
Steps to reproduce the behavior:

  1. Go to Project/Forms and create a Form that has activation criteria 'is a subclass of A' and 'is not a subclass of B' (see first Screenshot).
  2. Click on 'Apply' and then 'OK'
  3. Observe that the second criterion 'is not a subclass of B' is not being applied
  4. Return to the definition of the form, and observe that the second activation criterion is no longer there (see second screenshot)

Expected behavior
The Boolean combination of form entry criteria be saved and applied to determine whether a form is applicable.

Screenshots
image

After leaving the Form definition page and returning to it, the 2nd form activation criterion is no longer there:
image

Desktop (please complete the following information):

  • OS: Mac OS 14.4
  • Browser Safari 17.4
  • Version WebProtégé 5.0.0:20231031:dbb8310

Additional context
N/A

@samsontu samsontu added Status: Needs Triage Should be the default status for issues that have been acknowledged, but not yet processed. Type: Bug Indicates that WebProtege is not working as expected labels Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Should be the default status for issues that have been acknowledged, but not yet processed. Type: Bug Indicates that WebProtege is not working as expected
Projects
None yet
Development

No branches or pull requests

1 participant