SP Designer 2013: Can I reduce redundancy between action steps and transition conditions?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty{ margin-bottom:0;
}






up vote
2
down vote

favorite












I used to have a 2010 Workflow that had conditions like this:
enter image description here



I feel like the best way to write this in SP Designer 2013 is like this, but is there a better way:
enter image description here










share|improve this question


















  • 1




    You could set a workflow variable in the first If-Else statement called something like varChangeAwaiting and set it to a specific value. Then you can just do the second If-Else statement as if varChangeAwaiting equals <value>. Then if the boolean equation changes, you just have to change it in one spot (the first If-Else and not the second. Let me know if that helps or need a better explanation.
    – KGlasier
    8 hours ago










  • KGlasier: Thanks for your comment! Let me make sure I'm understanding completely: EDIT (line breaks don't work)..... So in the workflow action steps, I make a workflow variable, and set it to true, then when I get to the transition section, I just reference that variable and make the logic choices there, instead of the long conditional - correct?
    – phfb
    8 hours ago








  • 1




    Yes I think that's what you want to do. I'll make a post about it just to make sure it's clear. Sorry I commented before your EDIT. Deleted my last comment.
    – KGlasier
    8 hours ago

















up vote
2
down vote

favorite












I used to have a 2010 Workflow that had conditions like this:
enter image description here



I feel like the best way to write this in SP Designer 2013 is like this, but is there a better way:
enter image description here










share|improve this question


















  • 1




    You could set a workflow variable in the first If-Else statement called something like varChangeAwaiting and set it to a specific value. Then you can just do the second If-Else statement as if varChangeAwaiting equals <value>. Then if the boolean equation changes, you just have to change it in one spot (the first If-Else and not the second. Let me know if that helps or need a better explanation.
    – KGlasier
    8 hours ago










  • KGlasier: Thanks for your comment! Let me make sure I'm understanding completely: EDIT (line breaks don't work)..... So in the workflow action steps, I make a workflow variable, and set it to true, then when I get to the transition section, I just reference that variable and make the logic choices there, instead of the long conditional - correct?
    – phfb
    8 hours ago








  • 1




    Yes I think that's what you want to do. I'll make a post about it just to make sure it's clear. Sorry I commented before your EDIT. Deleted my last comment.
    – KGlasier
    8 hours ago













up vote
2
down vote

favorite









up vote
2
down vote

favorite











I used to have a 2010 Workflow that had conditions like this:
enter image description here



I feel like the best way to write this in SP Designer 2013 is like this, but is there a better way:
enter image description here










share|improve this question













I used to have a 2010 Workflow that had conditions like this:
enter image description here



I feel like the best way to write this in SP Designer 2013 is like this, but is there a better way:
enter image description here







2013 sharepoint-designer workflow designer-workflow






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 8 hours ago









phfb

586




586








  • 1




    You could set a workflow variable in the first If-Else statement called something like varChangeAwaiting and set it to a specific value. Then you can just do the second If-Else statement as if varChangeAwaiting equals <value>. Then if the boolean equation changes, you just have to change it in one spot (the first If-Else and not the second. Let me know if that helps or need a better explanation.
    – KGlasier
    8 hours ago










  • KGlasier: Thanks for your comment! Let me make sure I'm understanding completely: EDIT (line breaks don't work)..... So in the workflow action steps, I make a workflow variable, and set it to true, then when I get to the transition section, I just reference that variable and make the logic choices there, instead of the long conditional - correct?
    – phfb
    8 hours ago








  • 1




    Yes I think that's what you want to do. I'll make a post about it just to make sure it's clear. Sorry I commented before your EDIT. Deleted my last comment.
    – KGlasier
    8 hours ago














  • 1




    You could set a workflow variable in the first If-Else statement called something like varChangeAwaiting and set it to a specific value. Then you can just do the second If-Else statement as if varChangeAwaiting equals <value>. Then if the boolean equation changes, you just have to change it in one spot (the first If-Else and not the second. Let me know if that helps or need a better explanation.
    – KGlasier
    8 hours ago










  • KGlasier: Thanks for your comment! Let me make sure I'm understanding completely: EDIT (line breaks don't work)..... So in the workflow action steps, I make a workflow variable, and set it to true, then when I get to the transition section, I just reference that variable and make the logic choices there, instead of the long conditional - correct?
    – phfb
    8 hours ago








  • 1




    Yes I think that's what you want to do. I'll make a post about it just to make sure it's clear. Sorry I commented before your EDIT. Deleted my last comment.
    – KGlasier
    8 hours ago








1




1




You could set a workflow variable in the first If-Else statement called something like varChangeAwaiting and set it to a specific value. Then you can just do the second If-Else statement as if varChangeAwaiting equals <value>. Then if the boolean equation changes, you just have to change it in one spot (the first If-Else and not the second. Let me know if that helps or need a better explanation.
– KGlasier
8 hours ago




You could set a workflow variable in the first If-Else statement called something like varChangeAwaiting and set it to a specific value. Then you can just do the second If-Else statement as if varChangeAwaiting equals <value>. Then if the boolean equation changes, you just have to change it in one spot (the first If-Else and not the second. Let me know if that helps or need a better explanation.
– KGlasier
8 hours ago












KGlasier: Thanks for your comment! Let me make sure I'm understanding completely: EDIT (line breaks don't work)..... So in the workflow action steps, I make a workflow variable, and set it to true, then when I get to the transition section, I just reference that variable and make the logic choices there, instead of the long conditional - correct?
– phfb
8 hours ago






KGlasier: Thanks for your comment! Let me make sure I'm understanding completely: EDIT (line breaks don't work)..... So in the workflow action steps, I make a workflow variable, and set it to true, then when I get to the transition section, I just reference that variable and make the logic choices there, instead of the long conditional - correct?
– phfb
8 hours ago






