QAT Function Manager
QAT Function Manager is a tool offered by QAT Global to manage custom functions for CA Gen 7.6 and CA Gen 8.0. Most Gen developers are familiar with the native functions available in any CA Gen model, such as concat, substr, textnum and others. When building statements inside an Action Diagram, developers can select these functions, which are part of a static and limited list.
It’s Fast and Simple!
- Define or Import Custom Functions.
- Register Custom Functions into Gen Models.
- Define and Compile Custom Function Code into Runtime Library or Implement Third Party Runtime Library.
- Add Action Diagram Statements to Gen Applications Using Custom Functions.
- Generate and Install Gen Application.
You can benefit from Custom Functions now!
See our growing list of available functions in the QAT Function Libraries!
GOOD NEWS: QAT Function Manager enables you to create and manage your own functions.
- QAT Function Manager enables your developers to manage Custom Functions for CA Gen. Individual Custom Functions can be defined or entire function libraries can be imported and registered to any CA Gen model.
- Once a Custom Function is defined within QAT Function Manager (user defined or imported), it can be registered to any CA Gen model, which adds the Custom Function(s) to the available function list in the model.
- For Custom Functions, QAT Function Manager generates the source code stubs for any platform. The source code is completed by the developer and compiled into a runtime library.
- QAT Function Manager allows for complex or highly reusable routines (including Gen Action Blocks) to be executed with a single function statement.
- QAT Function Manager makes it easy to get more from CA Gen.
- QAT Function Manager provides a fast and easy way to define and manage Custom Functions for CA Gen.
- Custom Functions are productive for developers because they don’t require subsetting or traditional view matching.
- Custom Functions are easily shared both internally and externally using the Custom Function Libraries created by QAT Function Manager.
Using QAT Function Manager with your CA Gen models is simple.
The main window has two distinct areas:
- The available custom functions are displayed in the left pane. Libraries containing custom functions can be purchased from third parties and imported, or you may define your own functions and libraries using the tool.
- The right pane displays the functions that are registered in the currently open model. This pane can also be used to display the description for any selected function.
Registering a function to a model is simple and easy: Just select the desired function, click “Register” and you’re on your way.
- Once a function has been registered, simply exit from QAT Function Manager and open your Action Diagram.
- The newly registered function(s) will be available for use within your own statements just as you would with native Gen functions such as concat and substr.
- Use QAT Function Manager to generate the source stubs for your native language C, Java, .NET or COBOL where you can complete the code and compile into runtime libraries.
- At implementation, the associated function libraries are deployed to the environment for runtime execution. Deploy the function one time and use it like any other function from that point forward.
Custom Functions are new statements available for use in Action Diagrams. They are an effective alternative to External Action Blocks that implement functionality not provided by an original “out-of-the-box” CA Gen installation.
Custom Functions are registered in a CA Gen model by creating the necessary function signature within the model. Once registered, the functions are available to anyone that has access to that model.
Custom Functions
Available in all subsets without scoping.
Bound to a domain only (i.e. Text) so you can pass any view with the same domain.
Return values can be used as arguments for other functions and statements.
QAT Custom Function Manager automates the consumption and management of internal and third-party function libraries.
External Action Blocks (EABs)
- Must be explicitly scoped.
- Bound to a Gen view (i.e. import entity or workset view) so you must pass the same view.
- Return values cannot be used as arguments to other functions or statements.
- No automation for third-party library consumption.
Custom Functions are implemented with runtime libraries and behave just like any other native Gen function. Once registered, they must be deployed one time and are always available for use. Select the function from the list, provide its parameters, and go!
Yes. The experts at QAT Global have been successfully using Custom Functions with several customers for over two years. QAT Global offers two products (QAT Publisher and QAT Exchange) that were developed using Custom Functions which are running in customer applications today. There are also several custom functions that were specifically developed at the request of clients that are enhancing the functionality of their applications.
The main window has two distinct areas:
The available custom functions are displayed in the left pane. Libraries containing custom functions can be purchased from third parties and imported, or you may define your own functions and libraries using the tool.
The right pane displays the functions that are registered in the currently open CA Gen model. This pane can also be used to display the description for any selected function.
Registering a function to a model is simple and easy: Just select the desired function, click Register and you’re on your way.
Once a function has been registered, simply exit from QAT Function Manager and open your Action Diagram.
The newly registered function(s) will be available for use within your own statements just as you would with native Gen functions such as concat and substr.
Use QAT Function Manager to generate the source stubs for your native language C, Java, .NET or COBOL where you can complete the code and compile into runtime libraries.
At implementation, the associated function libraries are deployed to the environment for runtime execution. Deploy the function one time and use it like any other function from that point forward.