Skip to main content

Component Template UI Updates (Mobile) - User Guide

09.18 batch — M2

Written by Trevor Shaffer

Overview

Applying templates to a component and creating new components share a single entry point on mobile, matching the web experience. Technicians use this to quickly apply an asset or component template, or build a new component from scratch, without switching between separate buttons.

Accessing Component Templates

  1. Tap the Assets tab in the bottom navigation bar.

  2. Tap an asset, then tap Components.

How to Add a Template

Steps:

  1. From Components, tap Add Template.

  2. Browse Asset Templates at the top, followed by Component Templates below.

  3. Use the search bar to filter by name, or toggle shorthand search to match by a template's shorthand code.

  4. Tap each template you want to apply — selected cards show a number for the order they'll be applied in.

  5. Tap Apply to add the selected templates.

NOTE: The order you tap templates in is the order they're applied.

How to Create a Component

Steps:

  1. From Components, tap Create Component.

  2. Fill in the component details.

  3. Tap Save to add the new component to the asset.

Use Cases

  • A technician setting up a new pump asset in the field applies an asset template and a couple of component templates in one pass, in the order they should appear.

  • A tech working from a large template library uses the shorthand search toggle to find a specific template quickly by its short code.

Best Practices

  1. Tap templates in your intended order: Selection order determines application order.

  2. Use shorthand search on long lists: It's faster than scrolling through full template names.

Troubleshooting

Issue: Applied templates don't appear in the order expected.
Solution:

  1. Check the order numbers shown on each card at the time they were applied — that's the saved order.

Summary

The combined Add Template flow puts asset templates, component templates, and manual component creation in one place on mobile, matching the web experience and keeping ordering clear.

Did this answer your question?