1




1




Yes I think that's what you want to do. I'll make a post about it just to make sure it's clear. Sorry I commented before your EDIT. Deleted my last comment.
– KGlasier
8 hours ago




Yes I think that's what you want to do. I'll make a post about it just to make sure it's clear. Sorry I commented before your EDIT. Deleted my last comment.
– KGlasier
8 hours ago










1 Answer
1






active

oldest

votes

















up vote
3
down vote



accepted










You could set a local variable in SPD Workflow called varChangeAwaiting and set it to a boolean type, as follows:



enter image description here



Then set your If-Else up as you already have it but add the local variable. Sorry for not having the exact same if-else statement as you, but I did this in a bit of a rush.



enter image description here



Does that make sense? Now if you ever have to change the if-else you can just change it in one spot and the boolean will still flip. There's a chance you'll need to do a Set Variable: varChangeAwaiting to No at the top of your stage to initialize the variable, but it might default to No.






share|improve this answer





















  • This makes good sense. Bummer SP's not just in python, but this is a big improvement. Thanks!
    – phfb
    7 hours ago










  • @phfb I wish we could use some sort of programming language, at least. Would make life so much easier on our end.
    – KGlasier
    7 hours ago













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "232"
};
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',
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsharepoint.stackexchange.com%2fquestions%2f253669%2fsp-designer-2013-can-i-reduce-redundancy-between-action-steps-and-transition-co%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
3
down vote



accepted










You could set a local variable in SPD Workflow called varChangeAwaiting and set it to a boolean type, as follows:



enter image description here



Then set your If-Else up as you already have it but add the local variable. Sorry for not having the exact same if-else statement as you, but I did this in a bit of a rush.



enter image description here



Does that make sense? Now if you ever have to change the if-else you can just change it in one spot and the boolean will still flip. There's a chance you'll need to do a Set Variable: varChangeAwaiting to No at the top of your stage to initialize the variable, but it might default to No.






share|improve this answer





















  • This makes good sense. Bummer SP's not just in python, but this is a big improvement. Thanks!
    – phfb
    7 hours ago










  • @phfb I wish we could use some sort of programming language, at least. Would make life so much easier on our end.
    – KGlasier
    7 hours ago

















up vote
3
down vote



accepted










You could set a local variable in SPD Workflow called varChangeAwaiting and set it to a boolean type, as follows:



enter image description here



Then set your If-Else up as you already have it but add the local variable. Sorry for not having the exact same if-else statement as you, but I did this in a bit of a rush.



enter image description here



Does that make sense? Now if you ever have to change the if-else you can just change it in one spot and the boolean will still flip. There's a chance you'll need to do a Set Variable: varChangeAwaiting to No at the top of your stage to initialize the variable, but it might default to No.






share|improve this answer





















  • This makes good sense. Bummer SP's not just in python, but this is a big improvement. Thanks!
    – phfb
    7 hours ago










  • @phfb I wish we could use some sort of programming language, at least. Would make life so much easier on our end.
    – KGlasier
    7 hours ago















up vote
3
down vote



accepted







up vote
3
down vote



accepted






You could set a local variable in SPD Workflow called varChangeAwaiting and set it to a boolean type, as follows:



enter image description here



Then set your If-Else up as you already have it but add the local variable. Sorry for not having the exact same if-else statement as you, but I did this in a bit of a rush.



enter image description here



Does that make sense? Now if you ever have to change the if-else you can just change it in one spot and the boolean will still flip. There's a chance you'll need to do a Set Variable: varChangeAwaiting to No at the top of your stage to initialize the variable, but it might default to No.






share|improve this answer












You could set a local variable in SPD Workflow called varChangeAwaiting and set it to a boolean type, as follows:



enter image description here



Then set your If-Else up as you already have it but add the local variable. Sorry for not having the exact same if-else statement as you, but I did this in a bit of a rush.



enter image description here



Does that make sense? Now if you ever have to change the if-else you can just change it in one spot and the boolean will still flip. There's a chance you'll need to do a Set Variable: varChangeAwaiting to No at the top of your stage to initialize the variable, but it might default to No.







share|improve this answer












share|improve this answer



share|improve this answer










answered 7 hours ago









KGlasier

55713




55713












  • This makes good sense. Bummer SP's not just in python, but this is a big improvement. Thanks!
    – phfb
    7 hours ago










  • @phfb I wish we could use some sort of programming language, at least. Would make life so much easier on our end.
    – KGlasier
    7 hours ago




















  • This makes good sense. Bummer SP's not just in python, but this is a big improvement. Thanks!
    – phfb
    7 hours ago










  • @phfb I wish we could use some sort of programming language, at least. Would make life so much easier on our end.
    – KGlasier
    7 hours ago


















This makes good sense. Bummer SP's not just in python, but this is a big improvement. Thanks!
– phfb
7 hours ago




This makes good sense. Bummer SP's not just in python, but this is a big improvement. Thanks!
– phfb
7 hours ago












@phfb I wish we could use some sort of programming language, at least. Would make life so much easier on our end.
– KGlasier
7 hours ago






@phfb I wish we could use some sort of programming language, at least. Would make life so much easier on our end.
– KGlasier
7 hours ago




















draft saved

draft discarded




















































Thanks for contributing an answer to SharePoint 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsharepoint.stackexchange.com%2fquestions%2f253669%2fsp-designer-2013-can-i-reduce-redundancy-between-action-steps-and-transition-co%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Accessing regular linux commands in Huawei's Dopra Linux

Can't connect RFCOMM socket: Host is down

Kernel panic - not syncing: Fatal Exception in Interrupt