Searching for Entities

Last modified on August 12th, 2020.


Innoslate provides the ability to perform searches for specific entities within your project’s database via the ‘Search’ feature.

You will find the ‘Search’ field used to enter your search criteria at the top center of the toolbar in ‘Database View.’

You can search based on a number, a word or group of words, a label, a class, or both class and label in any combination you wish. Simply type your search criteria in the search box and hit ‘Enter’ on your keyboard or click the magnifying glass button to the right of your entered text to display your search results.

Basic Searches

 

Basic Searches with Qualifiers

 

Advanced Searches

 

 

 

 

 

Diagrams Type

Supported Diagram Name

A0_DIAGRAM

icom, icom diagram

IDEF0_DIAGRAM

idef0, idef0 diagram

LAYER

layer, layer diagram

LML_ACTION

action, action diagram

LML_ASSET

asset, asset diagram

LML_HIERARCHY

hierarchy, hierarchy chart, hierarchy diagram

LML_I2

i2, i2 diagram, i-squared, i-squared diagram

LML_ICD

icd, interface control, interface control diagram

LML_N2

n2, n2 diagram, n-squared, n-squared diagram

LML_PHYSICAL_INPUT_OUTPUT_DIAGRAM  

physical, physical diagram, physical i/o, physical i/o diagram

LML_RISK

risk, risk diagram

LML_SPIDER_DIAGRAM

spider, spider diagram

LML_TIMELINE

timeline, timeline diagram

RADAR_DIAGRAM

radar, radar diagram

SYSML_ACTIVITY

activity, activity diagram

SYSML_BDD

bdd, bdd diagram, block definition, block definition diagram

SYSML_IBD

ibd, ibd diagram, internal block, internal block diagram

SYSML_PACKAGE

package, package diagram

SYSML_PARAMETRIC

parametric, parametric diagram

SYSML_REQUIREMENTS

requirement, requirements, requirement diagram, requirements diagram

SYSML_SEQUENCE

sequence, sequence diagram

SYSML_STATE_MACHINE

state machine, state machine diagram

SYSML_USE_CASE

use case, use case diagram

TREE

tree, tree diagram

UML_CLASS

class, class diagram

 

List of Available Qualifiers

The table below outlines of all the search qualifiers supported by the Innoslate search system.

 

Search Qualifier

Example Search

Returns

id:value

Id:1

Entities where the id is equal to specified value.

attributeid:"attribute id=value"

Attributeid:"1=1"

Entities where the specified attribute value equals the searched value.

class:"attribute name=value"

Action:"Percent Complete=45"

Entities where the specified attribute value equals the searched value. See Attribute Search above for more details.

class:name

class:Action

Entities of the specified schema-based class.

diagram:diagram type

diagram:LML_ACTION

Entities which have that specific diagram enum. See Diagram Search above for more details.

diagram:diagram name

diagram:"Action Diagram"

Entities which have that specific diagram name. See Diagram Search above for more details.

relationshipid:relation Id

relationshipid:1

Entities that contain the relationship type.

relationship:relation name

relationship:"decomposed by"

Entities that contain the relationship type.

order:type

order:number

Orders the results by either name, number, or modified in ascending order. Including a minus after the type (ex. order:number-) will sort descending.

is:crossproject

is:crossproject

Entities with cross project relationships.

is:diagram

is:diagram

Entities that have a generated diagram within Innoslate.

is:leaf

is:leaf

Entities with no children (no target relationships on decomposed by).

is:orphan

is:orphan

Entities with no target relationships to any other entity.

is:root

is:root

Entities with no parents (no target relationships on decomposes).

label:name

label:Activity

Entities with the specified label applied.

is:top

is:top

Entities which are the top of an overall hierarchy (documents, root diagrams, etc.).

number:number

number:5.1

Entities with the specified number.

globalid:global Id

globalid:I_1E3MYNY9MGHV_9WCAZFAFXJW6C  

Entities which have the supplied global id.

Database Variances

