Create model data namespaces for application-provided screens

You can create model data namespaces for source bindings and target bindings for application-provided screens.

namespaces: {
    sourceBindingNamespaces: [{
	       description: 'Initial input to screen',
	       value: 'screenInput'
    }, {
	       description: 'The list of organizations the current user can search for orders with.',
	       value: 'getOrganizationList_output'
    }, {
	       description: 'The response from the getOrderList mashup',
	       value: 'getOrderList_output'
    }]
}

namespaces: {
    sourceBindingNamespaces: [{
	       description: 'Custom namespace added in extension',
	       value: 'extn_getOrganizationList_output'
    }]
}

If a mashup reference definition is present in InitController, the same namespace must be present in the sourceNamespace property. If, BehaviorController is involved, do a set model with the same namespace.

To define a namespace for target binding in extended screens, add the namespace definition in the targetBindingNamespaces property. An example of the application-provided namespace for target binding definition is as follows:

namespaces: {
    targetBindingNamespaces: [{
	       description: 'The input to the getOrderList mashup.',
	       seq: '1',
	       value: 'getOrderList'
    }]
}

In the extended screen, add the target binding namespace as follows:

namespaces: {
    targetBindingNamespaces: [{
	       description: 'The input to the getOrderList mashup.',
	       seq: '1',
	       value: 'extn_getOrderList'
    }]
}