Inventory Scanner Configuration
On this page
The Alloy Inventory Scanner app reads its configuration from the mobile
application record InventoryScanner. The configuration is a list of workflow
actions the app may run. The app reads the list at every connection, and each
entry gives:
ActionID- the workflow action to run.DisplayName- the caption of the action's button in the app.ResponseText- the message the app shows when the action succeeds.
When the app does not get a successful answer to its configuration request, it stays connected but offers no actions.
You edit the record in the Settings App or in the Admin Center; see Admin Center and Settings App. For how the URL mask selects a record, see Mobile App Configuration. For how technicians use the app, see Alloy Inventory Scanner.
The entry in a new database
In a new 2026.1 database created with the Default Workflow (see
Default Workflow Configuration), the record
holds one entry. It names the Inventory action, its DisplayName is set to
Inventory, and its ResponseText is set to "Inventory completed", so the app
shows an INVENTORY button. In that configuration, the Inventory action
carries a condition on the application name described below. An upgraded
database need not have this entry, and an
administrator may have changed it.
How the app uses the actions
- Each action is a button on an asset's panel, captioned with its
DisplayNamein upper case. - The button opens a form titled with the caption, with a required Location and a Comment.
- When the technician submits the form, the app first checks the asset. A
retired asset is refused on the device with the message
Asset "<asset ID>" is retired, and nothing is sent to the server.
Otherwise the app runs the action on the asset with the chosen location and
the comment. On success it shows the action's
ResponseText; on failure, an Error dialog shows the server's error text. - The app gives its application name as
InventoryScannerwhen it runs an action.
Fields an action must keep
The app never requests an action's form from the server. Of the form's fields,
it supplies only the location and the comment, whatever else the form holds. An
action you list in the record therefore has to keep the two fields that carry
them: the physical Location_ID field and a virtual
Memo field named Comment. Any other field on the action's form gets no value
from the app. To change the action, work on a copy of it; see
Work on a copy of the action.
Minimum app version
An entry may carry a MinVersion attribute. The app sends no version with its
request, so an entry with MinVersion makes the server refuse the whole
configuration with "Version is not supported." followed by the required version.
The app then stays connected with no actions.
Before you begin
In the Settings App, the Mobile Applications item is tied to the security action Mobile Applications ("Allows managing Mobile Applications"), a child of Services Configuration Management. See Permissions Reference.
Edit the record in the Settings App
TIP: We recommend that you save the text of Configuration to a file before you change it, so that you can return to it.
- In the navigation bar, go to Services > Mobile Applications.
- Double-click the
InventoryScannerrow, or select it and click Edit or press Enter. - In the Mobile Application [InventoryScanner] dialog, edit Configuration, URL Mask, or both. The dialog shows the application ID as a read-only line, "Mobile Application ID:" followed by the ID.
- Click OK.
OK parses the configuration as XML before anything is saved. If the text does
not parse, an error is shown, the dialog stays open, and nothing is written. If an
ActionID names an action that does not exist, saving fails with "Action not
found". The record is written only after OK succeeds. The app uses the
saved configuration from the next time it connects.
The Settings App shows each ActionID as the action's number and translates it
back when it saves, so the text you see is not identical to the stored text. If
a stored ActionID names an action that does not exist in the database, the
configuration does not open and "Action not found" is shown. A configuration
imported from another database whose actions do not exist here cannot be opened.
To return to a saved configuration, open the record again, replace the whole
text of Configuration with the saved text, and click OK. Save and paste
the text in the same application, because the Settings App shows each
ActionID differently from the stored text. Importing the record with
Import Settings... does not restore it: for a record that already exists,
the import keeps the current configuration and adds only the elements it
lacks. See Export and Import Configuration.
The Mobile Applications page lists the records with the columns Mobile Application ID and URL Mask. A Configuration column is hidden by default. The toolbar carries Edit, Copy Item, and Delete.
Edit the record in the Admin Center
In the Admin Center, you can list the mobile application records, edit the configuration and the URL mask of a mobile application record, copy a record, and delete one. The configuration is required. The Admin Center does not create mobile application records. For the steps, see Mobile App Configuration.
Work on a copy of the action
We recommend that you change a copy of the action that the record names, not the action itself. In a new 2026.1 database created with the Default Workflow (see Default Workflow Configuration), that action is the Inventory Step Action of assets.
- In the Settings App navigation bar, go to Workflow and Business Logic > Asset Management > Assets > Workflow > Actions > Step Actions.
- Select Inventory and click Copy Item. The copy, named Inventory - Copy, is saved at once with a new ID and opens in its own window, whose title shows the copy's ID.
- Make your changes to the copy, keeping the Location and Comment fields on its form (see Fields an action must keep), and click OK.
- In the
InventoryScannerrecord, set the entry'sActionIDto the copy's ID (see Edit the record in the Settings App). An ID that names no action makes saving fail with "Action not found".
The copy carries the same condition on the application name as the original. A custom form or function of the original is duplicated for the copy; a reusable one is shared by both, so a change to it also changes the original. See Actions.