Case assignment rules reassigning back to queue
I have a case assignment rule. The case is assigned to the queue based on that and then is subsequently routed to the queue member. But the issue occurs when the case owner clicks on the EDIT button and makes some changes, the case is assigned back to the queue. What could be the issue?
configuration assignment-rules
add a comment |
I have a case assignment rule. The case is assigned to the queue based on that and then is subsequently routed to the queue member. But the issue occurs when the case owner clicks on the EDIT button and makes some changes, the case is assigned back to the queue. What could be the issue?
configuration assignment-rules
add a comment |
I have a case assignment rule. The case is assigned to the queue based on that and then is subsequently routed to the queue member. But the issue occurs when the case owner clicks on the EDIT button and makes some changes, the case is assigned back to the queue. What could be the issue?
configuration assignment-rules
I have a case assignment rule. The case is assigned to the queue based on that and then is subsequently routed to the queue member. But the issue occurs when the case owner clicks on the EDIT button and makes some changes, the case is assigned back to the queue. What could be the issue?
configuration assignment-rules
configuration assignment-rules
edited Dec 28 '18 at 17:38
m Peixoto
417213
417213
asked Dec 28 '18 at 15:44
Anna
486
486
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Basically you need to add another filter to stop recalculation of the assignment rule. As we know Queue ID starts with 00G and User ID starts with 005. So comparing the OwnerId to make sure if the OwnerId doesn't start with 005 (which means it is not owned by Queue Member), then only run the assignment rule.
add a comment |
It looks like assignment rule is firing again. You need to add another filter which can stop your assignment rule to fire everytime
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "459"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f244931%2fcase-assignment-rules-reassigning-back-to-queue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Basically you need to add another filter to stop recalculation of the assignment rule. As we know Queue ID starts with 00G and User ID starts with 005. So comparing the OwnerId to make sure if the OwnerId doesn't start with 005 (which means it is not owned by Queue Member), then only run the assignment rule.
add a comment |
Basically you need to add another filter to stop recalculation of the assignment rule. As we know Queue ID starts with 00G and User ID starts with 005. So comparing the OwnerId to make sure if the OwnerId doesn't start with 005 (which means it is not owned by Queue Member), then only run the assignment rule.
add a comment |
Basically you need to add another filter to stop recalculation of the assignment rule. As we know Queue ID starts with 00G and User ID starts with 005. So comparing the OwnerId to make sure if the OwnerId doesn't start with 005 (which means it is not owned by Queue Member), then only run the assignment rule.
Basically you need to add another filter to stop recalculation of the assignment rule. As we know Queue ID starts with 00G and User ID starts with 005. So comparing the OwnerId to make sure if the OwnerId doesn't start with 005 (which means it is not owned by Queue Member), then only run the assignment rule.
answered Dec 28 '18 at 16:55
Sudipta Deb
5511414
5511414
add a comment |
add a comment |
It looks like assignment rule is firing again. You need to add another filter which can stop your assignment rule to fire everytime
add a comment |
It looks like assignment rule is firing again. You need to add another filter which can stop your assignment rule to fire everytime
add a comment |
It looks like assignment rule is firing again. You need to add another filter which can stop your assignment rule to fire everytime
It looks like assignment rule is firing again. You need to add another filter which can stop your assignment rule to fire everytime
answered Dec 28 '18 at 16:07
sfdc
8,050879150
8,050879150
add a comment |
add a comment |
Thanks for contributing an answer to Salesforce Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f244931%2fcase-assignment-rules-reassigning-back-to-queue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown