error 500 during Variants creation in ui builder .

[Community Alums]

I am unable to duplicate or create variants of a dashboard page on my custom workspace. 

[Ranjit Nimbalka · Accepted solution]

Hi @Community Alums ,

please go through this blog that may help you:- 

https://www.servicenow.com/community/developer-articles/ui-builder-defect-notification/ta-p/2742155#:~:text=Understanding%20the%20UI%20Builder%20Error%20and%20Its%20Impact&text=Upon%20upgrading%2C%20a%20critical%20error,script.

Regards,

Ranjit

[Ranjit Nimbalka · Accepted solution]

Hi @Community Alums ,

please go through this blog that may help you:- 

https://www.servicenow.com/community/developer-articles/ui-builder-defect-notification/ta-p/2742155#:~:text=Understanding%20the%20UI%20Builder%20Error%20and%20Its%20Impact&text=Upon%20upgrading%2C%20a%20critical%20error,script.

Regards,

Ranjit

[Ranjit Nimbalka]

Hi @Community Alums ,

Thanks for marking my answer as helpful. If it helped you in any way please accept the solution so that it will be beneficial to the future readers with the same query.

Regards,
Ranjit

[Community Alums · Accepted solution]

Hi @Community Alums ,

"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.

[MGanon]

Did this help? It didn't help my instance.

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