Recent changes to bugs

"is mastered by" Relation hast the wrong direction

Christian Becker — Mon, 15 Jan 2007 15:30:18 -0000

The Relation "is expert for" / "is mastered by" has the Wrong direction.
This Relation is commonly created by the slm_service Process.
The Relation is used by the View "v_analyze_expert_account_by_service" to determine the responsible OU in the Escalation of the Incident Management.

Technically, the right direction is "(ou) is expert for (service)", but the created relations will be "(service) is expert for (ou)".
By Relations created by the slm_service Process this has no effects on the Incident Management, because the View "v_analyze_expert_account_by_service" also uses this wrong direction.
Only manually created Relations might not work in the Incident Management.

check permission bug!

TimFu — Wed, 22 Nov 2006 08:46:49 -0000

hi,

org.bpmspace.security.MyAuthorizer

......

public void checkPermission(Permission permission, ProcessDefinition processDefinition, Token token)
throws AccessControlException {
try {
final ProcessInstance account = UserAccountFactory.getUserAccount();
final ProcessInstance authorization = PermissionFactory
.getAuthorizationProcessInstance(permission, account);
if (authorization == null) {
throw new AccessControlException("Not authorized " + account, permission);
}
} catch (NoSuchUserAccountException e) {
throw new AccessControlException("Failed to authenticate the current user", permission);
}
}

I think you should import processDefinition and token argument into method getAuthorizationProcessInstance of PermissionFactory!