Self Service: User Management

[abhaychawla]

Goal:

As a user,
I want a screen to view all the clients (self-service/non-self-service users)
so that I can manage them as a whole.

Tasks:

1. Add a screen to manage all clients (self-service/non-self-service users)
2. Add feature to search
3. Allow bulk activation/deactivation of self-service users
4. Add feature for creating a self-service user
5. Click and view details of a client (self-service/non-self-service users)
6. Edit details of a client (self-service/non-self-service users)

Acceptance Criteria:

• Add a screen to manage all clients (self-service/non-self-service users)
• Add feature to search
• Allow bulk activation/deactivation of self-service users
• Add feature for creating a self-service user
• Click and view details of a client (self-service/non-self-service users)
• Edit details of a client (self-service/non-self-service users)

UPDATE: User Interface completed. Functionality can be completed once required APIs are available.

Fineract: https://issues.apache.org/jira/browse/FINERACT-638

[abhaychawla]

Mockups for reference:

[abhaychawla]

@edcable @gauravsaini03 @anweshknayak
Should we add the requirements for the self-service user management in the current clients' page itself or create it as a separate component for now?

[muddlebee]

I think @gauravsaini03 mentioned to keep it separate.

[abhaychawla]

Okay.

[muddlebee]

Also one more thing. We already using bootswatch for the material look, which is overriding the default bootstrap.css with the bootswatch one. So using material-angular will just increase the overhead and make it more slow.
Also bootstrap.js doesn't work in angular for that there's https://ng-bootstrap.github.io/#/components/accordion/examples. I am using this for now. As it is lightweight and replacement for bootstrap.js.

For now we should stick to

• bootswatch
• ng-bootstrap

using material-angular doesn't make sense as we already have the material view. Let me know what you think about it. We can use if there is a dire need and it doesn't get solved without the above two mentioned. Also it's better if we use external libraries to a minimal extent for optimal performance of site.

[abhaychawla]

Yes, I agree with you. We should stick to using bootswatch. I was also thinking about why we might need to use both.

[abhaychawla]

[UPDATE] As per community discussion, we shifted to using angular-material.