minitour / db2018_ex5 Goto Github PK

Controller requests 2 parameters for read_all: hospitalID and departmentID.
The second parameter is not needed here.

after making an API call show a snackbar to indicate if the operation was successful or not.

Some tests do not match the backend controller.
Make sure after making the API call to add a delay to allow the assertion to happen:

api.readAll(params, (response,items) -> {
        assertTrue(items!=null && items.size() > 0);
});
try { Thread.sleep(3000); } catch (Exception ignored){}

The Requirements File:

https://drive.google.com/open?id=1KCvjgZc6PJYe1GDA6xyCnzkTMKcGgL8n

Checkout PersonForm.java as an example.

Apply the same for all other forms.

• textFieldFactory
• comboBoxForFields
• listForField
• inupdateableFields

Add a new route /updatePassword

Parameters: ACCOUNT_ID, SESSION_TOKEN, currentPassword,newPassword.
Response: Success/Failure

Logic:
Check if the currentPassword matches the password that is stored. Use Bcrypt.checkpw().

Database Dependencies:

• Needs a stored procedure to update the password.
  Parameters(ACCOUNT_ID, password)

UpdateAccounts SET password = @password WHERE ACCOUNT_ID = @ACCOUNT_ID;
SELECT @ACCOUNT_ID;

After understanding the requirements collected in issue #1, start designing the system.
This includes both the client and the server:

Server

• REST API Design and Web Services
• Controllers Definitions
• Database Integration and Models Definition
• Roles and Permissions management
• Security Mechanisms

Client

• API Manager Design
• Screens UI / UX
• Controllers
• Local Storage

Read all the files in the reference folder and extract all requirements starting from EX5, then EX1, EX2, EX3.

• What features should the system include?
• How many roles should the system be able to handle?
• How many predefined SQL queries (Stored Procedures) should we define and what are they and where will they be used?
• What triggers should we create?
• What are the screens that we need?

Something wrong with the form.