Supported data types

Built-In SimpleTypes: binary, boolean, byte, date, decimal, double, float, integer, long, short, string, time, time stamp

Not supported data types

Further dictionary types (predefined types, for example, currency), core data types (for example, amount, duration, attachment), Java native types

For more information about limitations on data types, see the SAP Note 1337578.

Reverse Context Mapping

Web Dynpro component’s interface controller context nodes have the property Input Element set to true. This feature is to use context nodes of an outer loading component via static component usage from within an inner loaded component.

Since SAP NetWeaver BPM uses dynamic component usage from a generic outer loading component this property must be set to false.

Model Binding

Web Dynpro component’s interface controller context nodes, which are bound to a Web Dynpro model (CMI) are instantiated after the point in time when BPM can access the Web Dynpro context. Due to this the use of Web Dynpro context nodes, which are bound to a used model are not supported.

Corresponding exception:

Error while trying to retrieve the task: NodeElement(.DisplayResults.Data): model node element cannot be created without a model instance [EXCEPTION] {0}#1#com.sap.tc.webdynpro.progmodel.context.ContextException: NodeElement(.DisplayResults.Data): model node element cannot be created without a model instance

Dynamic Context Structure Modification

In Web Dynpro it is possible to change the Web Dynpro context structure programmatically at runtime. The Web Dynpro developer is free to generate, for example, the complete context’s structure if necessary. For the creation of the runtime data, mappings and rules, BPM takes the Web Dynpro component’s structure from the introspection of the component at design time.