Perform Actions on Records

On this page

A step action works on a record that already exists. A create action makes a new record and starts it with the values of the action's template. Both kinds are defined in the workflow; see Workflow Overview.

Technicians run actions in the Web App and in the Mobile App.

Actions in the Web App

Run an action on a record

  1. Open the record, or find it in a list.
  2. Start the action:
    • On the full form, click the action on the Action Bar or on the toolbar.
    • On the preview form, click the action in the Action Bar drawer.
    • In a list, select the row, open the toolbar's Actions menu (or click the row's own action button), point to Actions, and click the action.
  3. If the action needs input, a form or a wizard opens. Fill it in and click Submit, as described below.

To start a create action in the Web App, see Create a record with New and Open and Edit a Record.

Run an action on several records

  1. In a list, select the rows of the records.
  2. Open the toolbar's Actions menu, point to Actions, and click the action. Only actions that may run on several records are offered.
  3. If the action needs input, fill in its form or wizard and click Submit.

When an action runs on more than one record, its form, and every step of its wizard, works as follows:

  • The fields do not show the values of the selected records. A field starts with the value that the action's form sets for it, if any; otherwise it starts empty, and a Yes/No check box starts cleared. An action run from a stock room's toolbar for adding assets or consumables also starts with that stock room filled in.
  • Beside each field is a marker. After you change a field, its marker shows an icon. Click the icon to reset the field to its starting value and leave the field out of the action.
  • A value that you type and then delete still counts as a change, and the action receives the field empty. To leave the field out, click its marker.
  • For a field that the business logic handles, the marker always shows its icon. Clicking it shows "This value is being handled by the business logic and cannot be suppressed." and resets nothing.

To change fields or tags on several records without running a workflow action, see Update Several Records at Once.

Fill in an action form or wizard

An action that needs input opens a form; an action with several steps opens a wizard. What the form asks is part of the action's setup in your workflow.

  • On a single-step form, click Submit to run the action.
  • In a wizard, move between steps with Back and Next. Back is unavailable on the first step and Next on the last. Submit appears on the last step.
  • On the form of an action that creates a record, Submit and open follows Submit. It runs the action and then opens the new record. This button is offered for every kind of record except approval requests, purchase order items, and vendor products.

Mandatory fields. A mandatory field carries the same asterisk beside its caption as on the record's full form. A field is mandatory because the action's form was set up that way, whatever the same field requires elsewhere.

  • Mandatory fields are first checked when you click Submit or Next. An empty field shows "This field is required." in place of the field's hint (an attachment area has its own message; see below), and the cursor moves to the first field that failed. The action does not run, and in a wizard Next does not move on. After a failed check, the fields are checked again as you change them.
  • In a wizard, Next checks only the fields of the current step. The workflow can also check the step's values before the wizard moves on.
  • A mandatory attachment area needs at least one attached file. Without one, it fails with "This field is required", which is not translated into the interface language.
  • A mandatory Yes/No check box shows no asterisk, and a cleared check box counts as filled in.
  • A value of 0 counts as filled in. A mandatory lookup counts as filled in only when it holds a selected record.

Length limits in a wizard. A text field's length limit is checked only after you change that field, so a value that a step fills in beyond the limit does not stop the wizard from moving on.

Canceling a wizard. If you have changed nothing and are still on the first step, the wizard closes at once. Otherwise you are asked to confirm.

If the record changes while the form is open

While an action form is open, the Web App checks whether the record has been changed: every 60 seconds while the form's browser tab is in view, and when you return to the tab. When it has, a banner appears above the fields. The form is not locked, but the action cannot run on the changed record:

  • When you click Submit, the action is refused with "You cannot perform this action because the object was modified by another user or process." The same message appears when the record has been deleted.
  • The form stays open with the values you entered, and clicking Submit again from the same form is refused again.
  • To run the action, close the form and start the action again. The form opens anew, with fresh starting values.

When the action runs on several selected records, one changed or deleted record refuses the whole run, and the action runs on none of them.

If an action's form cannot open

When the form of an action contains a field that no longer exists, the Web App shows the server's message that the action cannot be performed. The message names the action, its number, and the missing field, and asks you to contact your Alloy Navigator administrator.

If the action no longer exists

While you have an action's form open, an administrator may remove that action from the workflow, for example by deleting it or by importing it again as a new action. The Web App then refuses to run the action with "You cannot complete the action because Alloy Navigator business logic has been modified. Please save the data you have entered, close the window, and launch the action again. If you have problems accessing the action, contact your Alloy Navigator administrator."

