Skip to main content

Service requests

In briefA service request — a self service button on screen — is a form you publish so that someone can start automation without touching the workflow. Submitting it fires one or more events, one after another, in the order you set. Each button has versions and is deployed per environment, like a workflow, and the portal groups buttons by category.

WhereYou build them under Design › Self Service Config, on the Self Service Configuration page; Organize Self-Service Buttons on its toolbar arranges the portal page. People submit them under Operations › Self Service — the portal.

WhenUse one when someone outside the automation team needs to start a known task on demand:

  • a business user requesting a file restore, a report, or a re-run;
  • an operator starting a routine task with a few choices filled in, such as a region or a date;
  • a task of several steps whose events must run in a set order.

Use something else when nobody needs to ask: a schedule belongs in a workflow's frequency, and a reaction to a failure in a notification group.

How

  1. On Self Service Configuration, select New Self Service Button, then add its events in the order they must run; each ${…} placeholder you write adds an input.
  2. Save, which creates a version, then deploy it to each environment.
  3. Check that requesters hold the permissions the portal checks, then submit it once yourself.

The full steps are in Create a service request.

Notes
  • Events are checked as the requester, not as the person who built the button.
  • A button missing from the portal is usually not deployed to that environment, or its deployment is inactive or outside its effective window. A Hidden rule that is true also removes it.
  • Hidden and Disabled rules are checked again on submission. A rule that can't be evaluated usually leaves the button usable, with a warning.
  • Arranging the portal page or filing a button in a category needs no redeploy.
  • The configuration grid's Active column and a button's Deploy modal show only the environments your role may view deployments in; No access means it may view none.
  • A Pinned deployment must name a version the button has; one that names a missing version is not shown in Self Service, and its card says so.
  • An input's default must be one requesters can submit, where the button's events place it. The input editor and the save refuse one that is not, and Copy leaves it out.
Watch out
  • One failing event doesn't stop the others. After a partial failure, don't submit again: the events that worked would run twice.
  • If no answer comes back in time, check the event log before submitting again.
  • An input no event references is removed from the button, so delete a placeholder only when you mean to drop its input.
  • Collect a requester's secret with a Password input, not a Text input; an encrypted property can be used only as the value of $PROPERTY:SET / $PROPERTY:ADD.