Integrate Software AG Products Using Digital Event Services : MashZone NextGen Help : Appendix : Legacy Presto components : Mashables and Mashups : Mashups in MashZone NextGen Wires : Creating Mashups in Wires : Add Actions or Other Blocks : Add Input Parameters
Add Input Parameters
The Input action block defines an input parameter for the mashup. You and other users can use input parameters to dynamically control the information or behavior of the mashup. Mashup input parameters can assign values to virtually any block property within the mashup for any number of blocks.
There are several ways to add an Input action block and connect it a block property for another block:
*Automatically Add Input Fields for Block Properties
*Select an Existing Input Block for Block Properties
*Manually Add and Connect Input Blocks to Block Properties
See also Changing Mashup Input Parameter Names.
Name
Wires provides a default input parameter name when you add Input to a mashup. If this mashup has not yet been turned on, you may change the name of an input parameter.
Important:  
Never change the name of a mashup input parameter once you have turned a mashup on. This can cause apps or other mashups that use this mashup to fail.
Input parameter names must be unique within a mashup and valid. See Valid Input Parameter Names for specific details.
Data Type
Optionally, choose the type of data that goes in this input field:
*boolean for true/false data.
*datetime for dates, times or combinations in one of the valid date or time formats. See Date and Time Formats, Math and Sorting in Wires for more information.
*date is deprecated. Use datetime instead.
*decimal for decimal numeric data for mashables.
*document for complex input with a hierarchy. The data must be a well-formed XML document.
*integer for integer numeric data for mashables.
*number for numeric data of any type for mashups.
*string for text data.
Default Value
Optionally, enter a default value for this input field.
For document-type parameters, you can enter a default value as a well-formed XML document. The entire structure must be contained within one XML element. For example:
<name>
<first>Ethan</first>
<last>Fromme</last>
</name>
Copyright © 2017 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback