Locked Out of Your PDI After Enabling AIUX? - Brazil Version

[Gokul_SNOW]

Recovering a Locked-Out PDI After Enabling the AI-Native User Experience (AIUX)

If you recently enabled the system properties aiux.experience or aiux.on_off_user_pref_enabled on your Personal Developer Instance (PDI) and found yourself completely locked out or facing a blank page, you are not alone.

Because the AIUX framework renders pages on entirely new infrastructure, a severe layout breakdown can hijack primary UI page routing, causing normal table endpoints to throw routing or frame-rendering errors.

If you are completely locked out, here is an advanced recovery method that may help you regain access without wiping your data.

1. Mobile UI Endpoint Bypass (Recommended)

The AIUX rendering engine primarily targets desktop workspace frameworks. In many cases, the legacy mobile web framework remains unaffected and allows access to update the problematic properties.

Steps

1. Modify your PDI URL to point directly to the classic mobile interface:

   https://devXXXX.service-now.com/$m.do#/form/sys_properties/65a36c7f1b9807109ac055f0604bcbb5?sysparm_view=Mobile

2. If the page loads successfully, use the simplified navigation menu to locate System Properties.

3. Search for the property:

   aiux.experience

4. Change its value to:

   false

5. Save the record and refresh your instance.

This should restore access to the classic user interface and resolve the AIUX routing issue.

---

Thanks,
Gokul Subramaniam

---

💡 Tip: If the property above is not sufficient, also verify that aiux.on_off_user_pref_enabled is set to false, then clear your browser cache and reload the instance.

[glideFather]

ahoy @Gokul_SNOW,

I haven't got into such a situation so I am wondering... when you are locked out how can you then access system properties?

Also, are there any situations when the aiux.experience should be true? If not, then you can proactively change it to false to avoid that from happening maybe?

[Gokul_SNOW]

@glideFather  In my case, when I say "locked out," I don't mean that I couldn't reach the instance at all. The AIUX property caused the primary UI routing to break, so navigating through the normal interface resulted in blank pages and rendering errors. However, the legacy mobile interface ($m.do) was still accessible, which allowed me to get to the System Properties record and revert the setting.

[Dr Atul - LNG]

Thanks, buddy. Over the last two days, I’ve had to reset my PDI three times because this property has messed everything up and caused things to stop working. @Gokul_SNOW 

[Gokul_SNOW]

No Problem!! 😊 @Dr Atul - LNG 

The funny part is that I actually updated the property after watching your Brazil release video. Even though you mentioned that it could cause issues, I still wanted to test it on my PDI to see whether I would run into the same problem or not.

Well, I definitely did! 😄 But on the bright side, it helped me discover the solution, which ultimately turned into a useful workaround for others facing the same issue.