Skip to content
QiTASC.com / intaQt Setup and Configuration /
Glue Path
/ .. /
Glue Path










Glue Configuration

The Glue Configuration provides specifications about custom compound steps, including:

  • The directory in which they are stored

  • If intaQt's built-in Steps should be enabled or disabled

  • If legacy functionality is accessible.

Glue Path

The Glue Path points to where custom Stepdefs are stored. It must be specified in projects that use custom Stepdefs.

The Glue Path can be:

  • An absolute path.

  • A path relative to intaQt's working directory. The working directory is the folder where intaQt's executable is located (<User-defined Path>/intaqt/bin/).

  • Relative to the project root directory, which is the root folder of the relevant project. This path must always be a subfolder of the project root directory.

If the given Glue Path has subdirectories, these folders are also searched for in .steps and .uisteps Files. Models defined in .steps Files are available to .uisteps Files if located in the same imported directory as configured in the Glue Path. For more information about this, see Making Steps Language Models Available to the UI Steps Language.

If any of the paths included in the Glue Path configuration file do not resolve, a warning is printed to the log and the Glue Path configuration will not be loaded.

Syntax 

1
2
3
Glue = {
    path : [<String>, ...]
}

Parameter

  • path - The path to where Stepdefs are stored

Absolute Path Example 

1
2
3
Glue = {
    path : ["/Users/qitasc/myprojects/uisteps", "/Users/qitasc/secondproject/steps"]
}

Path Relative to intaQt's Working Directory Example 

1
2
3
Glue = {
    path : ["../dirOutsideProject/languageDir"]
}

Path Relative to the Project Root Directory Example 

1
2
3
Glue = {
    path : ["../../projects/specificProj/languageDir"]
}

Glue Path Resolving Process

Step 1 intaQt will try to resolve using the project root directory:

  • a - If the resolved path exists and is a subfolder of the project root, accept it.

  • b - If it exists and is not a subfolder of the project root, go to Step 2.

  • c - If it does not exist, go to Step 2.

Step 2 intaQt will next try to resolve using the working directory:

  • a - If the resolved path exists, accept it.

  • b - If it does not exist, a warning is logged and all entries are rejected from the .conf file.

Activate and Deactive Built-in Telephony Stepdefs

intaQt's built-in Compound Steps are activated by default. These can be replaced by a Custom Implementation written in the Steps Language when default Steps are deactivated in the Glue configuration.

Additional information is available in Steps and Compound Steps.

Syntax 

1
2
3
Glue = {
    builtinTelephonySteps : <String>
}

Parameter

  • builtinTelephonySteps - Whether intaQt's built-in Compound Steps are available or not
    • Must be one of "activated" or "deactivated"

Example 

1
2
3
4
Glue = {
    path : ["/home/user/QiTASC/intaqt/customsteps"]
    builtinTelephonySteps : "activated"
}

Use Deprecated/Legacy Syntax

intaQt's deprecated Steps Language may be accessed using the legacySyntaxEnabled configuration. However, this configuration not recommended and should only be used in rare cases.

The HTTP Built-ins should instead be used create SOAP messages from templates.

Syntax 

1
2
3
Glue = {
    legacySyntaxEnabled : <Boolean>
}

Parameter

  • legacySyntaxEnabled -
    • true - Activates the deprecated intaQt syntax
    • false (default) deactivates the deprecated intaQt syntax

Example 

1
2
3
4
Glue = {
    path : ["/Users/qitasc/myprojects/uisteps", "/Users/qitasc/secondproject/steps"]
    legacySyntaxEnabled: true
}