Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

The element type "td" must be terminated by the matching end-tag "</td>".

sanjeev28 k
Giga Expert

Hi All,

I have issues due to fuji upgrade. I am not able to see the items on the checkout cart for which I have requested for.

Moreover I am seeing two macros "servicecatalog_checkout_one" and "servicecatalog_checkout_one_v2" in fuji version which was not earlier in Eureka version.

And when   I "try it " the   " servicecatalog_checkout_one_v2" , It gives the error- The element type "td" must be terminated by the matching end-tag "</td>". Any suggesstion? .

service.JPG

8 REPLIES 8

sanjeev28 k
Giga Expert

Hi All,



A little mistake, servicecatalog_checkout_one_v2 & servicecatalog_checkout_one are not macro , These are UI pages


Hi


The UI page code OOB.



<?xml version="1.0" encoding="utf-8" ?>


<j:jelly trim="false" xmlns:j="jelly:core" xmlns:g="glide" xmlns:j2="null" xmlns:g2="null">


              <g:requires name="scripts/js_includes_catalog.js" includes="true"/>


              <g:requires name="styles/js_includes_catalog.css" includes="true"/>


              <g:requires name="styles/sc_cat_only.css" includes="false"/>


  <j:set var="jvar_two_step" value="true" />


              <g:inline template="sc_sanitize.xml"/>


  <g:servicecatalog_cart_template />


</j:jelly>



It doesnt show any td tags. So if the UI page is customized/modified, please share the code or check for any entries with the <td> tags


It happens when building reports too.   Spent 4 hours building this afternoon and now none of them can be updated.
Fuji Patch 7


I was receiving this issue today. I checked the log, and saw:



The 'Report Users and Groups' record is in application 'scopedapplication', but its 'Report' parent record is in application 'Global'. The record and its parent must be in the same application.: no thrown error



Changing my application back to Global resolved this issue for me.