Discussions
Run Match / Deduplication Rule On Program Canvas
Would like to replace as much as possible that we currently have built into Program Builder programs and move to Program Canvas/Campaign Canvas. But, we have several Program Builder steps that run Match or De-duplication rules. Please add this as a step available on Program Canvas.
Comments
-
I tried to file a feature request on this withSR 3-13605718701, but I was told this is slated for release with the 486 or 487 release. The ETA was not firm, but this means it's coming. Just need confirmation from the PM on this.
-
I tried to file a feature request on this withSR 3-13605718701, but I was told this is slated for release with the 486 or 487 release. The ETA was not firm, but this means it's coming. Just need confirmation from the PM on this.
Hey folks, this is something we'll be looking to tackle soon, but it is not part of the 486 or 487 release. I'll update the status of the idea as we get closer to executing on it.
-
Hey folks, this is something we'll be looking to tackle soon, but it is not part of the 486 or 487 release. I'll update the status of the idea as we get closer to executing on it.
Will this include all of the data tools such as update rules as well?
-
Will this include all of the data tools such as update rules as well?
Update rules are already a part of the Canvas.
-
Definitely a showstopper.
-
Hey folks, this is something we'll be looking to tackle soon, but it is not part of the 486 or 487 release. I'll update the status of the idea as we get closer to executing on it.
Hello @Prasanna V - Oracle Eloqua-Oracle - will this be part of the next release (487, I believe)? If so, when can we expect that release to be rolled out to POD1?
-
Hello @Prasanna V - Oracle Eloqua-Oracle - will this be part of the next release (487, I believe)? If so, when can we expect that release to be rolled out to POD1?
No, it won't be, but @Prasanna V - Oracle Eloqua-Oracle will update us on here when it's coming.
-
No, it won't be, but @Prasanna V - Oracle Eloqua-Oracle will update us on here when it's coming.
Thanks @Alexander Huzar for the update...this is killin' me. Being able to use match/deduplication rules in Program Canvas and/or Campaign canvas is the one thing preventing me from moving several long, slow Program Builder programs to Program Canvas. This really needs to be done sooner rather than later.
-
Thanks @Alexander Huzar for the update...this is killin' me. Being able to use match/deduplication rules in Program Canvas and/or Campaign canvas is the one thing preventing me from moving several long, slow Program Builder programs to Program Canvas. This really needs to be done sooner rather than later.
@mhartmann we're in the same boat. When we run de-duplication it's +15 minutes for every scenario we need to evaluate for duplicates. Our process adds about 1 hour 45 minutes to the normal integration SLA. I've stopped working on new ways to de-duplicate records because it would simply add even more time to the process. I'm actually seriously considering running the match rules in parallel by adding the contact to multiple independent programs, one for each match rule. program builder programs of the same run mode still run sequentially in the same instance (it's even worse actually because on the same server this is shared between clients), but at least we would not have to wait +15 minutes between steps. If this was on the canvas we could get it done in minutes. In order to avoid this we evaluate the email address domain to determine if it requires deduplication and only send the personal domains (gmail, hotmail, etc.) through the de-duplication process. Without deduplication, it's 2 minutes through a couple program canvasses and <5 minutes in one program builder, then another 5 minutes to flush out the external call queue - total in reality is about 3-10 minutes from a form submit to a new Lead in SalesForce.
-
@mhartmann we're in the same boat. When we run de-duplication it's +15 minutes for every scenario we need to evaluate for duplicates. Our process adds about 1 hour 45 minutes to the normal integration SLA. I've stopped working on new ways to de-duplicate records because it would simply add even more time to the process. I'm actually seriously considering running the match rules in parallel by adding the contact to multiple independent programs, one for each match rule. program builder programs of the same run mode still run sequentially in the same instance (it's even worse actually because on the same server this is shared between clients), but at least we would not have to wait +15 minutes between steps. If this was on the canvas we could get it done in minutes. In order to avoid this we evaluate the email address domain to determine if it requires deduplication and only send the personal domains (gmail, hotmail, etc.) through the de-duplication process. Without deduplication, it's 2 minutes through a couple program canvasses and <5 minutes in one program builder, then another 5 minutes to flush out the external call queue - total in reality is about 3-10 minutes from a form submit to a new Lead in SalesForce.
@Alexander Huzar - that is the exact scenario I am dealing with...lead to account matching. To make things worse for us, we don't have SF.com, we have a custom integration where I have to still use third party cloud connectors in program builder to send information to the CRM. So, I already have a built-in 30-60 minute delay for those steps alone. I've already shortened the process by using a combination of program canvas/campaign canvas/program builder (another beef I have is that we aren't able to send from program builder to program canvas, but that is a separate gripe).
But, in the case where there is a non-match (we also use D&B connector to match to existing accounts via DUNS number) I have a tiered attempt at matching that takes at least an hour or two if there is no match. Really need the match/de-dupe rules in program canvas.
-
@Alexander Huzar - that is the exact scenario I am dealing with...lead to account matching. To make things worse for us, we don't have SF.com, we have a custom integration where I have to still use third party cloud connectors in program builder to send information to the CRM. So, I already have a built-in 30-60 minute delay for those steps alone. I've already shortened the process by using a combination of program canvas/campaign canvas/program builder (another beef I have is that we aren't able to send from program builder to program canvas, but that is a separate gripe).
But, in the case where there is a non-match (we also use D&B connector to match to existing accounts via DUNS number) I have a tiered attempt at matching that takes at least an hour or two if there is no match. Really need the match/de-dupe rules in program canvas.
@mhartmann I use a "proxy" campaign canvas just to route from a program builder to program canvas. Just don't "sync with CRM" on the campaign (I guess this irrelevant for your config), and let it run until like 2020 just in case. Campaigns can add and move to both program builder and program canvas so they make for really good relays. I also use shared lists as controls - for example, if I'm adding to another program (because I don't want to include it in the main flow), I add to a shared list in the auxiliary program, then at the end of the flow I remove from the shared list so that back in the main program I can use a decision rule to evaluate membership in the shared list. The reason why I do this is because the re-evaluation on a canvas is more frequent than the 15 minute step-to-step in standard mode program builder, so I can save 5 to 10 minutes sometimes.
Retry frequency for decision rules in program canvas:
24 hours or less = every 10 minutes
more than a day = every 30 minutes
more than a week = every 1 hour
Anyway, only thing I can suggest is to not re-run through the match/dedupe rules if you've run someone through in the past 24 hours. That's what I built at my end and it has had a significant impact. (I use a shared list to inventory everyone who has been de-duplicated in the past 24 hours and then use a decision rule to bypass these people and save almost 2 hours per record.)
-
@mhartmann I use a "proxy" campaign canvas just to route from a program builder to program canvas. Just don't "sync with CRM" on the campaign (I guess this irrelevant for your config), and let it run until like 2020 just in case. Campaigns can add and move to both program builder and program canvas so they make for really good relays. I also use shared lists as controls - for example, if I'm adding to another program (because I don't want to include it in the main flow), I add to a shared list in the auxiliary program, then at the end of the flow I remove from the shared list so that back in the main program I can use a decision rule to evaluate membership in the shared list. The reason why I do this is because the re-evaluation on a canvas is more frequent than the 15 minute step-to-step in standard mode program builder, so I can save 5 to 10 minutes sometimes.
Retry frequency for decision rules in program canvas:
24 hours or less = every 10 minutes
more than a day = every 30 minutes
more than a week = every 1 hour
Anyway, only thing I can suggest is to not re-run through the match/dedupe rules if you've run someone through in the past 24 hours. That's what I built at my end and it has had a significant impact. (I use a shared list to inventory everyone who has been de-duplicated in the past 24 hours and then use a decision rule to bypass these people and save almost 2 hours per record.)
Thanks @Alexander Huzar for the suggestion. I am also using some proxy campaigns to move between program builder and program canvas. Not sure if your suggestion about re-running would apply in our case. But, it is a clever solution.
-
@mhartmann I use a "proxy" campaign canvas just to route from a program builder to program canvas. Just don't "sync with CRM" on the campaign (I guess this irrelevant for your config), and let it run until like 2020 just in case. Campaigns can add and move to both program builder and program canvas so they make for really good relays. I also use shared lists as controls - for example, if I'm adding to another program (because I don't want to include it in the main flow), I add to a shared list in the auxiliary program, then at the end of the flow I remove from the shared list so that back in the main program I can use a decision rule to evaluate membership in the shared list. The reason why I do this is because the re-evaluation on a canvas is more frequent than the 15 minute step-to-step in standard mode program builder, so I can save 5 to 10 minutes sometimes.
Retry frequency for decision rules in program canvas:
24 hours or less = every 10 minutes
more than a day = every 30 minutes
more than a week = every 1 hour
Anyway, only thing I can suggest is to not re-run through the match/dedupe rules if you've run someone through in the past 24 hours. That's what I built at my end and it has had a significant impact. (I use a shared list to inventory everyone who has been de-duplicated in the past 24 hours and then use a decision rule to bypass these people and save almost 2 hours per record.)
If only they had introduced bidirectional support of Program Canvas/Builder in R485.
-
No, it won't be, but @Prasanna V - Oracle Eloqua-Oracle will update us on here when it's coming.
Unfortunately it appears that he is no longer at Oracle. Wouldn't expect this feature for awhile...hopefully soon!
Post edited by Unknown User on -
Unfortunately it appears that he is no longer at Oracle. Wouldn't expect this feature for awhile...hopefully soon!
No, that's not true! It's still on the radar and we know it's needed. Stay tuned for updates.
Group Product Manager, CX - Marketing: Eloqua
-
BUMP
-
@JodyMooney-Oracle Any ETA for this?
-
@JodyMooney-Oracle, Will this "Stay tuned for updates" period ever end?
-
Deduplication/Match Rules remains one of the few compelling remaining reasons to continue to build flows using the old Program Builder. I would love to move my clients off Program Builder, but need this action available in the Program Canvas first.
-
@JodyMooney-Oracle Any chance there is an update on the plan to include this feature before sunset for support in program builder in February? Lots of clients making the transition now and concerned about this missing ability.
-
@KellyNewton - To be clear, Program Builder is NOT being sunset in February. Is this published somewhere else? If so, please pass along where this was mentioned and I will help address at the source.
Group Product Manager, CX - Marketing: Eloqua
-
I understand, as I stated, I was looking for information regarding if this missing ability (Dedup/Match Rules) is on the roadmap soon for Program Canvas because of the sunset of SUPPORT for program builder in February. As per the release notes, clients will no longer be able to open an SR regarding Program Builder as of February 1.
-
@KellyNewton Trying to get to the bottom of the Program Builder comment. I think you might be getting this confused with the sunset of Salesforce Native integration - as it sunsets on Feb 1, 2021. Not program builder though. Here's the product notice of SFDC sunset: https://community.oracle.com/topliners/discussion/4470780/product-notice-support-for-native-salesforce-integration-ending-feb-1-2021/p1
If this is not the case, and you're seeing it somewhere in the release notes that I'm missing, please send me an email jody dot mooney at oracle com and we'll get this all sorted out.
As a side note, I've asked the team for an update on the functionality that you're looking for an update on as well!!
Group Product Manager, CX - Marketing: Eloqua
-
Program canvas has been out for years, when are we finally going to see this feature? Another one missing that would make life so much easier is the send email step in CDO program canvas.
