One-Step Actions in the Browser Client

The One-Step Actions accessed and run in the Browser Client are created in the CSM Desktop Client or in CSM Administrator. One-Step Actions cannot be created, edited, or deleted in the Browser Client.

In the Browser Client, users can run One-Step Actions from:

  • The menu bar (run from the One-Step Action Manager or the list of Most Recently Used (MRU) One-Step Actions).
  • Buttons, links, and widgets on dashboards.
  • Business Object records (as buttons or links). Some One-Step Actions might also run as Automatic Actions that are executed when a Business Object is saved.
  • The One-Step Action Manager (accessed from the menu bar).
  • An Actions menu on a grid.

Good to know:

  • When One-Step Actions execute in the Browser Client, the interface appears as disabled until the One-Step Actions complete.
  • Print Actions are supported in the Browser Client and Portal when Trusted Agents are used to run the Actions. This includes Run a Report Actions that are configured to print a report. SaaS customers can configure a Trusted Agent to use printers on their remote network; on-premises customers can configure a Trusted Agent to use printers on their local network or on a remote network. If you do not configure Trusted Agents, users receive an error indicating that Print Actions are not supported when the One-Step Actions is run on the Browser Client or Portal.
  • When One-Step Actions that contain multiple Actions are executed in a CSM web application, the end result of the One-Step Action is shown to users when execution is complete. Users are prompted for input as needed, but if the Save Business Object After Action check box is cleared for a particular Action, changes made by the Action are not saved.
  • There is currently no option in the Browser Client to run a One-Step Action for a group. You can, however, configure a One-Step Action to run against a specific saved search. In this case, the One-Step Action runs against the defined group of records, regardless of the client used to run the One-Step Action. For more information, see Define the Conditions for a One-Step Action.
  • Write file, read file, run program, and transfer attachments (to or from a file system) One-Step Actions generally works for the CSM Browser Client, but the One-Step Action must be designed to write an accessible file on the server, and then execute a program on the server using the contents of that file. This requires configuring IIS security rights specifically to handle this capability.
  • When a One-Step Action executes in the CSM Browser Client, a progress bar is not displayed.