Open asvishnyakov opened 7 years ago
Research result: The reason is why member has outdated list of security accounts is cache. When we create new security account, we have MemberId, but we not invalidate this member.
@tatarincev Make review on PR, please
Could we postpone this PR, because we have other promising cache invalidation technology based on event consistency?
@tatarincev Depend on when we can implement this new technology. I prefer to merge PR, because otherwise members data is inconsistent: you may have situation, when there is no member with this specified user, but you can't register user with the same name, because it's already exist. UPD. But if we may implement this new cache invalidation very soon, may be we must postone. Because as I can see, there is no customers for which this problem appear.
@tatarincev Update status, please, possible resolved
Version info:
Expected behavior
When you create user for contact/employee in Customer module, user must appear in Accounts widget after creation, customer model must be invalidated and Save button enabled.
Actual behavior
Newly created user does not appear in Accounts widget.
Steps to reproduce
New blade for newly created user appear, but user does not appear in Accounts widget and customer model is not invalidated.