user

Registered by Jordan Craw

Implementation / Module that allows handling of users, profiles, as well as their integration with groups. Because these will be internal users, the use of customer management will be employed with another structure as the likely outcome will be there is no need for user functions with customers as their account information is stored separately on an ecommerce solution.

Likely option is that the information for customers is static and based upon orders or leads that are generated and not upon the unusual structures of several forms of ecommerce application such as oscommerce.

This will be a handler module that receives requests much like other core module, processes them and then sends acknowledgement to the requesting module.

Events parser is, I guess some form of metaphor -- event callbacks and types are defined by each module and handle the actions to take independantly as a singular event handler would be incredibly large and cumbersome.

To overcome this, there must be some form of standard storage for events and callbacks for modules and that each module provides the same retvals -- JSON maybe.

Blueprint information

Status:
Started
Approver:
Jordan Craw
Priority:
Essential
Drafter:
Jordan Craw
Direction:
Needs approval
Assignee:
Jordan Craw
Definition:
Discussion
Series goal:
None
Implementation:
Started
Milestone target:
None
Started by
Jordan Craw

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.