To add a corresponding OpenID to the employee table how does the association relate to a new employee after the concern is linked or what?
Reply content:
To add a corresponding OpenID to the employee table how does the association relate to a new employee after the concern is linked or what?
The way you ask is that an employee table already exists. Two cases.
The employee is registered, lets the employee log in, and updates the employee's OpenID.
Employee is not registered, registered, the OpenID with.
Do you have any questions, or do I not understand the problem clearly?
This business scenario is too vague to describe.
Are new employees like self-service registrations?
If so, you can get open_id before signing in (PC Scan login, authorized login), then fill in the new Employee form and insert the OpenID and employee data together into the employee table
Recommend an employee table, a watchlist, use the background to manage the relationship between employees and concerned users, is to manually set which concerns the user is which company employees.
Listen to what you mean, there's already an employee table. Just now, we need to associate the user with the previous employee table. To correlate user tables generated by two different systems, you first need to have a unified and unique association identifier, such as a mobile phone number. For example, each employee in the previous employee table filled out a cell phone number. Then the user concerned about the public after forcing the user to bind the mobile phone number, this time to the Staff table query, if the mobile phone number already exists, then the employee is bound to this OpenID, if it does not exist directly to the employee table
The user sends the message to the public number or concerns to get to OpenID
To determine whether an employee has been concerned or is not concerned about it,
has been concerned about using plug-ins to update staff attention to OpenID,
Not concerned about binding OpenID when you're concerned