CloudStreams allows you to modify the behaviour about how properties take values at run time. You can assign override values from Header, Connection Parameter, Service, Parameters, and Literal to Connection group and Authentication group properties. You can also assign override values to resource request parameters, resource request headers, and from response headers. When you assign an override value, you can either hard code a specific value, or assign a default value to a variable, that is, a value that is only assigned if the variable is null at run time, or assign a value of another variable by referencing the variable. See Assigning Values for more information.

CloudStreams supports two abstract object types: BusinessObject and SchemaObject. A Business Object represents business entities such as an invoice or a transaction. Some SaaS providers expose these business entities, and for those back ends, you need to create abstract objects so that you can dynamically create the signatures.

So for back ends to represent business entities correctly and also to reduce the effort needed to get information for each entity, you can abstract the back end entity by defining appropriate abstract object types. You need to create a Document Type (DocType) that will be used to create the abstract object type and to get information about those objects, you must also implement two look up services. The look up services are like dynamic calls to the back end to list and describe the back end entities.

CloudStreams currently supports the data types String and Record. CloudStreams also provides a parameter formatter which enables you to format input data into a custom format as desired. Alternatively, in cases where the default parameter formatter is not sufficient to achieve the desired parameter behavior, you can write a custom implementation for the parameter formatter.