Innoslate supports multiple databases. Each database behaves slightly different when it comes to search. The table below is to help illustrate these differences. Four entities were created for this search example. The first three entities had the name, number, or description filled in with “Innoslate is a MBSE tool”. The fourth had the number field filled in with I.1.12. 




 

Microsoft SQL

PostgreSQL 

H2

Name:

     

Name:is

*

*

*

Name:"is%"

 

X

X

Name:"%is%"

X

X

X

Name:Innoslate

X

X

 

Name:Inn*

X

X

X

Name:Inn%

X

X

X

Name:_n*

 

X

X

Name:_%

X

X

X

Name:"MB*"

X

   

Name:"MB%"

 

X

X

Name:"%MB%"

X

X

X

Name:"MBSE"

X

X

 

Name:"MBSE tool"

X

X

 

Name:Innoslate is a MBSE tool

X

X

 

Name:"Innoslate is a MBSE tool"

X

X

 

Number:

     

Number:is

*

*

*

Number:"is%"

 

X

X

Number:"%is%"

X

X

X

Number:_.*

X

X

X

Number:_.%

 

X

X

Number:Innoslate

X

X

 

Number:Inn*

X

X

X

Number:Inn%

X

X

X

Number:_n*

 

X

X

Number:_%

X

X

X

Number:"MB*"

X

   

Number:"MB%"

 

X

X

Number:"%MB%"

X

X

X

Number:"MBSE"

X

X

 

Number:"MBSE tool"

X

X

 

Number:Innoslate is a MBSE tool

X

X

 

Number:"Innoslate is a MBSE tool"

X

X

 

Description:

     

Description:is

*

*

*

Description:"is%"

 

X

X

Description:"%is%"

X

X

X

Description:Innoslate

X

X

 

Description:Inn*

X

X

X

Description:Inn%

 

X

X

Description:%Inn%

X

X

X

Description:_n*

 

X

X

Description:_%

X

X

X

Description:"MB*"

X

   

Description:"MB%"

 

X

X

Description:"%MB%"

X

X

 

Description:"MBSE"

X

X

 

Description:"MBSE tool"

X

X

 

Description:Innoslate is a MBSE tool

X

X

 

Description:"Innoslate is a MBSE tool"

X

X

 

ALL:

     

is

*

*

*

"is%"

 

X

X

"%is%"

X

X

X

Innoslate

X

X

 

Inn*

X

X

X

Inn%

**

X

X

%Inn%

X

X

X

_n*

 

X

X

_%

X

X

X

"MB*"

X

   

"MB%"

 

X

X

"%MB%"

X

X

X

MBSE

X

X

 

"MBSE"

X

X

 

"MBSE tool"

X

X

 

Innoslate is a MBSE tool

X

X

 

"Innoslate is a MBSE tool"

X

X

 

_.*

X

X

X

_.%

X

X

X

Innoslate is a MB*

X

X

***

Innoslate is a MB%

 

X

***



*: Stop word, so all results are true

**: Only Name and Number

***: Only Number and Description

Searching for Entities

Last modified on August 12th, 2020. 


Innoslate provides the ability to perform searches for specific entities within your project’s database via the ‘Search’ feature.

You will find the ‘Search’ field used to enter your search criteria at the top center of the toolbar in ‘Database View.’

You can search based on a number, a word or group of words, a label, a class, or both class and label in any combination you wish. Simply type your search criteria in the search box and hit ‘Enter’ on your keyboard or click the magnifying glass button to the right of your entered text to display your search results.

Basic Searches

  • By Number
    Searching for a number checks the number, name and description of every entity in your database looking for your search criteria.

    For example:
    2.3.2.0 – Matches entities that contain the number 2.3.2.0.

 

  • By Word(s)
    Searching for a word or group of words checks the number, name and description of every entity in your database looking for your search criteria.

    For example:
    Stakeholder – Matches entities that contain the word stakeholder.
    OR
    preliminary design Matches entities that contain the word preliminary and the word design.

