Hi @AARTHYPEGA

I noticed you hadn't received a reply on your Question about Pega Cloud and I wanted to see if you had found the solution to your question. If you haven't, I wanted to direct you to one of our new Expert Circles that I think will be helpful in recieving a reply! I'd like to suggest reasking your question in our Pega-as-a-Service Expert Circle. Our Expert Circles are pretty active and I think it's the best for you to get a quick reply!

Let me know once you've posted and I'll see what I can do to help you receive a reply!

@AARTHYPEGA

don’t point an AVRO schema’s Application setting to a Data Page. That field is validated at save time, not at run time, so Pega expects a literal URL that already starts with https. When you reference a DPage, the rule form sees a token (not a URL), fails the SSL check, and throws the “Provide a URL starting with https://” error. Fix it by defining a real Application setting of type URL and give it per-environment values (Dev/Test/Prod) that are full https URLs to your schema registry. Then select that Application setting in the AVRO rule. If you need more indirection, store the URL in a DSS per environment and have a startup job or small utility set the Application setting from the DSS, but keep the AVRO rule bound to a literal Application setting value. Also confirm “Use SSL” is enabled on the AVRO/Kafka side and that your URLs truly use https (no trailing spaces, no http redirects). If you must build the URL dynamically, do it outside the AVRO rule (e.g., resolve via DPage in a pre-flow step) and write it into a property the connector uses, but don’t feed a DPage into the Application setting picker. This is expected behavior/limitation, not a defect; open a support ticket only if a literal https URL still fails validation.