How to stop unwanted screen-sets loading on your site?

[mshannon93]

We are having issues with default screen-sets loading on our website from the same API key, even though we don't reference those screen-sets in the code. We have noticed it appearing without the correct CSS and therefore causing issues. To stop this I have added a return false to the javascript within the screen-set javascript:

// Called before a new screen is rendered. This event gives you an opportunity to cancel the navigation by returning false.

onBeforeScreenLoad: function(event) {

return false;

},

Is this the best method to avoid unwanted screen-sets appearing from the same API key?

[olehi941]

Hello mshannon93,

"Is this the best method to avoid unwanted screen-sets appearing from the same API key?" - Yes, it is a good way to prevent some OOTB logic.

But at the same time, I would recommend you navigate to Screen-Set and check Screen after which you experience unwanted screen invoking/appearing.
Maybe there defined OOTB logic to invoke the next screen. You can change it by selecting:
- Submit (cancel screen)
- Close (cancel screen)
- Skip (got to next screen)
- And so on...

Attaching the screenshot just as an example.

Hope it helped.

[Preeti1]

Hi mshannon93,

SAP Customer Data Cloud does not impose any limit on the number of screen-sets that could be hosted in a single API key.

• Specify the custom 'Screen-Set ID' and custom 'Screen ID' in the code while loading the Gigya SDK.
• And in case of customized authentication flows, please ensure that respective custom screens are set as success screen in the UI Builder for seamless navigation.

Here is a simplified example in JavaScript using Gigya's accounts.showScreenSet method. This method is part of the Gigya SDK, and its usage might vary based on your specific implementation.

// Example using Gigya SDK

gigya.accounts.showScreenSet({

screenSet: 'CustomScreenSet', // Specify the name of your custom screenset

containerID: 'divContainer', // Specify the ID of the HTML element where the screenset should be rendered

});

Thanks,
Preethi G
SAP CDC Consultant

[shemma]

Hi Mark,

In response to your question, no, using this method may not be the optimal approach to prevent undesired screen displays. It's crucial to delve into the root cause of encountering an unwanted screen, as several factors could contribute to this issue:

1. An interruption from one of our services, such as completing the registration process.
2. Defining a success screen in the admin console.

I recommend reaching out to our support team to discuss your business requirements and needs.

By explaining your situation, we can assist in configuring the appropriate behavior and flow.

Regarding the "onBeforeScreenLoad" event, it is accurate that returning false can prevent the screen from rendering. However, this might lead to unintended consequences if additional steps are required on the subsequent screen. In most cases, this event is used to transition from the current screen to a different one, when applicable.

[romaingorrias]

Hi Mark,

You can try to mitigate that by specifying the default screensets in the UI builder app in the console, and set them to your own screensets. This might not solve all instances of this issue but it's a good place to start.

You can double-check the configuration by loading gigya.js and checking the values of defaultRegScreenSet & defaultMobileRegScreenSet

 "defaultRegScreenSet": "Default-RegistrationLogin",
 "defaultMobileRegScreenSet": "Default-RegistrationLogin",

Regards,

Romain.