Browser Client One-Step Actions

Browser Client One-Step Actions look and behave similarly to One-Step Actions in the Desktop Client.

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

• The Browser Client 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 Browser Client menu bar).
• An Actions menu on a Grid.

Good to know:

• 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.
• When One-Step Actions execute in the Browser Client, the interface appears as disabled until the One-Step Actions completes.
• 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.
• Printing One-Step Actions will only work if a specific, server-accessible printer is selected.
• 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 Search Group. 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 do not work for the CSM Browser Client, unless a One-Step Action is designed to write a file on the server, and then execute a program on the server using the contents of that file. However, this would require configuring IIS security rights specifically to handle this capability.