If a step action has already been removed when you open its form, the message reads instead: "While you were working with this object, the administrator made changes to the business logic. Please try running this action again."

In either case, copy any text you have entered, close the form, and start the action again. If the action is no longer offered, contact your Alloy Navigator administrator.

Where actions appear

On the full form. The Action Bar is the panel on the right side of the record, with its actions grouped in sections. While the panel is unpinned, a click outside it hides it and leaves a vertical Actions tab; click the tab to bring the panel back. Pin the panel to keep it open. On the full form the panel also stays open after you click an action.

On the preview form. The Action Bar opens in a drawer, which you close with its Actions button. The drawer cannot be pinned, and it closes when you click an action.

On the full form's toolbar. Actions that the workflow places on the toolbar appear there without groups. A toolbar action is either a button that shows its caption, and its icon if it has one, with the action's description as its tooltip, or an icon-only button whose tooltip is the caption. Actions that do not fit the toolbar's width move into the More menu (the vertical dots), where each shows its icon and caption, with its description as its tooltip. An action can appear both on the Action Bar and on the toolbar.

In a list. In a list of records that have a workflow, the toolbar's Actions menu has an Actions submenu with the workflow actions of the selected rows. Actions of a named group are in a further submenu of their own. In a list that allows actions, each row also has its own action button, titled Open, except in a dialog for picking a record and in a list shown as a tree. The button opens a menu for that one row with the same Actions submenu, grouped the same way, and with the commands that open the record at the top when the list allows opening records; while the row has no actions, the submenu reads No Actions. A list offers every action of the record whatever its place on the form, including actions that appear only on the Action Bar of the form and actions that the workflow places neither on the Action Bar nor on the toolbar, which the full form does not show. The toolbar's Actions menu is unavailable until you select at least one row, except in a list inside a record's form that has global actions. In a list inside a record's form that has unsaved changes, choosing an action first asks you to save or discard the changes.

Actions in the Mobile App

The Alloy Navigator app never lists a step action that is not valid for the record's status or does not meet its criteria, or a create action that does not meet its criteria, whatever the hidden-or-dimmed setting is, so the app shows no dimmed actions. To run actions in the app, see Work with Records in the Mobile App.

Why an action is missing or dimmed

A step action is offered on a record only when all of the following hold:

  • The record is in one of the action's statuses. An action set up without a status list is offered in every status that is not closed.
  • The record is of one of the action's types. An action set up without a type list is offered for every type.
  • You hold a security role that may run the action, or the action is open to every role. When the role that grants the action is restricted to certain organizations, the record's organization must be one of them. For a support account, this role condition does not apply: an action restricted to certain roles is offered whatever the role grants say; see Accounts.
  • The record meets the action's additional criteria, if it has any.

Some actions follow further rules:

  • A reopen action is offered only on records in an inactive status.
  • On a computer, a reopen action is refused when reopening the computer would exceed the number of nodes your license covers.
  • An action that may run only on a single record is not offered when you select several records in a list.
  • Some actions are never listed with the others because they are run from another place: a project task or a stock room's toolbar.
  • A create action is offered according to your security roles, and only when its additional criteria, if it has any, are met. The status and type rules do not apply, and an organization restriction on your role does not narrow the create actions you see. A create action is never shown dimmed, whatever the hidden-or-dimmed setting: one whose additional criteria are not met is not offered at all, in the Web App or in the Mobile App.

Hidden or dimmed

When a step action is not valid for the record's status or does not meet its criteria, the Web App either hides it or shows it dimmed. One system-wide setting decides which, and unless an administrator changes it, such actions are hidden. A dimmed action stays in its place on the Action Bar, the toolbar, or the More menu, and cannot be clicked.

Whatever the setting, the Web App always hides an action that none of your security roles may run.

Your administrator chooses how unavailable actions appear; see Unavailable workflow actions. The Web App reads the setting when a session connects to the server, so sessions that are already open may not show the change immediately.

What your organization's workflow decides

The Action Bar holds no logic of its own: which actions exist, how they are grouped, and when they are available are set in the workflow. For each action, the workflow sets:

  • its name and its place in the order;
  • for a step action, the group it is listed under;
  • for a step action, where it appears on a record: on the Action Bar, on the record's toolbar, on both, or on neither, and whether its toolbar button shows the caption;
  • for a step action, the statuses and types of record in which it is offered;
  • any additional criteria;
  • the security roles that may run it;
  • for a step action, whether it may run on several selected records at once;
  • the form it opens, if any, and which fields of that form are mandatory;
  • for a create action, the template whose values the new record starts with.

Administrators set these up; see Actions.