About plug-in properties

You must map the input and output properties of the components for each step with the input and output properties and variables of the service template. The input properties of the components used in a service template must be associated with the input properties or variables, or output properties of other component steps associated with a service template. The service template input properties store the input values that are required to run a service. The service template output properties store the results of running the service.

The value of the plug-in input property can be the value that you previously set for the property, or directly set for the service template. The input property can also be a variable. You can apply service share properties to the input properties.

The output property content depends on the type of component. You can store the result of running a step as output properties. Variables temporarily hold the values that are passed between components.

The input and output properties of the components are set from the Flow tab of the Service Builder Edit window. The input and output properties and variables for the service template are set in the Property tab of the Service Builder Edit window.

Input and output properties can store a maximum of 1,024 characters unless you specify "composite" as the data type for the Input/Output property. If you specify a value that is more than 1,024 characters without specifying the composite data type, the first 1,024 characters are stored as the property value and the remainder are discarded. If you reference the value of a property key in the format ?dna_property-key?, the referenced value is truncated if it is more than 1,024 characters.

A plug-in property with a property key and purpose, which are determined in advance, is called a reserved plug-in property. These properties specify credential information and the target hosts of remote commands.