Clients often ask how long it will take entity & criteria updates to
appear on their site. I haven't had a definitive answer other than "90
minutes or tomorrow morning" What is the rule of thumb for how long it
will take for an entity update to appear live, end to end, using
different methods of updating entities?getOffer parameter, such as:
https://mboxedge28.tt.omtrdc.net/m2/[clientcode]/mbox/json?mbox=mboxXYZ.....entity.id=1234&entity.inventory=0As
an example, when entity.inventory set to 0, ...
That article talks about escaping reserved characters ($) in a design
template (Velocity). My question was around escaping the value of the
entity's output. In particular, double quotes in content cause problems
when trying to generate JSON syntax or HTML attribute syntax.My
solution: Without the ability escape in Velocity, I escape the content
before uploading in the product feed. A good compromise for most
scenarios is to html encode double quotes to " . In practice that
is working well.In mos...
Jon, it's great to have you here! I see that you updated the JSON
documentation, which is great! I've been working with various Velocity
commands & discovered that the following works (adapted from your
example above):#* * "Return a simple list of recommended entity ids" *#
{ "notes":{ "purpose": "Return a simple list of recommended entity ids",
"use-case": "Use this approach if you prefer to do a real-time lookup of
entity attribute details (such as inventory, price, rating) from another
system...
Do Recommendations Designs support escaping of characters for formats
they need to be delivered in? This seems critical to producing valid
syntax in Design results. Examples: JavaScript needs escaped quotes (\"
and \'): entityTitle = "HD 48\" TV & speakers"HTML attributes need HTML
encoding " for double quotes etc:
Jon, that is a fantastic response, thank you so much. I'm still going
through it. A bunch of great info.What isn't clear to me is the second
issue of my original message: how do I keep entity values with single
and double quotes from breaking JSON syntax? Our product names have
measurements & possessives in them, so these are not uncommon. Given
that, what would keep this line in your code from breaking? "name":
"$entity1.name", when it becomes something like: "name": "Samsung's 32"
Television &...
I don't think that addresses it. Your linked doc discussed how to pass
JSON as a parameter INTO an MBOX request.The doc I linked to says that
it is possible to get JSON containing recommendations results/contents
OUT of Target... in the result of a mbox call. The purpose is to take
the JSON content and format it into results into HTML/etc on the client
side rather than having the Recommendations Design do it on the server
side.Thanks for the reply & your follow up!
On the Design Overview page of the Recommendations documentation it says
"Target can also return recommendations as a JSON object." It gives an
example output of the JSON that can be generated. However, the topic of
generating JSON is not discussed anywhere in that section. I imagine
this is either accomplished in a design or an mbox parameter, but I
cannot find any further discussion of the topic. How is this
accomplished?A related question: the documentation says that Designs use
Apache "Veloc...
