MENU
A developer builds a new OmniScript. It contains a Set Values element with a ContextId key/value pair that was used during testing.
What should the developer do before moving the OmniScript to a production org?
Suggested Answer: B
Get Premium OMS-435 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
11 comments · newest first
ZE
Zena
12 months ago
I agree, updating the ContextId is a must before going live!
DW
Dwight
12 months ago
Wait, can you really just deactivate the ContextId? That sounds risky.
FL
Flo
12 months ago
Deleting the Set Values element seems a bit extreme.
KE
Keena
1 year ago
I think adding a Show/Hide condition could be useful too.
DU
Dusti
1 year ago
Definitely need to update the ContextId value for production!
DO
Domitila
1 year ago
I think deactivating the ContextId key/value pair might be the safest route to avoid any issues in production.
OS
Osvaldo
1 year ago
I remember practicing a question about deactivating elements before moving to production. Maybe we should consider that option too?
LI
Lili
1 year ago
I think we need to update the ContextId value to match the production environment, but I'm not entirely sure if that's the only step we should take.
BR
Brendan
1 year ago
I feel like adding a Show/Hide condition could be useful, but I can't recall if it's necessary for this specific scenario.
PE
Pete
1 year ago
Ugh, I'm drawing a blank on this one. All the options sound plausible. I'll have to guess and hope for the best, but I'm not feeling great about my chances on this question.
AN
Annamaria
1 year ago
I have a feeling the "Enable Extend and Connect checkbox" might be relevant too, since it sounds like it could extend the voicemail reach to the right mailbox.