OPENAUTH.NET.LANDV Branch tour begins production of CRM system

OPENAUTH.NET.LANDV Branch tour begins production of CRM system

The origin of this event is because there is no unified membership card platform system, currently need to connect three hotel membership system, because three hotels use three kinds of hotel management system, the coupling between each other is low. Three software direct production interface can also be used, but to consider access to other systems, so there is this OPENAUTH.NET.LANDV branch tour.

Openauth.net is an open source workflow rapid development framework for permissions. The framework is based on Martin Fowler Enterprise application development ideas and a new technology portfolio (ASP. NET MVC, EF, AUTOFAC, WebAPI, Swagger, json.net, etc.), core modules include: organization, role user, authorization, form design, Workflows, and so on. Its architecture is easy to expand and is the first choice for SMEs.

Characteristics

With the classic DDD architecture, every line of code is well thought out and complies with solid rules!

The national context of RBAC (role-based access control) can be applied directly to your system.

1. Menu permissions manager and salesman landing System has a function menu is not the same
2. Button Permission Manager can approve, and salesman can't
3. Data rights a clerk can not see the bill of Clerk B
4. Field permissions Some people do not see the customer's phone number or other fields when they query the customer information

User Application System of the specific operator, I am here to design the user can be directly assigned to the User menu/button, you can also assign permissions through the role.

role in order to classify and manage many users with similar permissions, the concept of roles is defined, and all of the rights resources above can be assigned to roles, roles, and user n:

institutional tree-shaped corporate sector structure, domestic companies use more, it is actually a user group, institutions and users designed to be N/a relationship, that is, sometimes a user can belong to two departments, this situation in our customer needs indeed have appeared.

Technology stack

• Front End Vue + layui + ztree + gooflow + leipiformdesign
• Back-end ASP. NET MVC + Web API + EF + AUTOFAC + swagger + json.net
• Code generation Tool Codesmith
• Design Tools PowerDesigner + Enterprise Architect

Systems Engineering Structure:

1. Openauth.repository system storage layer for database operations
2. Openauth.app application layer, providing interface for interface
3. OPENAUTH.MVC Web site
4. Openauth.unittest Unit Test
5. Infrastructure Universal Tools Collection
6. OPENAUTH.WEBAPI SSO service and providing interface services to third parties

OPENAUTH.NET.LANDV Branch tour begins to create a CRM system