Community Tip - If community subscription notifications are filling up your inbox you can set up a daily digest and get all your notifications in a single email. X
I want to add an activity in one of our ECN flows that runs in parallel to the rest of the approval so that the reviews and so on continue and a part can get released but the ECN itself wouldn't be resolved until that last parallel activity is completed.
The idea is that the release of a part isn't gated by that one activity that can happen throughout the ECN flow.
Looks like paralle expressions are ok. Any pros/cons to doing this with activities? Any pitfalls? Or perhaps a different approach?
Solved! Go to Solution.
@HelesicPetr I'm mostly looking for a sanity check is all since I don't see it in documentation explicitly.
Windchill (and this community in general) taught me that just because I think something needs to be done a certain way doesn't mean that it's
a) a good idea,
b) how PTC intended for that to happen in the first place and
c) possible without requiring excessive tweaks that are prone to breaking later.
On testing, it seems to work just fine with multiple activities running in parallel. As long as the right logic is in place (mostly OR and AND nodes in my case for correct pauses in the workflow) there don't seem to be any issues.
Time will tell if this remains the case.
@HelesicPetr I'm mostly looking for a sanity check is all since I don't see it in documentation explicitly.
Windchill (and this community in general) taught me that just because I think something needs to be done a certain way doesn't mean that it's
a) a good idea,
b) how PTC intended for that to happen in the first place and
c) possible without requiring excessive tweaks that are prone to breaking later.
On testing, it seems to work just fine with multiple activities running in parallel. As long as the right logic is in place (mostly OR and AND nodes in my case for correct pauses in the workflow) there don't seem to be any issues.
Time will tell if this remains the case.