Configuring event actions
To configure an event action to interface with Axios Assyst, you must write a configuration file. Modify the pxassyst.cfg sample script included in the samples directory and copy it to the \<instance>\script\ directory. If you cannot find the sample file, try re-running setup to modify your installation. Sample files are automatically installed with complete (typical) installations. You can select them in custom installations.
When you configure an event, you enter the program name or, as of Bravura Security Fabric version 7.0, the target ID you set up in Targeting a Assyst Help Desk server . In both cases, pxassyst looks for the default script with the matching name.
You can write an alternative .cfg file; for example when you have multiple Axios Assyst targets. When you configure an event, you specify the file using the -cfg parameter; for example:
pxassyst.exe -cfg myfile.cfgor
MYASSYST -cfg myfile.cfg
Requirements
If you do not use a ticket target to configure events, you must define the variables shown in the table below in every Assyst Help Desk script.
Key | Flag in acli.exe | Description of the value |
|---|---|---|
databasetype | -v | The database type (for example, SQLServer). |
server | -h | The database server (for example, <host name>\\<server name>). |
database | -d | The database name (for example, assyst). |
adminid | -u | The database user ID (for example, sa). |
adminpwd | -p | The password for the database user ID. |