WF permissions and roles (1)

On Role: WebWorkflowRoleHere is an example of a role.

Because WebWorkflowRole uses ASP. NET's user database "aspnetdb" by default, I did not discuss it at the time. I decided to design a database dedicated to multi-user participation and implement it in WorkflowRole.

After thinking for a while, I also wrote a few articles. I feel that I can still implement the functions I want to implement, the idea of "group" and "rule" is introduced based on the traditional user and role, for example, "user A" and "role X ", "workflow instance node Q" and "rule 2006-11-11 00:00:00 to 2006-11-12 00: 00: 00" Add it to A group, then "User A, in 2006-11-11 From 00:00:00 to 00:00:00, the workflow instance node Q has the role X permission"

When the design was complete, I suddenly thought of a problem, that is, ASP. NET 2.0 login control and WebParts control.

We know that the user interface of different roles in the system is different from the menu, if ASP. NET 2.0 does not provide the logon control and WebParts control, so there is no problem. We implemented it by ourselves. We previously did this in ASPNET1.1, but now I cannot ignore ASP. NET 2.0.

If I want to migrate the data structure, page developers may have to select their own headers to implement ASP. NET 2.0, or map my database structure to the data structure of aspnetdb in a data bridge mode, or use two sets of role systems.

This is not a good situation!

Therefore, the best way to do this is to use aspnetdb for users and roles in the workflow. without modifying the original database structure of aspnetdb, you can expand it to a certain extent.