If you’re using the 6.0.1 release, there’s a manual in [install path]\Developer\doc\guides called ISDSPs&TemplatesGuide.pdf. Chapter 2 has a section called “Using the DSP Tags” that tells you how to use variables.
The simplest way is to use the syntax %value yourVariable%.
If the variable you are trying to include in the template is in plain view (i.e. not in a Record, Record List, etc), the %value% tag will give you the results you need.
Remember that DSP is case-senstive when writing your template.
I’d like to add to Dan’s comment - since you don’t have the value coming in from the pipeline, using %value yourVariable% wouldn’t be able to retrieve the value since it’s not in your pipeline. But you could put the following at the beginning of your dsp page:
%value yourVariable null=‘my value’% (assigns the initial value)
Since ‘yourVariable’ won’t be in the pipeline (as you said you didn’t want to initialize it in a flow service), the dsp would set the value appropriately before you use it later in the dsp.
I don’t know if I am missing the point, but when I am in a .dsp and want to create a variable that I use in either a later .dsp or in an invoked service i simply use %scope param(newVariable=‘something’)%
Hi,
If the need is to create a few variables in order to display the output, then you can do it using javascript.
<script>
var newVar = ‘%value myVar%’;
</script>
and in scripted the variable "newVar " can be used to show the output.
Using Java script one can define arrays and store the values of record from the service into an array declared in JavaScript.
You can do one thing , use %endscope% after the retrieval purpose… Like this
…new variable definition
%scope param (newvar=“Dummy”)%
…PipelineOutput contains the flowservice output
%scope PipelineOutput%
…
…
…I want to use/manipute the “newvar” here
%value …/newvar%
%value /newvar%
%value newvar%
%endscope%
%endscope%