SOLVED
Use of variable in continuous delivery, how to do ?
1 Accepted Solution
Correct answer by
Hello,
The error is okey 
but make sure you are using the right instance variable and actually it is better to use alert activity instead of delivery.
The workflow can look like the one below:
where:
- query population you want report on
- java script activity where you save population from query to the instance variable
- also you can write this code into the initialization script of the alert activity instead of having JS activity in the workflow
- test activity is checking population count > 0 in which case it will send alert message to any operator or group
- alert where you loop over the population and make e.g table from it, which will be send alert to operator
Marcel
Hello Celine,
so you have output from workflow and you want send the information in the pipeline to some operator, right?
If this is the case (hope so) you need to collect data stored in the pipeline and display them in the delivery (alert to operator).
It can be easily done by:
Either adding java script code in the activity before the delivery or you can actually paste JS code right into the alert or delivery itself.
1)
Add JS activity before delivery and check name of activity before.
var query = xtk.queryDef.create(
<queryDef schema="query" operation="select">
<select>
<node expr="fields_from_select1"/>
<node expr="fields_from_select2"/>
</select>
</queryDef>
);
instance.vars.items = query.ExecuteQuery();
EDIT:
<queryDef schema="temp:query".....
it should be temp:activity_name
2) Add JS code to the delivery activity
you need to loop data saved in instance.vars.items and display them in the email contents:
<% for each (var item in instance.vars.items){ %>
<%= item.field_from_select1 %>
<%= item.field_from_select2 %>
<%= item.field_from_select3 %>
<%}%>
Write JS code in the source mode
<% %> for JS code
<%= %> for writing JS code to the output
You can create e.g. table to display the data.
All put together
BR,
Marcel
Correct answer by
Hello,
The error is okey
but make sure you are using the right instance variable and actually it is better to use alert activity instead of delivery.
The workflow can look like the one below:
where:
- query population you want report on
- java script activity where you save population from query to the instance variable
- also you can write this code into the initialization script of the alert activity instead of having JS activity in the workflow
- test activity is checking population count > 0 in which case it will send alert message to any operator or group
- alert where you loop over the population and make e.g table from it, which will be send alert to operator
Marcel
Hello Marcel.
I had a problem with the instance variable, wich appeared to be considered as a String and not as an XML element.
I just add a lign in the script and it's OK :
Thank you very much for your help,
Céline
Hello David,
you do not have to use "Add data" because the data you are querying are there but under the target element that means you need to query e.g. not @label but [target/@label] or @internalName but [target/@internalName]
To get idea what you can bring to the alert pause the alert activity and look at the target in it by right click on the pipeline.
But if you add additional data of the same filtering dimension you will not have to use this target prefix
Alert activity could look like this:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
</HEAD>
<BODY>
<P>
<%
var query = xtk.queryDef.create(
<queryDef
schema="temp:queryToPick" operation="select">
<select>
<node expr="[target/@label]"/>
<node expr="[target/@internalName]"/>
<node expr="[target/operation/@internalName]"/>
<node expr="[target/operation/@label]"/>
</select>
</queryDef>
);
var items = query.ExecuteQuery();
%>
<P>List of failed workflows in the last 30minutes </P>
<TABLE>
<THEAD>
<TR>
<TD>Workflow</TD>
<TD>Internal Name</TD></TR></THEAD>
<TBODY>
<% for each (var item in items){%>
<TR>
<TD><%= item.target.@label %> ( <%= item.target.operation.@label %> )</TD>
<TD><%= item.target.operation.@label %> ( <%= item.target.operation.@internalName %>
)</TD></TR>
<% } %>
</TBODY>
</TABLE>
</BODY>
</HTML>
Hope this helps.
Marcel
Hello Andy,
thats adobe's stuff you can ignore that error or move the js code to the delivery itself. But why you use delivery activity and not alert activity?
Marcel
Hi Andy,
what you are doing will not work in delivery activity.
Reason: An instance is an object of the workflow, so your instance variable or variable is only available in the workflow execution instance. These variable are not available to MTA(while preparing email delivery personalization) that's why you are getting this error.
Option 1 you can define a new variable at the delivery label and store this variable in the delivery variables.
option 2: use alert activity and you will be able to use your code as is
option 3: add this value as new personalization object in delivery visa delivery advanced properties.
Option 2 will be easy to implement.
Regards,
Amit
Related Conversations
