Browser Client One-Steps
Browser Client One-Steps look and behave similarly to One-Steps in the Desktop Client. In the Browser Client, Users can run One-Steps from:
- The Browser Client menu bar (run from the One-Step Manager or the list of Most Recently Used (MRU) One-Steps).
- Buttons, links, and Widgets on Dashboards.
- Business Object records (as buttons or links). Some One-Steps might also run as Automatic Actions that are executed when a Business Object is saved.
- The One-Step Manager (accessed from the Browser Client menu bar).
- An Actions menu on a Grid.
Good to know:
- The One-Steps accessed and run in the Browser Client are created in the CSM Desktop Client or in CSM Administrator. One-Steps cannot be created, edited, deleted, or run against groups of records in the Browser Client.
- The One-Step Manager behaves differently in the Browser Client than it does in the CSM Desktop Client. See Browser Client Managers for more information.
- The ability to run certain One-Steps depends on security rights. For example, to run a One-Step from a Team folder (scope), you must have rights to run Team One-Steps.
- Actions/One-Steps that are available as buttons and links on records, in Actions context menus, and/or that run automatically are configured by your Administrator.
- Printing One-Steps will only work if a specific, server-accessible printer is selected.
- Executing commands will only work for commands that are mapped the same way between the Desktop and the Browser Clients.
- There is currently no option in the CSM browser applications to run a One-Step for a group unless an explicit group is associated with the One-Step.
- Interactive One-Steps used as part of Save Actions generally only execute the last performed interaction.
- Write file, read file, run program, and transfer Attachments (to or from a file system) One-Steps generally do not work for the CSM Browser Client, unless a One-Step 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.