Accessing this Operation
This operation can be accessed by clicking
System
.
Describing this Operation
This operation is designed to:
- Launch an
executable file (.exe), a
shell (.sh) or a .bat file
- Call a compiled CAA coded
function thus enabling you to perform complex operations that cannot be
performed using a script language.
Methodology
You choose the working mode (Process or
library) of the operation. In library mode, the name
of the function, which corresponds to the name of the CAA function to call, is
required. In this mode, the Process Name input is the library name. The library
name does not need the extension (like .dll under Windows OS), the operation
being OS independent, it looks automatically for the library corresponding to
the current Operating System. Arguments: The behavior itself and the extended
object.

- Inputs and outputs managed
with
CATIVariableManagement interface.
- Extended object managed
through the same interface.
- Behavior states depend on
the return code of the called function.
The availability of the operation inputs depends on the selected
call type.
- Process: The
operation remains the same as the V6R15 one. The only difference is that it is
possible to specify in which mode the process runs.
- Library: The
function name is required and the process name requires the name of the library
to load. The operation is in
CannotOperate
mode until the 2 mandatory inputs i.e.
the library name and the function Name are valuated. So if the function is
located in a file called MyLib.dll, the library name is
MyLib. The library need not be in the runtime
view at build time. Since the operation calls a library, the module containing
the function has to be compiled.
Example
When working with the CAA function, make sure that this function has
the following signature:
extern "C"
HRESULT MyCAAFunction (CATIVariableManagement* iOperation, CATIVariableManagement*iExtendedObject)
(see script below.)
The inputs are those defined on the operation. As the operation is
an argument of the function, the
CATIVariableManagement
interface is used to retrieve
the operation inputs. Operation outputs are managed using the same interface.
Using this Operation Interface
Name
|
Name attributed to the operation.
|
Comment
|
Comment attributed to the operation.
|
Frame
|
Field
|
Field
|
Explanation
|
Process
|
Call Type
|
Process
|
Select this mode if you want to launch an
executable.
|
|
|
Library
|
Select this mode if you want to call a CAA
function. Only the library name must be specified.
|
|
|
Synchronous
|
If checked, the process is run
synchronously with the operation. The synchronous/asynchronous run only applies
to Process call types. The operation waits for the launched process to end
before continuing its operation. It means that the
app
waits for the process execution. If cleared, the process is launched and the
operation continues its operation, independently from the launched process.
Note that this option is available in Process mode only.
|
|
|
Function name
|
Type the name of the CAA function to call.
This input is mandatory when working with CAA functions.
|
|
|
Source File:
|
Type the name of the file used to generate
the input data for the process. If no
path is indicated, the
CATTemp variable indicates the directory to
use. If no file is indicated, a temporary file name is allocated by the
operation. Note that this field is not available when selecting the Library
mode. It is therefore dimmed.
|
|
|
Result File
|
Type the name of the file used to handle
the result of the process. Note that this field is not available when selecting
the Library mode. It is therefore dimmed.
|
Using this Operation
You want to perform advanced operations using C++.