This section answers some of the questions that are frequently asked about working with multiple clients.
How do I migrate ALM Desktop Client from Internet Explorer to ALM Client Launcher?
Run ALM Client Launcher and no client-side migration is needed.
When you run ALM Client Launcher for the first time, it downloads the ALM client files to your local machine. From then on, you can enjoy the same ALM functionality as what you can access with ALM Desktop Client on Microsoft Internet Explorer.
If I connect to an ALM project in Web Client and modify workflow script here, how is the script presented in ALM Desktop Client for the same project, and vice versa?
If you want to apply the same workflow for all the users of a project, either let them use the same client or keep the two workflows consistent.
You can restrict a user group from using ALM Desktop Client or Web Client:
To disable a user group from using Web Client, you can do so in Project Customization — Module Access. For details, see Customize module access for user groups.
To disable a user group from using ALM Desktop Client, you can edit the CanLogin function in the VBScript workflow. Here’s an example:Copy code
Function CanLogin (DomainName, ProjectName,UserName)
CanLogin = True
if User.IsInGroup("Defect Reporter") then
msgbox "You are expected to visit this ALM project using Web Runner!"
CanLogin = False
Is it OK to access the same ALM project via different types of ALM clients?
Yes. Each user can use their preferred client to access the same project in ALM.
For details about ALM clients, see Available ALM clients.