Basic Searches with Qualifiers

  • Label
    You can narrow your search results by labels, using the label qualifier.  Since entities can have multiple labels you can also use multiple of these qualifiers.
     
    For example:
    planning label:Activity Matches entities with the word planning that are also labeled as an Activity.
    OR
    label:Activity label:Process Matches entities with both the Activity and Process labels.

 

  • Class
    You can narrow your search results by class, using the class qualifier. Combine this with a label qualifier to further refine results.

    For example:
    mitigate risk class:Action – Matches entities with the word mitigate and the word risk that are of the schema-based class Action.
    OR
    power class:Requirement label:“Functional Requirement” – Matches entities with the word power that are of the schema-based class Requirement and also labeled as a Functional Requirement.

Advanced Searches

  • AND and OR
    When a more advanced search is required, it is possible to use the AND and OR search modifiers to more precisely refine results.  The AND modifier requires both values on either side of the AND to be found. The OR modifier requires only one (1) of the values on either side of the OR to be found.  These modifiers can also be used in combination with a single word, class qualifier, and/or label qualifier.

    For example:
    label:Facility AND label:Infrastructure Matches entities that are labeled with both the Facility and Infrastructure labels.
    OR
    distribution label:System OR label:Subsystem – Matches entities with the word distribution that are also labeled with either as a System or a Subsystem.

 

  • NOT
    The NOT modifier will find the inverse of the following search term.

    For example:
    NOT is:root – Matches entities that are not roots in hierarchies.
    OR
    NOT refined class:Action Matches entities that do not have the word ‘refined’ and are of the schema-based class Action.

 

  • Wildcards
    Wildcard searches allow you to search for a combination of characters. Innoslate supports the percent(%) character to search for any number of non-whitespace characters before or after a set of characters.

    For example:
    Name: App% – Matches entities with any name with string ‘App’
    OR
    Number: 2% – Matches entities with any number that has a ‘2’.

 

  • Prefix
    Prefix searches allow you to search for a combination of characters after a prefix. Innoslate supports the asterisk(*) character to search for any number of non-whitespace characters after the previous characters. With this you can search for numbers that start with specific characters.

    For example:
    number:5.* – Matches entities with numbers that start with ‘5.’.
    OR
    number:SRS.* class:Statement Matches entities with numbers that start with ‘SRS.’ and are of the schema-based class Statement.

 

  • Stop Words
    Stop words are words or characters that are automatically filtered out of the search string. These words are usually linking verbs, conjunctions, or pronouns.

    The List of stop words are the following:

    i, me, my, myself, we, our, ours, ourselves, you, your, yours, yourself, yourselves, he, him, his, himself, she, her, hers, herself, it, its, itself, they, them, their, theirs, themselves, what, which, who, whom, this, that, these, those, am, is, are, was, were, be, been, being, have, has, had, having, do, does, did, doing, a, an, the, and, but, if, or, because, as, until, while, of, at, by, for, with, about, against, between, into, through, during, before, after, above, below, to, from, up, down, in, out, on, off, over, under, again, further, then, once, here, there, when, where, why, how, all, any, both, each, few, more, most, other, some, such, no, nor, not, only, own, same, so, than, too, very, s, t, can, will, just, don, should, now

    To search for a stop word used the percent sign after the stop word.

    For example:
    been% – Matches entities with that the stop word ‘been’.
    OR
    s% – Matches entities that contain the stop character ‘s’.

 

  • Attribute Search
    Attribute searches allow you to search for attributes contained in entities. Innoslate supports the >, <, >=, <=, or = characters to search for attributes or attributes in ranges. The list below outlines the searches that can be performed on each attribute type. Attributes type can be found under the Type column in class or relation in the schema. Classes and Attributes names are case sensitive, where the values are not.

    • TEXT: Matches entities in a class with the attribute that contains the string of text.
      Operators Supported: =

      For example:
      Characteristic:“Units=meter” – Matches entities in Characteristic class that have the attributes Units that contain the value meter. 
    • NUMBER: Matches entities in a class with the attribute that evaluates as true.
      Operators Supported: >, <, >=, <=, =

      For example:
      Conduit:“Capacity>=50” – Matches entities in Conduit class that have the attributes Capacity that is greater than or equal to 50. 
    • BIG_TEXT:Matches entities in a class with the attribute that contains the string of text.
      Operators Supported: =

      For example:
      Decision:“Assumptions=acceptable” – Matches entities in Decision class that have the attributes Assumptions that contain the value acceptable. 
    • HTML: Matches entities in a class with the attribute that contains the string of text.
      Operators Supported: =

      For example:
      Website:“Title=Welcome” – Matches entities in Website class that have the attributes Title that contain the value Welcome. 
    • ENUMERATION: Matches entities in a class with the attribute that contains the enumeration text.
      Operators Supported: =

      For example:
      Requirement:“Status=Draft” – Matches entities in Requirement class that have the attributes Status that contain the value Draft. 
  •  
    • BOOLEAN: Matches entities in a class with the attribute that contains the value Yes or No, or True or False.
      Operators Supported: =

      For example:
      Plane:“Operational=True” – Matches entities in Plane class that have the attribute Operational that contains the value of Yes.
      OR
      Plane:“Operational=Yes” – Matches entities in Plane class that have the attribute Operational that contains the value of Yes.
    • PERCENT: Matches entities in a class with the attribute that evaluates as true.
      Operators Supported: >, <, >=, <=, =

      For example:
      Action:“Percent Complete>75” – Matches entities in Action class that have the attributes Percent Complete that is greater than 75. 
    • DATETIME: Matches entities in a class with the attribute that evaluates as true. DateTime accepts 12 different DateTime formats. These formats can be seen in the list below. Time is standard to military time so 12 am is 00 and 12 pm is 12.

      Important: Entities with attributes of datetime created before 4.3 will need to have the entities updated to be able to be evaluated correctly. Updates can be any change to the entity and not necessary to the DateTime attribute.

      Operators Supported: >, <, >=, <=, =
      DateTime Supported Formats:
      yyyy-MM-dd HH:mm:ss
      yyyy-MM-dd HH:mm
      yyyy-MM-dd
      MM-dd-yyyy HH:mm:ss
      MM-dd-yyyy HH:mm
      MM-dd-yyyy
      yyyy/MM/dd HH:mm:ss
      yyyy/MM/dd HH:mm
      yyyy/MM/dd
      MM/dd/yyyy HH:mm:ss
      MM/dd/yyyy HH:mm
      MM/dd/yyyy

      For example:
      Action:“Start<2020-12-25 13:45:30” – Matches entities in Action class that have the attributes Start that is less than 1:45.30 pm on December 25, 2020. 
    • URI: Matches entities in a class with the attribute that contains the string of text.
      Operators Supported: =

      For example:
      Virtual:“URI=google” – Matches entities in Virtual class that have the attributes URI that contain the value google. 
    • FILE: Matches entities in a class with the attribute that contains a file attachment.
      Operators Supported: =

      For example:
      Artifact:“File=True” – Matches entities in Artifact class that have the attribute File that contains a file attachment.
      OR
      Artifact:“File=Yes” – Matches entities in Artifact class that have the attribute File that contains a file attachment.
    • DURATION: Matches entities in a class with the attribute that evaluates as true.
      Operators Supported: >, <, >=, <=, =

      Important: Entities with attributes of duration created before 4.3 will need to have the entities updated to be able to be evaluated correctly. Updates can be any change to the entity and not necessary to the duration attribute.


      For example:
      Action:“Duration>=1.5 Hours” – Matches entities in Action class that have the attributes Duration that is greater than or equal to 1.5 hours. 
    • GEOPOINT: Matches entities in a class with the attribute that evaluates as true. GeoPoint attribute search can be searched by a single value or pair of values separated by a comma.
      Operators Supported: >, <, >=, <=, =

      For example:
      Physical:“Coordinates>37.0902” – Matches entities in Physical class that have the attributes Coordinate that greater than 37.0902.
      OR
      Physical:“Coordinates=37.0902, 95.7129” – Matches entities in Physical class that have the attributes Coordinate that equal 37.0902 and 95.7129.
    • QUALITY: Matches entities in a class with the attribute that contains the value Yes or No, or True or False.
      Operators Supported: =

      For example:
      Requirement:“Clear=True” – Matches entities in Requirement class that have the attribute Clear that contains the value of Yes.
      OR
      Requirement:“Clear=Yes” – Matches entities in Requirement class that have the attribute Clear that contains the value of Yes.
    • MULTIPLICITY: Matches entities in a class with the attribute that contains the string of text.
      Operators Supported: =

      For example:
      Vehicle:“Wheels=2..4” – Matches entities in Vehicle class that have the attributes Wheels that contain the value 2..4. 
    • USER_TEAM: Matches entities in a class with the attribute that contains the string of users or teams.
      Operators Supported: =

      Important: Entities with attributes of user_team created before 4.3 will need to have the entities updated to be able to be evaluated correctly. Updates can be any change to the entity and not necessary to the user_team attribute.


      For example:
      Issue:“Assignee=support” – Matches entities in Issue class that have the attribute Assignee that contains the user support.
    • MULTISELECT: Matches entities in a class with the attribute that contains the enumeration text.
      Operators Supported: =

      Important: Entities with attributes of multiselect created before 4.3 will need to have the entities updated to be able to be evaluated correctly. Updates can be any change to the entity and not necessary to the multiselect attribute.


      For example:
      Flag:“Color=green” – Matches entities in Color class that have the attributes Color that contain the values green.

  • Diagram Search
    Diagram searches allow you to search for diagrams created from entities. The list below outlines of the searches that can be performed on each Diagram type. In addition to this list provided below, Diagrams names can always be found in Diagrams View or on the left sidebar on each diagram. Search for diagrams is not case sensitive to evaluate correctly.

