Supervisory node object has incorrect properties

I made a re-test and the issue no longer occurs. Yet I noticed two other issues related to the Supervisory Nodes screen - pagination not working and the fact that it is impossible to edit any field on the Edit Supervisory Node screen. I will create separate tickets for the two.

@Joanna Bebak Both issues should be resolved.

I tested the ticket, and noticed some issues:

1. When using the POST /api/supervisoryNodes endpoint with name and without facility or with name and with facility, the following error is returned:

{
"timestamp": "2017-11-22T08:16:03.217+0000",
"status": 500,
"error": "Internal Server Error",
"exception": "org.javers.common.exception.JaversException",
"message": "ENTITY_INSTANCE_WITH_NULL_ID: Found Entity instance 'SupervisoryNode' with null idProperty 'id'",
"path": "/api/supervisoryNodes"
}

Without a name and without facility and without name and with facility everything works correctly - 400 code is returned with a message that name is required.

2. Edition of supervisory nodes ceased to work. I don't know if this is related to the changes introduced with this ticket but this might be a regression. After clicking on the "Edit" button on Administration > Supervisory Nodes, nothing happens, only an error occurs in the console:

This is ready for Team Parrot to work on, I removed my name as the assignee.

I just double checked and the issues mentioned in the ticket are still there. I don't see the facility in supervisory node being used anywhere, including fulfillment. A supervisory node is associated with a warehouse via a supply line.

FYI @Josh Zamor