Unsupported Features › Considerations for Third-Party Web Controls

Considerations for Third-Party Web Controls

The following considerations are when using third-party Web Controls:

• ASP.NET Web Clients support Web Controls to the same level Visual Studio does. Problems identified in CA Gen ASP.NET Web Client must be proven to work in Visual Studio before CA can investigate them.
• Disable By is not supported for third-party Web Controls.
• Procedure Action Diagram access to Web Controls is limited to the current Procedure Step. That is, the GUI object representing the component cannot be passed using the views to another Procedure Step manipulation.
• Features that cannot be modified using methods and properties of a Web Control cannot be supported by ASP.NET Web Client. An example is specifying Sequencing of Tabbing among controls that are embedded on a Web control.
• Web Controls are only valid for a single window execution context. After another window replaces the current window (the window with the Web Control), the control is reinitialized on return. Additionally, any GUI Objects related to the control, which are held in the views, are then invalid. This restriction is dictated by the browser's caching mechanism and the stateless nature of Web applications.
• Validator controls are supported. You may add a Validator control to the Toolbox from the ASP.NET Control Manager, then select and place the Validator control from the Toolbox on to a web page. In CA Gen ASP.NET Web Clients, the name of a control becomes the ID of the control. The .Net Validator controls expect the ID of a control to be specified for validation. To specify which control to validate, type the name of the control to validate in the appropriate property of the Validator control (for example, in the RequiredFieldValidator control a property exists called ControlToValidate).

  Note: If you change the name of the control you are validating, you will also need to manually modify the Validator control's property.

  Container controls for ASP.NET Web Clients are an unknown entity at present. We have not found any ASP.NET Web Control that would be considered a “true” container control.

• Data-bound controls cannot be bound at design time. You can, however, associate them with data at runtime using the following techniques:
  1. Create the appropriate bound data type through the Action Block.
  2. Populate the data through the Action Block.
  3. Associate the data with the Data-bound control through the Action Block.

     Note: This requires a solid understanding of the Data-bound control and knowledge about how to create and populate the appropriate type for the Data-bound control.