Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JBPM-6670 - Allow to search tasks assigned by potential owner through #1084

Merged
merged 1 commit into from Dec 4, 2017

Conversation

macihu
Copy link
Contributor

@macihu macihu commented Nov 28, 2017

Allow to search tasks assigned by potential owner through

@kie-ci
Copy link

kie-ci commented Nov 28, 2017

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

3 similar comments
@kie-ci
Copy link

kie-ci commented Nov 28, 2017

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

@kie-ci
Copy link

kie-ci commented Nov 28, 2017

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

@kie-ci
Copy link

kie-ci commented Nov 28, 2017

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

@mswiderski mswiderski mentioned this pull request Nov 28, 2017
@kie-ci
Copy link

kie-ci commented Nov 28, 2017

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

1 similar comment
@kie-ci
Copy link

kie-ci commented Nov 28, 2017

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

Copy link
Contributor

@mswiderski mswiderski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

few comments left to discuss/address

potOwnersList.add(potOwner);

if(userGroupCallback.getGroupsForUser(potOwner) != null) {
potOwnersList.addAll(userGroupCallback.getGroupsForUser(potOwner));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd move this to separate line

List<String> groups = userGroupCallback.getGroupsForUser(potOwner);

otherwise it might be rather heavy in some cases to call it twice

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done


@Override
public QueryResultMapper<List<UserTaskInstanceWithPotOwnerDesc>> forColumnMapping(Map<String, String> columnMapping) {
return new UserTaskInstanceWithModifVarsQueryMapper();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it intended to ignore columnMapping?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, why?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the method has argument columnMapping but it is never used like it most likely should be added as constructor of return new UserTaskInstanceWithModifVarsQueryMapper()

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry Maciej, I didn't understand you well. I think is good ignoring the argument columnMapping for this mapper. Similar to: https://github.com/kiegroup/jbpm/blob/master/jbpm-services/jbpm-kie-services/src/main/java/org/jbpm/kie/services/impl/query/mapper/UserTaskInstanceWithVarsQueryMapper.java

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's why I asked if that was intended or not. If you believe there will not be a need to read up custom variables then it's ok with me.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, it's ok


@Override
public QueryResultMapper<List<UserTaskInstanceWithPotOwnerDesc>> forColumnMapping(Map<String, String> columnMapping) {
return new UserTaskInstanceWithPotOwnerQueryMapper();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here, is it intended to ignore columnMapping?

@mswiderski
Copy link
Contributor

ok to test

@mswiderski mswiderski changed the title BPMSPL-781: Allow to search tasks assigned by potential owner through JBPM-6670 - Allow to search tasks assigned by potential owner through Dec 4, 2017
@mswiderski mswiderski merged commit 8a8fca4 into kiegroup:master Dec 4, 2017
hxf0801 pushed a commit to hxf0801/jbpm that referenced this pull request Apr 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants