Is there a manual or lesson on how Virtual Items are supposed to work in eB?

I'm trying to define attributes for a virtual item, but can't figure out how all the various types of virtual items are supposed to relate to one another (ungrouped vs grouped VI and Virtual Item Groups).

Is there a good use-case example of how these all inter-relate?

Parents
  • Here is what we are trying to model.

    We have an excel file for a bunch of tests that need to be performed. (Example, ensure pump xxx-xxx can perform yy gpm of flow). It then has some information like max/min/uncertainty values and text fields like "Notes", "Prerequisites". Finally it lists which requirements the tests originate from (Licensing/Design Documents).

    My initial thought was to model these tests as Virtual Items. Here is what I'm thinking.

    1) Create VI Class called "Test Requirements". Add all rows in the excel sheet as a VI. (Only has Code, Class, Description)

    2) Create VIG Class called "Test Requirements" as a VIG Structure. Here is where I would define all of the attributes that are in my excel sheet column headers.

    3) Create a VIG Template from the VIG Class. In eB web, create a VIG from this template. (As shown by Priyanka)

    4) Add all of the Ungrouped VIs to this VIG as members. This would create Grouped Virtual Items that have the attributes that I defined in step 2.

    5) Add the rest of the attributes in the excel sheet to these new Grouped VIs that were created.

    6) Approve the VIG and grouped VI once all of the members and attributes have been added.

    Does this sound correct? If so, I'd imagine that the provisioning spreadsheet would help somehow with this process?

Reply
  • Here is what we are trying to model.

    We have an excel file for a bunch of tests that need to be performed. (Example, ensure pump xxx-xxx can perform yy gpm of flow). It then has some information like max/min/uncertainty values and text fields like "Notes", "Prerequisites". Finally it lists which requirements the tests originate from (Licensing/Design Documents).

    My initial thought was to model these tests as Virtual Items. Here is what I'm thinking.

    1) Create VI Class called "Test Requirements". Add all rows in the excel sheet as a VI. (Only has Code, Class, Description)

    2) Create VIG Class called "Test Requirements" as a VIG Structure. Here is where I would define all of the attributes that are in my excel sheet column headers.

    3) Create a VIG Template from the VIG Class. In eB web, create a VIG from this template. (As shown by Priyanka)

    4) Add all of the Ungrouped VIs to this VIG as members. This would create Grouped Virtual Items that have the attributes that I defined in step 2.

    5) Add the rest of the attributes in the excel sheet to these new Grouped VIs that were created.

    6) Approve the VIG and grouped VI once all of the members and attributes have been added.

    Does this sound correct? If so, I'd imagine that the provisioning spreadsheet would help somehow with this process?

Children