The CreatorCon Call for Content is officially open! Get started here.

Amit Gujarathi
Giga Sage
Giga Sage

UI Builder Defect Notification: Proactive Solutions

 

Understanding the UI Builder Error and Its Impact

The recent identification of a defect in the Vancouver version, particularly related to the UI Builder, has raised concerns for users. Upon upgrading, a critical error message "Internal Server Error (500)" appears, hindering the functionality of the Page or Variant in the UI Builder. This problem specifically occurs when the instance includes a manually created system property com.glide.script.interpret.short.expressions.threshold with a non-default value.

 

Identifying Affected Instances

A thorough assessment indicates that several production instances with this manually created system property are either already operating on Vancouver or are potential upgrade candidates. This defect poses a significant risk to operational stability and performance.

 

Proactive Measures and Maintenance Schedule

In response, a proactive strategy has been formulated to address this issue. The key step involves deleting the manually created com.glide.script.interpret.short.expressions.threshold system property. This action is pivotal in realigning the system with the default built-in value, thereby mitigating the risk of encountering the error.

 

Scheduled Maintenance Details

  • Anticipated Impact: It is important to note that this maintenance is expected to occur without any downtime or adverse effects on the system's performance.

Opt-Out Option and Alternative Solutions

For instances where the scheduled maintenance is not feasible, an "Opt out" option is available. This can be executed via the Communication Record on the portal, followed by instructions in the Workaround section of KB1541877.

 

Additional Resources and Support

For further details regarding this issue and the planned maintenance, users are encouraged to consult KB1541877. This knowledge base article offers comprehensive insights and guidelines on managing the defect effectively.

 

Conclusion

The proactive steps taken to address the UI Builder defect in the Vancouver version demonstrate a commitment to ensuring system reliability and performance. By aligning with the maintenance schedule or opting for alternative solutions, users can effectively navigate this challenge with minimal disruption.

Comments
Badal Khojare
Mega Sage

Great information! Just to add deleting the property will consider the built in default value which is 500000 for Vancouver instances. The property may though not be visible in sys_properties table.

Michael Stehr
Tera Contributor

Great info Amit

But even this sys_property has been deleted in my instances, I'm still getting the "Internal Error 500" when trying to edit anything....

MichaelStehr_0-1702386757270.png

Any idea?

MGanon
Tera Guru

I renamed the property so that it would not be used. I still get the same error. What else can cause it?

 

Also, how is the system property "manually created" since it appears in many (if not all) instances? How can the value be changed from the default value if the created/updated and created by/updated by fields match?

CharlotteW
Giga Explorer

Please do someone know, or might have find, another solution to this problem besides deleting this property?

Darren Lau
Kilo Sage

Deleting this property worked.  We are on Washington Patch 4 Hotfix 1a.  I also looked at KB1541877.

Version history
Last update:
‎11-23-2023 08:48 PM
Updated by:
Contributors