Plex Model Configuration

Plex Model Configuration


In order for Plex Java functions to work with CM WebClient, each panel function must inherit from a WebClient base function. This function is called ~WebShell and it is located in the WebClient group model. This section explains how to set up CA Plex local model to work with the WebClient pattern libraries. This document applies to CA Plex version 6.1 and above.


The actions described in this document must be performed the first time you use the WebClient patterns in CA Plex models.

The first thing to do is to add WebClient group model to the host group model of your application. This action is performed once per group model in the same way as adding any other library models to a host model. The Web Client library may be added during creation of a group model together with the CA Plex Pattern libraries and other library models needed by the model, or they can be added to an existing CA Plex group model.

Once WebClient library is added to the group model and a local model has been defined, the objects in WebClient library models must be extracted to the local model.

All Plex functions with panel should inherit from WEBCLIENT/~WebShell before generation. The FNC is ~WebShell should be the first triple in the pattern inheritance.

CM WebClient can only support the Dialog and Child Panel window types. For TabStrip and FrameProperty, if the function has FNC is ACTIVE/TabStrip, the function should inherit from FNC is WEBCLIENT/~TabStrip directly. If the function has FNC is UISTYLE/FrameProperty, the function should inherit from FNC is WEBCLIENT/~FrameProperty directly.

To display web messages in web page, a Plex function should inherit from WebMessages (which should inherit from ~WebUI). WebMessages is a predefined page template that can serve as an example for your own page templates that display messages.

For example: XXX is a FNC WebMessages

WebMessages is a WEBCLIENT/~WebUI

WebMessages impl name NME WebMessages

In the inheritance path for a WebClient function, the root template(WebShell) must precede page templates(WebMessages) for WebMessages to work. The Plex function should have triple inheritance path in the following order.

For example: XXX is a FNC WEBCLIENT/~WebShell

XXX is a FNC WebMessages

To enable exporting grid records in a csv format, a Plex function should inherit from WebExportGrid.

For example: XXX is a FNC WebExportGrid
Plex v6.1/Plex v7.0 Model Configuration

    • Related Articles

    • Upload CA Plex Model to CM evolveIT For CA Plex

      Open in Chrome browser Click the Sign In text item Login Open CM evolveIT Customer Portal Click CA Plex Model option Enter email address This process will validate user is registered Enter Model ...
    • Configuration

      Verifying the initial configuration After the installation has completed, navigate to the following URL in a web browser: http://localhost:8082/ It may take a few moments for the server component to initialize. Once the page has loaded, you will see ...
    • Obtaining model counts for pricing

      Please follow the procedure below.   Here is the SQL code that can be run  by a CA 2E customer to obtain CA 2E Model  Object Counts. After you send the values to us, we can provide quick guidance on costs and timeframes for a model migration Note: ...
    • How do you use the CM Matchpoint Plex AutoGen Product

      Here is the contents of the Read Me file How to use: 1. Create List, Package or SubjectArea in your model and define them to GenReq.json file 2. Set roperties Plex_GenOptions.json 3. This tool uses Plex Model API, make sure there is NO Plex.exe ...
    • Sending CA 2E Model for Analysis, or for a POC

      If you would like to send your CA 2E Model to us to for Analysis or for a proof of concept, please follow the instructions in the attached document.