Monday, February 24, 2014

Autodesk Vault Programmer’s Cookbook. 1.3. Objects of Vault



Navigation:

|
|

There's so-called “model of labor” by Mardakhayev, that’s corresponding to IDEF0 model.

It describes the mechanism of labor. So, for hammering a shelf:
  • What is – boards, nails
  • What should be – assembled shelf
  • Object of labor – separate nails and boards
  • Instrument – hammer
  • Algorithm – “Keep calm and hammer on”
Applying to Vault API, the model of work with Vault is:


  • What is – current state of object/information
  • What should be – required state/information
  • Object of labor – object of Vault
  • Instrument – method of API service
  • Parameters – inputs, that controls method
Probably you’ve got a question: what type of objects we work with? In API they called Classes of Autodesk.Connectivity.WebServices Namespace:
  • Credentials: users, groups, etc.
  • Information units: piles, folders, BOMs, items, change orders, custom objects, e-mail, etc.
  • Properties: properties, access controls, category, revision, lifecycle state, etc.
  • Definitions of: revision, numbering scheme, lifecycle, custom entity, BOM scheme, etc.