Diagrams Type

Supported Diagram Name

A0_DIAGRAM

icom, icom diagram

IDEF0_DIAGRAM

idef0, idef0 diagram

LAYER

layer, layer diagram

LML_ACTION

action, action diagram

LML_ASSET

asset, asset diagram

LML_HIERARCHY

hierarchy, hierarchy chart, hierarchy diagram

LML_I2

i2, i2 diagram, i-squared, i-squared diagram

LML_ICD

icd, interface control, interface control diagram

LML_N2

n2, n2 diagram, n-squared, n-squared diagram

LML_PHYSICAL_INPUT_OUTPUT_DIAGRAM  

physical, physical diagram, physical i/o, physical i/o diagram

LML_RISK

risk, risk diagram

LML_SPIDER_DIAGRAM

spider, spider diagram

LML_TIMELINE

timeline, timeline diagram

RADAR_DIAGRAM

radar, radar diagram

SYSML_ACTIVITY

activity, activity diagram

SYSML_BDD

bdd, bdd diagram, block definition, block definition diagram

SYSML_IBD

ibd, ibd diagram, internal block, internal block diagram

SYSML_PACKAGE

package, package diagram

SYSML_PARAMETRIC

parametric, parametric diagram

SYSML_REQUIREMENTS

requirement, requirements, requirement diagram, requirements diagram

