Let's say you want to implement a workflow which should let the user select an agent they need help from based on the agents' location and other details like company department. Supposing that each employee has a user property with the country that they are based at; and that all employees are also grouped by their role in the team, this can be implemented very easily. After the end user selects the agent they want help from, an issue can be assigned to such employee.

...

The button can be a primary screen where you can select the country. The screen script for the first button lets you select the available countries. 

BA_use "poweraction";

setActionTitle("Country");

string[] countries = {"USA", "Canada", "The Netherlands"};
BA_createSelectList("Country", countries, "", false, true, "Select the country where you are based");

BA_setExecuteButtonText("Next");

In the action script of the button we need to get the value from the screen and save it into an auxiliary value:

use "poweraction";

string country = BA_getSingleValue(argv, "Country");
BA_setBlitzAttribute("country", country);

After a user selects a country, they should be selecting a further filtering parameter – department. In this case, the screen script should look like this:

BA_use "poweraction";

setActionTitle("Department");

string[] departments = {"HR", "Sales", "IT"};
BA_createSelectList("Department", departments , "" ,false, true, "Select the department that best applies for your request");

BA_setExecuteButtonText("Next");

In the action script of the first step, we need to get the value from the screen and save it into an auxiliary value:

use "poweraction";

string department = BA_getSingleValue(argv, "Department");
BA_setBlitzAttribute("department", department);

The last screen provides a list of users that are in the selected country and work in the selected department.
Thus, the select script will consider the values set in the previous screens.

BA_use "poweraction";

setActionTitle("User");

string country = BA_getBlitzAttribute("country");
string office = BA_getBlitzAttribute("department");

string[] users;
string[] usersInDepartment = usersInGroups(department);

for (string user in usersInDepartment) {
    if (getUserProperty(user, "country") == country) {
        users = addElement(users, user);
    }
}

BA_createSelectList("User", users, "", false, true, "Select the person to help you");

In the action script, we only set the selected value as the assignee:

use "poweraction";

string user = BA_getSingleValue(argv, "User");
assignee = user;

...

For this example, after you click the main button, you'll get a succession of the following screens:

Image Removed

Image Removed

Image Removed

...

After the last screen executes, the assignee of the current issue will be set to the value selected in the User field - "josh" in this case.

See also

Example 2 - Logging work as another user