The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This guide is for those who are integrating the WAE Design application and doing related developmental work, such as creating custom add-ons. Following is a summary of the chapters.
Note This guide references $CARIDEN_HOME
, which is the directory in which the WAE Design, WAE Live, and WAE Collector executables and binaries are installed. On Linux, the default $CARIDEN_HOME
is /opt/cariden/software/mate/curren
t, where /opt/cariden
is the default installation directory.
The information in a plan file is readily available for integration into other systems or workflows. All plan information is saved in tables, which you can retrieve, filter, and export to ordinary.txt format plan files. The easiest way to become familiar with the tables in a plan file is from the GUI, using the Plan Table Database Editor. This interface displays a list of all the tables in a plan and provides options for extracting plan information, from simple text searches to complex SQLite queries. The data you extract can be useful for critical tasks, such as these.
If you have a custom task that is part of your workflow, you can add that task as a menu item to WAE Design GUI, using the Add-on capability. Add-ons can simplify the task of data extraction for other systems, as well as for any WAE Design task that you perform frequently.