Innoslate Advanced Search: Quick Guide
A quick guide to searching your Innoslate project.
In the fast-paced world of model-based systems engineering (MBSE), quickly locating the right requirements, actions, risks, or diagrams across complex project databases can mean the difference between meeting deadlines and costly rework.
Innoslate’s Advanced Search feature empowers engineers, analysts, and project managers with a powerful, flexible query language to pinpoint entities with surgical precision. From simple keyword lookups to sophisticated attribute filtering, Boolean logic, and diagram-aware searches, this syntax transforms the Database View and search fields into a dynamic discovery tool—unlocking insights hidden in even the largest Innoslate projects.
Below is a quick guide reference for searching your project in Innoslate.
1. Basic Searches
|
Type |
Syntax |
Example |
Finds |
|
Keyword |
word |
Power |
Entities with name, number or descriptions with the word `power’ |
|
Exact Phrase |
phrase |
“power subsystem” |
Entities with name, number or descriptions with the word `power subsystem’ |
|
Number |
number:X |
number:2.3 |
Exact number |
|
Class |
class:“Name” |
class:”Requirement” |
All Requirement Entities |
|
Label |
label:“Name” |
Label:”Activty” |
Entities labeled ‘Acitivty’ |
2. Boolean Logic
AND → both sides must match
Example: label:Risk AND class:Action
OR → either side matches
Example: label:System OR label:Subsystem
NOT → excludes the term
Example: NOT is:root
3. Attribute Search (by Type)
Correct Format: Class:"Attribute Name, operator, value"
- Class → Case-sensitive class name (e.g., Action, Requirement)
- : → Colon separator
- " → Opening double quote
- Attribute Name → Exact, case-sensitive attribute (with spaces allowed)
operator → One of: =, >, <, >=, <= - value → Search value (case-insensitive)
- " → Closing double quote
|
Type |
Operators |
Example |
|
Text / HTML / URI |
= |
Requirement:"Status=Draft” |
|
Number/Percent |
=, >, <, >=, <= |
Action:"Percent Complete=0" |
|
DateTime |
=, >, <, >=, <= |
Action:"Start>=2/1/2050, 12:00:00 AM" |
|
Duration |
=, >, <, >=, <= |
Action:"Duration=2 weeks" |
|
Enumeration |
= |
Action:"Classification=Secret” |
|
Quality (Yes/No) |
= |
Requirement:"Complete=No" |
|
File Attachment |
= |
Artifact:"File=True" |
|
GeoPoint |
=, >, < |
Physical:"Coordinates=95.71,37.09" |
4. Wildcards & Prefixes
|
Symbol |
Meaning |
Example |
|
% |
Any Characters |
`Name: App%` → Apple, AppX |
|
* |
Suffix after prefix |
number:5.*` → 5.1, 5.2.1 |
|
XYZ.* |
Numbers starting with XYZ |
XYZ.1, XYZ.2.3 |
5. Special Filters
|
Qualifier |
Example |
Meaning |
|
is:root |
is:root |
Top-level (no parent) |
|
is:leaf |
is:leaf |
No Children |
|
is:orphan |
is:orphan |
No relationships |
|
is:diagram |
is:diagram |
Has generated diagram |
|
is:crossproject |
is:crossproject |
Cross Project Links |
|
diagram:Type |
Diagram:LML_ACTION |
Has Action Diagram |
|
relationship:”name”` |
relationship:"decomposed by" |
In decomposition |
6. Diagram Types (Short Names)
|
Short Code |
Full Name |
|
LML_ACTION |
Action Diagram |
|
SYSML_BDD |
Block Definition Diagram |
|
SYSML_IBD |
Internal Block Diagram |
|
LML_RISK |
Risk Diagram |
|
LML_TIMELINE |
Timeline Diagram |
|
UML_CLASS |
Class Diagram |
> Use: `diagram:"Action Diagram"` or `diagram:LML_ACTION’
7. Sorting Results
Name
- order:name A → Z
- order:name- Z → A
Number
- order:number 0 → 9
- order:number- 9 → 0
Modified
- order:modified newest first
- order:modified- oldest first
Created
- order:created newest first
- order:created- oldest first
Relationships
- order:related newest first
- order:related- oldest first
Diagram Modified
- order:diagrammodified newest first
- order:diagrammodified- oldest first
Example
order:number- class:"Action"