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:
I feel like the best way to write this in SP Designer 2013 is like this, but is there a better way:
2013 sharepoint-designer workflow designer-workflow
add a comment |
up vote
2
down vote
favorite
I used to have a 2010 Workflow that had conditions like this:
I feel like the best way to write this in SP Designer 2013 is like this, but is there a better way:
2013 sharepoint-designer workflow designer-workflow
1
You could set a workflow variable in the firstIf-Else
statement called something likevarChangeAwaiting
and set it to a specific value. Then you can just do the secondIf-Else
statement asif varChangeAwaiting equals <value>
. Then if the boolean equation changes, you just have to change it in one spot (the firstIf-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
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I used to have a 2010 Workflow that had conditions like this:
I feel like the best way to write this in SP Designer 2013 is like this, but is there a better way:
2013 sharepoint-designer workflow designer-workflow
I used to have a 2010 Workflow that had conditions like this:
I feel like the best way to write this in SP Designer 2013 is like this, but is there a better way:
2013 sharepoint-designer workflow designer-workflow
2013 sharepoint-designer workflow designer-workflow
asked 8 hours ago
phfb
586
586
1
You could set a workflow variable in the firstIf-Else
statement called something likevarChangeAwaiting
and set it to a specific value. Then you can just do the secondIf-Else
statement asif varChangeAwaiting equals <value>
. Then if the boolean equation changes, you just have to change it in one spot (the firstIf-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
add a comment |
1
You could set a workflow variable in the firstIf-Else
statement called something likevarChangeAwaiting
and set it to a specific value. Then you can just do the secondIf-Else
statement asif varChangeAwaiting equals <value>
. Then if the boolean equation changes, you just have to change it in one spot (the firstIf-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
add a comment |
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:
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.
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
.
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
add a comment |
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:
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.
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
.
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
add a comment |
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:
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.
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
.
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
add a comment |
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:
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.
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
.
You could set a local variable in SPD Workflow called varChangeAwaiting
and set it to a boolean
type, as follows:
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.
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
.
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
add a comment |
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
add a comment |
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.
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%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
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
1
You could set a workflow variable in the first
If-Else
statement called something likevarChangeAwaiting
and set it to a specific value. Then you can just do the secondIf-Else
statement asif varChangeAwaiting equals <value>
. Then if the boolean equation changes, you just have to change it in one spot (the firstIf-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