Skip to main content

I am using an OmniScript to capture user input in order to create a record, and it is deployed on an Experience Cloud (Community) site. However, the OmniScript is not visible to external or guest users. 

 

I have already created a permission set and granted access to the OmniScript standard objects to the guest user, but the guest user is unable to view the OmniScript on the public community site.

 

I have added the same OmniScript to the Lightning page, and it is visible there. However, on the public site, it is not visible to the guest user even after providing all the necessary access to the guest user profile.

Below are the screenshots where I am getting the error message. 'This OmniScript is either inactive or has been replaced with a new version which has not been deployed

.' 

 

Please help me identify what I might be missing. 

Omniscript not visible to guest user on public experience site

 

image.png

 

  

 

#Vlocity

2 Antworten
  1. 26. Dez. 2025, 12:23

    Hi @Ajeet Mahor

    , 

    Thank you for reaching out to the community.   

     

    May I recommend you to please check the following? 

     

    1. Configure Sharing Rules (Crucial) 

    Guest users must have Read access to the OmniScript metadata records itself through Criteria-Based Sharing Rules. 

    • Object: Omni Data Transformation (for DataRaptors) and Omni Process (for the OmniScript itself).
    • Criteria: Set a criteria such as Active = True or Type = [YourOS_Type].
    • Share with: Select the Guest User of your specific site.
    • Access Level: Read Only. 

    2. Verify "Public Access" Settings

    Even if the page is public, the guest user profile must have the execution permission enabled: 

    • In Experience Builder, go to Settings > General.
    • Click the Guest User Profile link.
    • In System Permissions, ensure "Enables consumers and partners to execute Omniscripts, DRs, Cards..." is checked. 

    3. Grant Apex Class Access

    Guest users need permission to the underlying Apex controllers that run OmniScripts: 

    • In the Guest User Profile, navigate to Apex Class Access.
    • Add the following classes (namespace varies if using Vlocity Managed Package):
      • omnistudio.BusinessProcessDisplayController (or vlocity_ins / vlocity_cmt equivalent)
      • omnistudio.ComponentController
      • omnistudio.NewportUtilities (if using Newport theme) 

    4. Enable "LWC OmniScript" Deployment 

    If you are using the Standard OmniStudio runtime (LWC), the error can appear if the LWC code for that specific version was not successfully generated: 

    • Deactivate and Re-activate the OmniScript. This triggers a fresh deployment of the LWC.
    • Ensure there are no missing custom LWCs embedded in the script, as this can block the activation process from completing the deployment. 

    5. Check Content Security Policy (CSP) 

    • In Experience Builder > Settings > Security & Privacy, check the CSP level.
    • If the script relies on external resources, you may need to change the security level to Relaxed CSP or add specific Trusted URLs for your site. 

    Please feel free to let me know if you need any more help with this.  

       

    Please mark this as the best answer if it solves your issue. This will help the community consider this a reference and avoid creating multiple questions on the same concept.   

       

    Have a great day ahead!  

       

    Thanks & Regards  

    Nagarjuna 

0/9000