SYSML_SEQUENCE

sequence, sequence diagram

SYSML_STATE_MACHINE

state machine, state machine diagram

SYSML_USE_CASE

use case, use case diagram

TREE

tree, tree diagram

UML_CLASS

class, class diagram

 

List of Available Qualifiers

The table below outlines of all the search qualifiers supported by the Innoslate search system.

 

Search Qualifier

Example Search

Returns

id:value

Id:1

Entities where the id is equal to specified value.

attributeid:"attribute id=value"

Attributeid:"1=1"

Entities where the specified attribute value equals the searched value.

class:"attribute name=value"

Action:"Percent Complete=45"

Entities where the specified attribute value equals the searched value. See Attribute Search above for more details.

class:name

class:Action

Entities of the specified schema-based class.

diagram:diagram type

diagram:LML_ACTION

Entities which have that specific diagram enum. See Diagram Search above for more details.

diagram:diagram name

diagram:"Action Diagram"

Entities which have that specific diagram name. See Diagram Search above for more details.

relationshipid:relation Id

relationshipid:1

Entities that contain the relationship type.

relationship:relation name

relationship:"decomposed by"

Entities that contain the relationship type.

order:type

order:number

Orders the results by either name, number, or modified in ascending order. Including a minus after the type (ex. order:number-) will sort descending.

