https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40420

            Bug ID: 40420
           Summary: Add Patron API call should respect mandatory borrower
                    fields
 Change sponsored?: ---
           Product: Koha
           Version: Main
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5 - low
         Component: REST API
          Assignee: [email protected]
          Reporter: [email protected]
        QA Contact: [email protected]
                CC: [email protected]

When creating a patron via the API, the call will fail when missing the values
required by the API itself (surname, library, category) and if it's missing a
patron attribute that's marked as mandatory for the staff interface (see bug
40220).

However, the API call succeeds and makes a patron when missing values defined
as mandatory in either BorrowerMandatoryField or
PatronSelfRegistrationBorrowerMandatoryField. 

To recreate:
1: set BorrowerMandatoryField to include surname, library, category and
anything else. I used phonepro (secondary phone)
2: use Postman or similar to add a patron, sending only surname, library, and
category
3: confirm your patron is created without the required secondary phone (or
whatever you used)
4: set PatronSelfRegistrationBorrowerMandatoryField to match
BorrowerMandatoryField
5: repeat steps 2 and 3

Following discussion on other bugs, I think we have an open question whether
this should follow BorrowerMandatoryField or
PatronSelfRegistrationBorrowerMandatoryField or a new third option of
APIBorrowerMandatoryField. But it should follow something.

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to