Hi,
I am working on the “Configuring conditional visibility in Constellation Views” challenge in Constellation adoption course, I see there are many 400 errors from the DX API in the browser Developer tool . Please find the details attached. The system is working correct but how 400 error is appearing is my concern. Any help will be appreciated.
Thanks,
Nilutpal
@NeelDas The 400 Bad Request Error in the “Configuring conditional visibility in Constellation Views” challenge often occurs due to invalid data being sent through the DX API. To resolve this, ensure the visibility conditions are correctly set with valid property references and matching data types, as mismatched types can trigger the error. Review the Network tab in the browser’s Developer Tools to inspect the API payload and verify that no required fields are missing or incorrectly formatted. Clear your browser cache and reload the application to avoid old configurations causing issues. Simplify the visibility condition by starting with a basic rule and gradually adding complexity to identify the error source. Check if any Data Transforms used in the visibility logic are functioning correctly and returning expected results. Also, ensure all application artifacts are properly saved and updated. If the issue persists, reviewing the DX API logs for detailed error messages can help pinpoint the problem. If needed, consider reaching out to Pega Support with the error details and API payload for further assistance.
This is a GenAI-powered tool. All generated answers require validation against the provided references.
@SairohithThanks for your suggestion. I didn’t try all steps but I didn’t face such issue in Community version. Sems its a system configuration issue.
Did this happen only once, and are you no longer experiencing the issue?
hi i
see this issue of bad request in course
challenge ,my observations so far:
1.the issue occurs when you try to combine a partial view (review inner ) with the editable data (user consent).
if user consent alone configured no issue observed.
however when reveiw inner alone is configured the issue is happening .
on further analysis it can be observed from exercise system.
these sections are configured and if Product details is removed the entire UI is working.
1.Contact Info
2.Determine Category.
3.Product Details.
4.Service Details.
5.Resolution Method.
The data capture between the screen for a radio control and this data reference is not showed in the form after a screen navigation.
So the old pega instances load the entire data page usually so need to check why Pega is not bringing the Entire Product page in this load and retaining that .
this is the Payload the Pega API is receiving in the post processing and when merge is trying to happen with case BLOB system is throwing a 400.
on load of UI workpage using PCOre :
See the Attachment :
on submit:
{“content”:{“UserConsent”:true,“PrivacyPolicy”:true,“Product”:{“pyGUID”:“”}},“pageInstructions”:}
please let us know what mechanism to be followed here to get this kind of scenario to work.
Thanks
APIDetails.txt (105 KB)