is:crossproject

is:crossproject

Entities with cross project relationships.

is:diagram

is:diagram

Entities that have a generated diagram within Innoslate.

is:leaf

is:leaf

Entities with no children (no target relationships on decomposed by).

is:orphan

is:orphan

Entities with no target relationships to any other entity.

is:root

is:root

Entities with no parents (no target relationships on decomposes).

label:name

label:Activity

Entities with the specified label applied.

is:top

is:top

Entities which are the top of an overall hierarchy (documents, root diagrams, etc.).

number:number

number:5.1

Entities with the specified number.

globalid:global Id

globalid:I_1E3MYNY9MGHV_9WCAZFAFXJW6C  

Entities which have the supplied global id.

Database Variances

Innoslate supports multiple databases. Each database behaves slightly different when it comes to search. The table below is to help illustrate these differences. Four entities were created for this search example. The first three entities had the name, number, or description filled in with “Innoslate is a MBSE tool”. The fourth had the number field filled in with I.1.12. 




 

Microsoft SQL

PostgreSQL 

H2

Name:

     

Name:is

*

*

*

Name:"is%"

 

X

X

Name:"%is%"

X

X

X

Name:Innoslate

X

X

 

Name:Inn*

X

X

X

Name:Inn%

X

X

X

Name:_n*

 

X

X

Name:_%

X

X

X

Name:"MB*"

X

   

Name:"MB%"

 

X

X

Name:"%MB%"

X

X

X

Name:"MBSE"

X

X

 

Name:"MBSE tool"

X

X

 

Name:Innoslate is a MBSE tool

X

X

 

Name:"Innoslate is a MBSE tool"

X

X

 

Number:

     

Number:is

*

*

*

Number:"is%"

 

X

X

Number:"%is%"

X

X

X

Number:_.*

X

X

X

Number:_.%

 

X

X

Number:Innoslate

X

X

 

Number:Inn*

X

X

X

Number:Inn%

X

X

X

Number:_n*

 

X

X

Number:_%

X

X

X

Number:"MB*"

X

   

Number:"MB%"

 

X

X

Number:"%MB%"

X

X

X

Number:"MBSE"

X

X

 

Number:"MBSE tool"

X

X

 

Number:Innoslate is a MBSE tool

X

X

 

Number:"Innoslate is a MBSE tool"

X

X

 

Description:

     

Description:is

*

*

*

Description:"is%"

 

X

X

Description:"%is%"

X

X

X

Description:Innoslate

X

X

 

Description:Inn*

X

X

X

Description:Inn%

 

X

X

Description:%Inn%

X

X

X

Description:_n*

 

X

X

Description:_%

X

X

X

Description:"MB*"

X

   

Description:"MB%"

 

X

X

Description:"%MB%"

X

X

 

Description:"MBSE"

X

X

 

Description:"MBSE tool"

X

X

 

Description:Innoslate is a MBSE tool

X

X

 

Description:"Innoslate is a MBSE tool"

X

X

 

ALL:

     

is

*

*

*

"is%"

 

X

X

"%is%"

X

X

X

Innoslate

X

X

 

Inn*

X

X

X

Inn%

**

X

X

%Inn%

X

X

X

_n*

 

X

X

_%

X

X

X

"MB*"

X

   

"MB%"

 

X

X

"%MB%"

X

X

X

MBSE

X

X

 

"MBSE"

X

X

 

"MBSE tool"

X

X

 

Innoslate is a MBSE tool

X

X

 

"Innoslate is a MBSE tool"

X

X

 

_.*

X

X

X

_.%

X

X

X

Innoslate is a MB*

X

X

***

Innoslate is a MB%

 

X

***



*: Stop word, so all results are true

**: Only Name and Number

***: Only Number and Description