The Real-Time Designer's Scene Composer enables you to capture a snapshot of an application, which is called a scene, and then use that snapshot to capture the control(s) the scene contains. Typically, a scene is a window or page in a target application that contains one or more controls, such as a calculator, a tab in a CRM application, or a particular page on a website.
Before you begin designing a project, perform connectivity analysis to determine the best method for capturing the controls in the target application. If the controls can be captured using the standard method described in Physical Objects, then that method is preferred. However, if one or more controls cannot be captured using the standard method, use the Scene Composer for capturing, as described in Working with the Scene Composer.
In some cases, the Scene Composer connectors can provide functionality that does not exist with any of the Screen Element connectors, such as General controls and ActiveX control functionalities. In other cases, the Screen Element connectors can provide functionality that does not exist with the Scene Composer connectors, such as WPF connector, Siebel connector, Terminal connector, and SAP connector functionalities.
The key conceptual difference between the Scene Composer and the Physical Objects modules is that in the Scene Composer you work on a business scene, rather than a single, specific control, as in the Physical Objects module. For example, you can define a specific website page as a scene, such as a page that is used to create a customer and enter their details.
For a list of available screen connectors and extensions, see Connectivity IDD - RTI.
From Real-Time Designer version 6.7, you can simultaneously use scenes in more than one solution. The scenes must have unique names across all the solutions in use.
