Hi @sidkgoel ,This was an underlying issue with the API itself not with
the UI. So there is currently the ability to delete the base
connection/account, but if you were to attempt to recreate a base
connection using the same exact name, it would fail and give an error
claiming that the name of that connection has already been used.
Whatever process the deletion request is initiating in the background
isn't fully functioning as expected.
Hi @NimashaJain I am trying to integrate Deliver offers using the
Decisions API using Java as backend but I'm not able get the schema
could you suggest how I can get the schema details for the above schema.
I can't find much about the integration examples using Java with Deliver
offers using the Decisions AP...
I feel your pain. 😣 Should the link destination be included in the
postMessage and then the actual navigation be handled from the parent
page by Launch after the custom link fires? Or should the parent
postMessage back to the iFrame after the custom link, so the navigation
can proceed?I think the second option is "safer", because it should
ensure that Launch has sent the Custom Link beacon before navigation
happens. But that means your users could have a longer delay between
clicking a link to ...
Hi @Luca_Lattarini , That's something my org is doing. It works the same
way as enabling SSO/SAML within your instance of Admin Console, and is
already pretty good granularity of permissions that can be specified
within product profiles. As a note, there are some workflows within
these apps that might require some access to AEP as well. So it would be
best practice to put your CJA/CJO users in a given user group and then
assign both the corresponding product+AEP product profiles to that user
With regards to observation 4, when constructing the XDM for HTTP API
(stream) ingestion, there are two fields that seem to be optional and
don't serve any purpose:1. There is a "flowId" field that can be
included, ref, but that same field isn't specified in the API request
body documentation, here.2. There is a field in the request body schema
called SOURCE_NAME which is optional, but it seems this value can be set
to anything without impacting the ability to ingest the data. For
Hi @jk,Yes, unfortunately, it is true that not all products allow you to
add developers. What I am intrigued by is whether this functionality has
really changed - is it really true that you could add developers to all
products earlier (even if it was through the blanket route)? Either way,
it would be helpful to know which products you are trying to add
developers to. I can at least give those teams a heads up about this
gap. Adobe Developer Console Team