Skip to main content

OmniScripts, when deployed via MDAPI with the attribute <isActive>true</isActive>, are deployed as Active. However, they have to be manually inactivated and activated again in order to apply changes on Experience Cloud pages.

Questions:

1. Is this Known Issue related to such behavior?

2. Is there a way to script inactivation / activation of OmniScript properly? I tried to update OmniProcess object record from a script - the OmniScript's status has been updated, but it has no effect untill, again, manually inactivation and activation.

 

I understand this is how it is designed (look here), but wonder if there a way to automate OmniStudio deployment from end to end.

 

(cross-posted from Salesforce DX community post)

답변 2개
  1. 2023년 2월 14일 오후 8:10

    Hi Manikandan,

    Thank you for the suggestion.

    I installed the OmniStudio v242.4 package (Spring '23) and enabled the Standard OmniStudio Runtime. I updated the OmniScript (manually updated  some text on the XML file) and deployed the update to the existing active OmniScript version. The update is still not visible until the OmniScript is deactivated and actived again - manually.

    I wonder if it is possble to trigger OmniSript deactivation (when done manually, there a pop up window indicates 2-step process that takes a few seconds with Path-like progress bar) and activation (when done manually there is a popup window indicates 4 steps process that take a bit longer with Path-like progress bar).

    Do you see a different behavior on your side?