Overview
This feature warns you when you try to save a component with no tasks as a component template, and blocks the save until the component has at least one task. It applies whenever you save a component as a template from mobile, keeping every template you create immediately useful instead of producing an empty one that has to be fixed later. It works the same way on both iOS and Android.
Accessing the Feature
From a component's card or list row, open its menu.
Tap Save Component as Template.
How to Save a Component as a Template
Steps:
Tap Save Component as Template from the component's menu.
Redlist checks the component's task count before anything else.
If the component has no tasks, a warning appears immediately and the save stops there — you have to add a task before trying again.
If the component has one or more tasks, a confirmation appears showing the component type and task count. Tap Save to continue, or Cancel to back out.
NOTE: This check is based on the task count already synced to your device, so make sure your app is up to date before saving a template if you've just added a task elsewhere.
How to Handle an Existing Template for That Component Type
If a template already exists for the component's type, you'll be asked how to proceed after confirming the save.
Steps:
Choose Overwrite to replace the existing template's tasks with this component's tasks (this is selected by default).
Or choose Select Type to save this component as a template under a different component type instead — you'll need to pick a type before you can save.
Tap Save to finish.
NOTE: In the Select Type list, any component type that already has a template is shown disabled with a note that a template already exists for it.
Understanding the No-Tasks Check
The check only runs at the moment you try to save a component as a template — it does not affect templates that already exist.
It counts tasks already on the component; tasks added to the template itself afterward are unaffected.
This does not change how component templates work once created — it only prevents saving a template that has no tasks in the first place.
Use Cases
Preventing empty templates. A technician tries to turn a freshly created, taskless component into a template — the warning stops them and prompts adding a task first, instead of a blank template being reused across future assets.
Existing components with tasks. A technician saves a fully built-out component (with several tasks already defined) as a template — the save proceeds with no interruption, since the check only blocks components with zero tasks.
Best Practices
Add Tasks Before Templating: Build out a component's tasks first, then save it as a template, so the template is immediately useful.
Sync Before Retrying: If you just added a task and still see the warning, sync the app so the new task count downloads to your device.
Assign a Component Type First: A component needs a component type assigned before it can be saved as a template at all.
Troubleshooting
Issue: You added a task to the component, but the warning still appears.
Solution:
Sync the app so the new task count is downloaded to your device.
Try saving the template again.
Issue: You can't save the component as a template at all, even though it has tasks.
Solution: Make sure the component has a component type assigned — a component without one can't be saved as a template.
Summary
Saving a component with no tasks as a template is blocked, with a warning guiding you to add a task first. This check runs before the save confirmation, works the same way on iOS and Android, and doesn't affect existing templates.