0% found this document useful (0 votes)

583 views

Programmers Guide

Aras Programmer Guide

Uploaded by

Anonymous Lz6f4C6KF

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

583 views

Programmers Guide

Aras Programmer Guide

Uploaded by

Anonymous Lz6f4C6KF

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 91

Aras Innovator

Programmer's Guide

Aras Innovator 8.1

Document #: 8.1.12042006
Last Modified: 4/4/2007

Aras Corporation

All Rights Reserved.

ARAS CORPORATION

Copyright 2006 Aras Corporation. All rights reserved

Aras Corporation
Heritage Place
439 South Union Street
Lawrence, MA 01843
Phone: 978-691-8900
Fax: 978-794-9826
E-mail: [email protected]
Website: http://www.aras.com
Notice of Rights

Copyright 2006 by Aras Corporation. This material may be distributed only

subject to the terms and conditions set forth in the Open Publication License, V1.0 or
later (the latest version is presently available at
http://www.opencontent.org/openpub/).
Distribution of substantively modified versions of this document is prohibited without
the explicit permission of the copyright holder.
Distribution of the work or derivative of the work in any standard (paper) book form
for commercial purposes is prohibited unless prior permission is obtained from the
copyright holder.
Aras Innovator, Aras, and the Aras Corp "A" logo are registered trademarks of Aras
Corporation in the United States and other countries.
All other trademarks referenced herein are the property of their respective owners.

Notice of Liability

The information contained in this document is distributed on an "As Is" basis,

without warranty of any kind, express or implied, including, but not limited to, the
implied warranties of merchantability and fitness for a particular purpose or a
warranty of non-infringement. Aras shall have no liability to any person or entity
with respect to any loss or damage caused or alleged to be caused directly or
indirectly by the information contained in this document or by the software or
hardware products described herein.

Page 2

Table of Contents
SEND US YOUR COMMENTS ...........................................................................................7
1

INTRODUCTION..........................................................................................................8
1.1
1.2
1.3

THE ITEM ..................................................................................................................8

THE AML .................................................................................................................9
METHODS AND THE IOM ..........................................................................................9

AML ..............................................................................................................................10
2.1
<ITEM> TAG ...........................................................................................................10
2.2
<RELATIONSHIPS> TAG ..........................................................................................10
2.3
<PROPERTY> TAGS ..................................................................................................10
2.4
ATTRIBUTES............................................................................................................11
2.4.1
Item Attributes................................................................................................11
2.4.2
Property Attributes.........................................................................................12

IOM REFERENCE .....................................................................................................13

3.1
IOMCREDENTIALS CLASS ......................................................................................13
3.2
INNOVATOR CLASS .................................................................................................14
3.3
ITEM CLASS ............................................................................................................14
3.3.1
Base Methods .................................................................................................14
3.3.2
Boolean Methods ...........................................................................................14
3.3.3
Attribute Methods...........................................................................................14
3.3.4
Property Methods...........................................................................................15
3.3.5
File Methods ..................................................................................................15
3.3.6
Relationship Methods.....................................................................................15
3.3.7
Item Collection Methods ................................................................................16
3.3.8
Logical Methods.............................................................................................17
3.3.9
New Methods..................................................................................................17
3.3.10 Error Methods................................................................................................17
3.3.11 Extended Item Class methods ........................................................................18

METHODS ...................................................................................................................19
4.1
ITEM ACTIONS EXTEND THE ITEM CLASS ...............................................................19
4.1.1
Context Item ...................................................................................................19
4.1.2
Methods are Item Factories ...........................................................................20
4.1.3
Handling the Wrong ItemType.......................................................................20
4.1.4
Methodology ..................................................................................................21
4.2
BUILT IN ACTION METHODS ...................................................................................21
4.3
GENERIC METHODS ................................................................................................22
4.3.1
Context Item ...................................................................................................22
4.3.2
Methods are Item Factories ...........................................................................22
4.3.3
Methodology ..................................................................................................23
4.4
SERVER EVENTS .....................................................................................................23
4.4.1
Context Item ...................................................................................................23

Page 3

4.4.2
Methodology ..................................................................................................23
4.4.3
Available Server Events .................................................................................24
4.5
CLIENT EVENTS ......................................................................................................27
4.5.1
Context Item ...................................................................................................27
4.5.2
Form Events ...................................................................................................27
4.5.3
Field Events ...................................................................................................28
4.5.4
Grid Events ....................................................................................................29
4.5.5
Item Actions and Server Event.......................................................................32
5

ACTION ITEMS..........................................................................................................33
5.1
CLIENT SIDE METHOD RULES .................................................................................33
5.2
SERVER SIDE METHOD RULES ................................................................................34
5.3
USE CASES ..............................................................................................................35
5.3.1
Client side - has cache Item is dirty...............................................................35
5.3.2
Client side - no cache Item - no item_query value.........................................35
5.3.3
Client side - has cache Item not dirty - no item_query value ........................35
5.3.4
Client side - has cache Item not dirty - has item_query value.......................36
5.3.5
Client side - no cache Item - has item_query value .......................................36
5.3.6
Server side - has cache Item is dirty ..............................................................36
5.3.7
Server side - no cache Item - no item_query value........................................37
5.3.8
Server side - has cache Item not dirty - no item_query value........................37
5.3.9
Server side - has cache Item not dirty - has item_query value ......................38
5.3.10 Server side - no cache Item - has item_query value ......................................38

ARAS INNOVATOR METHODOLOGY.................................................................39

COOKBOOK ...............................................................................................................40
7.1
7.2
7.3
7.4
7.5
7.6
7.7
7.8
7.9
7.10
7.11
7.12
7.13
7.14
7.15
7.16
7.17
7.18
7.19

CREATE AN ARAS INNOVATOR OBJECT...................................................................40

CREATE AN ITEM OBJECT .......................................................................................40
QUERY FOR AN ITEM ...............................................................................................41
QUERY AND ITERATE OVER A SET OF ITEMS ............................................................42
QUERY FOR AN ITEM AND RETURN ITS CONFIGURATION .........................................44
QUERY USING AML TO CONSTRUCT THE QUERY.....................................................47
QUERY FOR THE ITEM NEXT PROMOTION STATES ....................................................47
QUERY USING RELATIONSHIPS AS SEARCH CRITERIA ...............................................48
ADD AN ITEM CONFIGURATION IN ONE TRANSACTION ............................................50
ADD A NAMED PERMISSION ....................................................................................51
SET A PRIVATE PERMISSION FOR AN ITEM ..............................................................51
APPLY A GENERIC METHOD....................................................................................52
NEED A MISSING NAMESPACE .................................................................................52
NEED TO SAVE TEXT TO A FILE ...............................................................................53
NEED TO SEND EMAIL FROM A METHOD .................................................................54
NEED TO ADD A C# CONTROL ................................................................................55
NEED FOR SPEED APPLYSQL..................................................................................56
NEED A CALLBACK FOR A RELATIONSHIPS GRID ROW EVENT ................................57
NEED A CALLBACK FOR A RELATIONSHIPS GRID CELL EVENT................................58

Page 4

7.20
7.21
7.22
7.23
7.24
7.25
7.26
7.27
7.28
7.29
7.30
7.31
8

SHOW RELATIONSHIPS IN A GRID CONTROL ON THE FORM ......................................59

SHOW RELATIONSHIPS IN AN EXCEL COMPONENT ON THE FORM ............................60
OPEN THE RELATIONSHIPS IN AN EXCEL DOCUMENT ..............................................61
PAGE FIELDS ON THE FORM USING TABBAR ............................................................62
WANT THE IDENTITIES FOR THE USER .....................................................................64
WANT A FIELD TO BE EITHER A SEQUENCE OR USER ENTERED VALUE .....................64
WANT TO VAULT A FILE .........................................................................................65
WANT TO GET AN EXISTING VAULTED FILE AND SAVE IT WITH A NEW DOCUMENT 65
WANT TO OPEN A VAULTED FILE IN WORD ............................................................66
NEED TO REJECT AN ITEM PROMOTE .......................................................................67
HOW TO BUILD XML FOR A GRID ...........................................................................68
HOW TO BUILD XML FOR A MENU .........................................................................71

.NET CONTROLS.......................................................................................................72
8.1
GRID/TREEGRID/EXCELGRID CONTROL .................................................................73
8.1.1
Initialization from XML .................................................................................73
8.1.2
Grid Methods and Events...............................................................................73
8.1.3
TreeGrid Methods and Events .......................................................................73
8.1.4
ExcelGrid Methods ........................................................................................73
8.1.5
Cell Methods ..................................................................................................73
8.1.6
ContextMenu Methods ...................................................................................74
8.2
MENU BAR ..............................................................................................................74
8.2.1
Initialization from XML .................................................................................74
8.2.2
MainMenu Methods and Events.....................................................................74
8.2.3
Menu Element Methods..................................................................................74
8.3
WORKFLOW ............................................................................................................75
8.3.1
Initialization from XML .................................................................................75
8.3.2
Workflow Methods and Events.......................................................................75
8.3.3
Workflow Item Methods .................................................................................75
8.4
TOOLBAR ................................................................................................................75
8.4.1
Initialization from XML .................................................................................75
8.4.2
Toolbar Methods and Events .........................................................................75
8.4.3
Active Toolbar Methods.................................................................................75
8.4.4
Toolbar Item Methods....................................................................................76
8.5
STRUCTURE.............................................................................................................76
8.5.1
Structure Container Methods and Events ......................................................76
8.5.2
Structure Item Methods..................................................................................76
8.6
GANTT ....................................................................................................................76
8.6.1
Initialization from XML .................................................................................76
8.6.2
ProjectTree Methods......................................................................................77
8.6.3
Task Methods .................................................................................................77
8.6.4
Dependency Methods .....................................................................................77
8.7
STATUS BAR ...........................................................................................................77
8.7.1
Initialization from XML .................................................................................77
8.7.2
Status Bar Methods ........................................................................................77

Page 5

8.8
UTILITY CONTROL ..................................................................................................77
8.8.1
Utility Methods...............................................................................................77
8.8.2
Balloon Methods ............................................................................................77
8.8.3
Splash Screen Methods and Events................................................................78
8.9
OTHER CONTROLS ..................................................................................................78
8.9.1
Tabbar Methods and Events ..........................................................................78
8.9.2
Calendar Methods and Events .......................................................................78
8.9.3
Vault Methods and Events .............................................................................78
8.9.4
Color Dialog Method.....................................................................................78
9

ARAS INNOVATOR SOLUTION STUDIO ............................................................79

9.1

FEATURES ...............................................................................................................79
DEBUGGING...........................................................................................................80

10.1
10.2
10.3
11

SETTING UP VS.NET 2003 TO DEBUG SERVER SIDE METHODS ...............................80

SETTING UP VS.NET 2003 TO DEBUG CLIENT SIDE METHODS ................................81
SETTING UP THE SERVER SIDE LOGGING ..................................................................82
EXTERNAL APIS ...................................................................................................83

11.1
11.2
11.3

.NET COMPONENT ..................................................................................................83

ACTIVEX CONTROL ................................................................................................83
SOAP REQUESTS ....................................................................................................84

WAS/IS API COMPARISON.................................................................................86

AML SCHEMA........................................................................................................89

Page 6

Send Us Your Comments

Aras Corporation welcomes your comments and suggestions on the quality and
usefulness of this document. Your input is an important part of the information used
for future revisions.
o

Did you find any errors?

Is the information clearly presented?

Do you need more information? If so, where and what level of detail?

Are the examples correct? Do you need more examples?

What features did you like most?

If you find any errors or have any other suggestions for improvement, please
indicate the document title, and the chapter, section, and page number (if available).
You can send comments to us in the following ways:
o

Email:
[email protected]
Subject: Aras Innovator Documentation

Postal service:
Aras Corporation
Heritage Place
439 South Union Street
Lawrence, MA 01843
Attention: Aras Innovator Documentation

FAX:
978-794-9826
Attn: Aras Innovator Documentation

Or,

If you would like a reply, please provide your name, email address, address, and
telephone number.
If you have usage issues with the software, please visit
http://www.aras.com/support/

Page 7

1 Introduction
The purpose of this document is to provide a Guide to Programming Aras Innovator.
It covers key aspects of programming Aras Innovator for implementing your own
business logic within the Aras Innovator Enterprise Application Framework.
This document is indented to be used as a Desktop Reference and User Guide
covering the following topics:

1.1

The AML (Aras Markup Language), which is the language that drives the Aras
Innovator server.
The IOM (Innovator Object Model), which is the Object API for the AML.

Explains how Methods work and the Methodology for implement your own
business logic.
A Cookbook of recipes for performing common tasks.

The .NET controls API the Innovator Client is built on.

The Item

Everything in Aras Innovator is an Item, which is an instance of an ItemType, which

itself is an Item; illustrating that Aras Innovator is a self describing system. Don't
get hung up on the self-describing nature on Aras Innovator and focus on the
simplicity that everything eventually is an Item.
Items may have relationships to other Items illustrating that Items has structure.
Relationships are defined by RelationshipType, which is an Item that has three
properties to define the RelationshipType rule for the source (parent) Item, related
(child) Item, and relationship Item, which defines.

When the RelationshipType is created an "is_relationship" ItemType is also created

named the same as the RelationshipType and its id is the value to the relationship_id
Property on the RelationshipType. This can get a bit confusing but simply put there
is a RelationshipType/ItemType pairing to define the RelationshipType rule and an
ItemType to store the relationship Items.
Relationship Items have a related_id Property of type Item, which is the related
(child) Item for the relationship. The related_id Property is a link that points to an
Item. The relationship Item also has a source_id Property of type Item and is the
source (parent) Item for the relationship.
So, in Aras Innovator everything is an Item, and Items may have relationships,
which are Items that has source and related Item Properties forming an Item
configuration.

For example, an ItemType Item has Property relationships and this Item
configuration maps directly to the relational database for persistent storage of the
Item instances. Every ItemType has a matching relational TABLE where the Property
names are the COLUMN names.

Page 8

1.2

The AML

The AML (Aras Markup Language) is an XML dialect that follows the simple
/Item/Relationships/Item/Relationships repeating pattern to describe Item
configurations. Clients submit AML documents to the Aras Innovator server and
receive an AML document back.

An AML document contains data (Items), structure (Relationships, which are

hierarchical Items), and logic (an action to perform some business logic on the
Item). Each Item in the AML document has an action attribute, which is the name of
an Aras Innovator Method that performs business logic on the Item. The Aras
Innovator server interprets AML documents similar to scripting languages, AML
documents are often referred to as AML scripts.
This is an example of a BOM in AML language:

<Item type="Part" action="add">

<item_number>999-888</item_number>
<description>Some Assy</description>
<Relationships>
<Item type="Part BOM" action="add">
<quantity>10</quantity>
<related_id>
<Item type="Part" action="add">
<item_number>123-456</item_number>
<description>1/4w 10% 10K Resistor</description>
</Item>
</related_id>
</Item>
</Relationships>
</Item>

1.3

Methods and the IOM

The IOM (Innovator Object Model or Item Object Model) is an Object Model on top of
the AML. It provides the ability to build and submit AML documents to the Aras
Innovator Server using a simple Object API.

There is the "Method" ItemType, which are used to implement user defined business
logic. Methods are written in JavaScript, C#, J#, or VB.Net and use the IOM API to
implement the business logic. Three of these four programming languages
JavaScript, C#, and VB.Net are supported by MS .NET 1.1/2.0 Framework by default,
but if you want to program Innovator using J# make sure that Microsoft Visual J#
Redistributable Package is installed on your Innovator server.
The following is a Method in JavaScript using the IOM that is the same as the AML
BOM example above:
var innovator = new Innovator();
var partItem = innovator.newItem("Part","add");
partItem.setProperty("item_number", "999-888");
partItem.setProperty("description", "Some Assy");
var bomItem = innovator.newItem("Part BOM","add");
bomItem.setProperty("quantity", "10");
var relatedItem = new Item("Part","add");
relatedItem.setProperty("item_number", "123-456");
relatedItem.setProperty("description", "1/4w 10% 10K Resistor");
bomItem.setRelatedItem(relatedItem);
partItem.addRelationship(bomItem) ;

Page 9

var resultItem = partItem.apply();

2 AML
The AML is the XML dialect and language that drives the Aras Innovator server.
Clients submit AML documents to the Aras Innovator server via HTTP. The server
parses the AML applying the business logic defined as the action attribute for the
Items in the AML document, and an AML document is returned. The AML dialect is
very simple and the following tags define the AML language:

2.1

<Item> Tag

The <Item> tag defines an Item instance. XML is case sensitive (notice the capitalized
Item.) There are three principle attributes for the Item tag to define the Item
instance:

id which is the unique ID for the Item.

action which is the name of the Method that is applied to the Item.

type which is the ItemType name for the Item.

There are other attributes but these are the most significant, which defines the Item
and the action to apply on it. The following is an AML query example requesting a
Part Item by ID:
<Item type="Part" id="ACBDEF0123456789" action="get"/>

See section 4.2 for the list of Innovator pre-built actions.

2.2

<Relationships> Tag

Items can have relationships to other Items. The <Relationships> tag is a container
tag that holds the set of relationship Items. Again notice the capitalized
Relationships. There are no attributes for the tag it is just a container. With
relationships it is possible to describe an Item configuration to any level deep as
necessary.
The following is an AML query example requesting a Part Item and its BOM
relationships:
<Item type="Part" id="ACBDEF0123456789" action="get">
<Relationships>
<Item type="BOM" action="get"/>
</Relationships>
</Item>

2.3

<property> Tags

Properties for the Item are the nested tags directly below the <Item> tag. The
Property name is the tag name. For example, a "Part" ItemType may have the
properties: part_number, part_description, and part_cost, which are also the tag
names in the AML. Property names are lowercase so the property tag names are
also lowercase.

Page 10

The following AML illustrates a simple Item configuration for describing a Part to Part
BOM relationship:
<Item type="Part" action="add">
<item_number>999-888</item_number>
<description>Some Assy</description>
<Relationships>
<Item type="Part BOM" action="add">
<quantity>10</quantity>
<related_id>
<Item type="Part" action="add">
<item_number>123-456</item_number>
<description>1/4w 10% 10K Resistor</description>
</Item>
</related_id>
</Item>
</Relationships>
</Item>

2.4

Attributes

Properties are used to define the data for an Item; attributes are meta-data for the
Item or Property, which are used to control the server logic and Methods. Think of
attributes like command line switches, or as arguments to a function.
In addition to the type, id, and action attributes mentioned above there are several
additional attributes used to control the server. The following is the attribute
reference for the <Item> tag:
2.4.1 Item Attributes
Attribute
type

Type
String

where

String

Usage

The ItemType name for which the Item is an instance.

String

The unique ID value for the Item instance.

action

String

doGetItem

Boolean

The name of the Method (or Built in Action Method) to apply to the
Item.

Used with action="get"

select

String

orderBy

String

page

Integer

maxRecords

Integer

pagesize
levels

Used instead of the id attribute to specify the WHERE clause for the
search criteria. Include the table name with the column name using the
dot notation: where="user.first_name like 'Tom%'"

If 0 then do not perform a final get action on the Item after the server
performed that action as defined by the action attribute. Default is 1.
A comma delimited list of property names (column names) to return
which is the SELECT clause in the SQL statement.
A comma delimited list of property names (column names) to order the
results and is the ORDER BY clause in the SQL statement.
The page number for the results set.

Integer

The page size for the results set.

Integer

The Item configuration depth to be returned. This should be used with

caution because of the performance hit due to its lack of granularity in
the data fetched. Use the nested Relationships style of defining your
queries to do the same thing but with far greater performance.

This defines the absolute maximum Items to be searched in the

database.

Page 11

serverEvents

Boolean

If 1 then disable the server events improving performance. Default is 0.

related_expand

Boolean

If 0 then do not expand the related_id Property for the relationship

Items to include the related Item. Another word just returns its ID.

isCriteria

Boolean

If 0 then include the nested structure for the Item configuration in the
response but don't use it as search criteria. Default is 1, which will use
the nested structure in the request as search criteria.

Used with action="update"

version

Boolean

If 0 then don't version an Item on update. Default is 1, which is version

the Item (if its a versionable Item) on update.

2.4.2 Property Attributes

Attribute
type

Usage
The ItemType name for which the item is an instance of.

keyed_name

This is the keyed_name Property for the Item referenced by the Item type Property.

condition

This is the condition value for the AML query. The condition value is any valid SELECT
condition supported by the database. This is the list of possible condition values:
eq

Condition

ne
gt

Comments
The SQL conditional symbols:
=, <=, >=, <>, >, and <
are expressed as two letter mnemonic word:
eq, le, ge, ne, gt, and le

Example

le
like

not like
between

not between
in

not in
is

is null

is not null

The value for the Property tag would include wild card symbols,
which are % for any characters and _ for a single character.
Example

<name condition="like">Tom%</name>
This is a range condition and you would include the AND
keyword in the Property tag value.
Example

<cost condition="between">10.00 and 50.00</cost>

This is a set based condition where the value for the Property
tag is a comma delimited list of values for the set.
Example

<name condition="in">'Tom', 'Peter', 'Joe'</name>

Possible values for the Property tag could be null or not null.
Example

Page 12

3 IOM Reference
IOM Reference provides a general description of the IOM (Innovator Object Model or
Item Object Model) API. A more detailed API reference may be obtained from one of
the following:
- On-line: Go to
http://support.aras.com/documentation/documentation.aspx?version=8.1.1.
Under the section Tools, Utilities and Programmers Guides select On-Line
API Guide
- From Innovator Client UI: Login as Innovator Administrator. Under the Help
menu select API Reference
- In Innovator CD Image. Go to the documentation folder and open Aras
Innovator - API Guide.html
The IOM is an Object Model for the AML, but it is not purely Object Oriented. Using
Object Oriented terms, an ItemType is like a "Class" and the Item is like an "Object".
Although the Item is an Object with methods, there is only one Item Class for all
ItemTypes. In a pure Object Oriented representation, there would be a Class for
each ItemType because each ItemType has its own set of Properties to describe the
different Items.
An Item Object is intended to be abstract and pliable; it can represent any Item, for
any ItemType. The Item Object can be a single Item instance, or can be a set of
Items (as in the case for results from a query), or an Error.

The IOM is intended to be a generic and compact API for modeling the Item structure
for the AML as abstract Objects. The majority of the methods for the IOM deal with
memory management of the AML document for the Item. The AML is a script sent as
a message to the Aras Innovator Server; the IOM is an Object API to build the AML
messages and submit them via the Item.apply() method.
Please note, the term method has two meanings in this guide, the typographical
convention used throughout this Guide is as follows:

Lowercase "method" refers to methods on an IOM Item Object.

Sample code is shown in Courier 8pt font.

3.1

Capitalized "Method" refers to Method Items stored in the Aras Innovator

database.
Optional arguments are surrounded by [] characters.

IOMCredentials Class

The IOMCredentials Class defines the login credentials for connecting to the Aras
Innovator Server. The Item Class has a credentials public property, which is an
IOMCredentials Object.

Typically, you do not need to know about or deal with the credentials Object because
the Methods run in logged in session. You can, however, set the credentials for the
Item Object using these methods, if you want to submit the apply requests to a

Page 13

different Aras Innovator server. The IOMCredentials Class methods are mostly
getters and setters for URLs (Innovator and Vault servers), DB name, and login
name and password.

3.2

Innovator Class

In Innovator Class, methods like applyAML(), applyMethod(), and applySQL(),

being type Item, send the apply request to the Aras Innovator Server. In response,
the Server creates XML that apply_ methods use to construct an Item Object to
return; methods like getItemById() and getItemByKeyedName() search the
database the logged in session is connected to, and methods like newItem(),
newError() and newResult() construct a new instance of the Item Object.
Other members of this class perform miscellaneous non-Item related operations.
Use them if you need to get a new GUID (methods getNewID() ), generate a next
sequence value (method getNextSequence() ), or calculate the MD5 hash value for
a given string (method calcMD5() .)

3.3

Item Class

An Item Object can represent an Item, or a set of Items, or an Error.

Item public constructor has one required argument itemtype-name and one optional
argument action. The new Item will only be populated with the Properties and
default values from the ItemType when the optional action argument is "add".
The Item Class public field dom represents a DOM Object that holds the data for the
Item in the AML format.
3.3.1 Base Methods

The Item Class base method apply()submit the AML apply request to Innovator
Server using the context Item DOM as AML source and returns a new Item built on
the XML returned by the Server. In contrast, the base method loadAML() does not
return a new Item but rather rebuilds this.dom using AML taken as an argument.

You can call clone()method to get a new identical instance of the context Item and
you can call setNewID() method to replace the context Item id by newly generated
GUID.
3.3.2 Boolean Methods

Call method isCollection()to find out whether or not the Item represents a set of
Items, e. g. whether or not its dom property holds more then one Item node. Call
isError()method to find out whether or not the Item represents an Error. See IOM
API on-line reference for more boolean members of the Item Class.
3.3.3 Attribute Methods

Methods like getAction(), getID(), and getType() return a value of Item node
action, id, and type attribute respectively, while method getAttribute() takes an
attribute-name as an argument and, therefore, can be used to get any attribute by

Page 14

name. Thus, getAction()is a short cut to getAttribute(action), getID() is a

short cut to getAttribute(id), and so on.
Each get method in this group has a corresponding set method: setAction(),
setID(),setType(), and setAttribute(). Notice that method
setAttribute() not only sets new value for an existing attribute but can also add
a new attribute to the Item node and then sets its value.
3.3.4 Property Methods

Property methods comprise set of accessors to Item properties and Item propertys
attributes: get_, set_ (which acts also as add_), and remove_. In addition, if
property has/need a nested Item there are methods to get/insert such nested Item.
Accessors to Properties are getProperty(), setProperty(), and
removeProperty().These methods take property-name as an argument.
Accessors to Propertys attribute are getPropertyAttribute(),
setPropertyAttribute(), and removePropertyAttribute().
take property and attribute names as arguments.

These methods

Method setProperty()/setPropertyAttribute()not only sets new value for an

existing Item property/ propertys attributes but creates new property/ propertys
attributes and then sets its value if the property/ propertys attributes with a given
name does not yet exist.
Accessors to Propertys nested Item are: getPropertyItem(),
setPropertyItem(), and createPropertyItem(). All these methods take
property name as an argument, and method setPropertyItem() needs, in
addition, an Item Object as the second argument to create a DOM for the nested
Item.
3.3.5 File Methods

If the Item method getType() returns File then two methods getFileName() and
setFileName() can be used as accessors to the file name of the attached file. For
an item of type other then File these methods throw an exception.
3.3.6 Relationship Methods

Relationship methods comprise set of Items relationship accessors:

getRelationships(), addRelationship(), createRelationship(), and
removeRelationship(). The difference between createRelationship() and
addRelationship(), two methods that both are adding an Item node to the
Relationship parent node, is subtle. Lets consider the following server-side VB
method to illustrate how createRelationship()works:
Dim myInnovator As Innovator = Me.NewInnovator()
Dim myItem As Item = myInnovator.NewItem("myType","myAction")
myItem.createRelationship("User","add")

This code results in following myItem.dom XML

Page 15

Similar code that exercises addRelationship() methods is

Dim myInnovator As Innovator = Me.NewInnovator()
Dim myItem As Item = myInnovator.NewItem("myType","myAction")
Dim relItem As Item = myInnovator.NewItem("User","add")
myItem.addRelationship(relItem)

and this code results in following myItem.dom XML:

As you can see addRelationship() produces in this case more detailed Item node
under the Relationship parent node.
There are three methods getRelatedItem(), setRelatedItem(), and
createRelatedItem() that are valid for relationship Item only and are used as a
short cut to the Item.get/setPropertyItem() methods.
3.3.7 Item Collection Methods

This group comprises methods to work with collections. Collection in this context is a
set of Items as in the case for results from a query. Method appendItem() appends
its Item Object argument to an existing collection or converts a single Item instance
to set of Items. This mechanism is illustrated in a C# sample below:
Innovator myInnovator = this.newInnovator();
Item myItem = myInnovator.newItem("myType","myAction");

At this point, myItem presents a single Item instance, myItem.dom XML looks like
this:
<Item isNew="1" isTemp="1" type="myType" action="myAction" />

and myItem.isCollection() returns false. But three extra line of code:

Item addedItem = myInnovator.newItem("added","myAction");
// set ID to be able to remove addedItem later
addedItem.setID(myInnovator.getNewID());
myItem.appendItem(addedItem);

converts myItem to a collection, e.g. myItem.isCollection() returns true, and

myItem.dom XML becomes as following:
<Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Body>
<Result>
<Item isNew="1" isTemp="1" type="myType" action="myAction" />
<Item isNew="1" isTemp="1" type="added" action="myAction" id="B12F9384B1DE4C4F8158C36D18269BE9" />
</Result>
</Body>
</Envelope>

If the Item object id is not NULL it can be removed from the collection:
myItem.removeItem(addedItem);

Page 16

Use getItemCount() method to determine the size of a collection,

getItemByIndex() method to get an instance of the Item Object based on its
position inside of the collection, and method getItemsByXPath() to find an Item by
its XPath.
3.3.8 Logical Methods

The methods newOR(), newAND(), and newNOT() insert logical node with tag <or>,
<and> and <not> respectively under the parent Item node and return an Item
Object that represent a newly inserted logical node. For example, the code below :
Innovator myInnovator = this.newInnovator();
Item myItem = myInnovator.newItem("myType","myAction");
Item logicalOR = myItem.newOR();
logicalOR.setProperty("foo", "bar");

produces the following myItem.dom XML:

The method getLogicalItems()returns collection of logical nodes, thus, the

expression myItem.getLogicalItems().getItemByIndex(0).node in the code sample above
would point to the logical node <or>:
<or>
<foo>bar</foo>
</or>

The method removeLogical() removes a logical node specified by methods

argument.
3.3.9 New Methods

In this group there are two methods newItem() and newInnovator() that return
new Item and new Innovator Object respectively. See code samples in sections
3.3.6-:-3.3.8 for these methods usage illustration.
3.3.10 Error Methods

Error methods comprise set of accessors to Error specific properties such as

faultcode (methods get/setErrorWho(),) faultstring (methods
get/setErrorString() ,) faultactor (get/setErrorSource() ,) and detail
(methods get/setErrorDetail() .) Thus, the code sample below
Innovator myInnovator = this.newInnovator();
Item error = myInnovator.newError("default detail");
error.setErrorWho("any number");
error.setErrorString("Hello, World");
error.setErrorSource("myMethod");
error.setErrorDetail("new detail");

will produce the following Error Item DOM:

Page 17

<Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Body>
<Fault>
<faultcode>any number</faultcode>
<faultstring>Hello, World</faultstring>
<faultactor>myMethod</faultactor>
<detail>new detail</detail>
</Fault>
</Body>
</Envelope>

3.3.11 Extended Item Class methods

This set of methods implements specific functionality on the Item, which extends the
base Item Class. For purpose of reference all the Extended Item Class methods are
organized in four categories
Permission method:

getPermission()
Lock methods:
lockItem()
unlockItem()
Life Cycle method:
promote()
Workflow methods:
instantiateWorkflow()
startWorkflow()
cancelWorkflow()
closeWorkflow()
The detailed characteristic and usage illustration of methods above is left outside the
scope of the document. See on-line API reference for more details.

Page 18

4 Methods
Business logic in Aras Innovator is implemented using Method Items and are written
in JavaScript, C#, J#, or VB.Net often using the IOM to interact with Aras Innovator
Items.
There are three ways to implement Methods in Aras Innovator on the server side:

Item Action Methods which extend the Item Class and perform logic on Item
instances.
Generic Methods, which implement arbitrary logic.

Server Events which implement logic on the context Item before and\or after
the server operates on the Item.

Similarly there are three ways to implement Methods in Aras Innovator on the client
side:

Item Methods which extend the Item Class and perform logic on Item
instances.
Generic Methods, which implement arbitrary logic.

Form, Field, and Grid Events which implement logic on client side UI events.

The Method Item has a comment Property that you can use to annotate the Method
and can be seen when you search and review the Methods as mentioned above.

4.1

Item Actions Extend the Item Class

One purpose for Methods is to extend the Item Class. Methods extend the Item
Class when they are bound as the related Item for "Item Action" relationships on the
ItemType. In the AML the Method name is the action attribute name for the Item
tag.
<Item type="My ItemType" action="My Method" id=""/>

The Method could be called using the IOM like this (all three examples below are
equivalent and are written in C#):
1) Item myItem = this.newItem("My ItemType", "My Method");
myItem.setID(this.getID());
Item results = myItem.apply();
2) Item myItem = this.newItem("My ItemType");
myItem.setID(this.getID());
Item results = myItem.apply("My Method");
3) Item myItem = this.newItem();
myItem.setID(this.getID());
myItem.setType("My ItemType");
myItem.setAction("My Method");
Item results = myItem.apply();

4.1.1 Context Item

As it was mentioned above Item Action Methods are executed on an instance of Item
which is called context item (please read section 5 for more details on how context
item is obtained for Item Action Methods). The context item must be referenced

Page 19

inside Item Action Methods as the this keyword in JavaScript, C#, and J#, and the Me
keyword Object in VB.Net. The context item is an instance of IOM Item class;
correspondingly any methods of IOM Item class (see section 3.3 for more details)
could be called on the context item, e.g this.getProperty(foo) (C#) or
Me.getProperty(foo) (VB.Net).
NOTE: In order to be able to execute Methods code Innovator plugs
it into a particular template that provides required code attributes
(method and class boundaries, import statements, etc.). Each
supported language (JavaScript, C#, VB.NET, etc.) have several
available templates in Innovator. All written in the section is
applied to default templates (there is one default template per
supported language). Methods can explicitly redefine the template
that is used during the method compilation. Usage of alternative
templates and methodology of writing valid Methods for them is left
outside the scope of the document.
4.1.2 Methods are Item Factories

Methods follow the Factory design pattern in that they return an Item or Error
Object. The "Item Action" Method must return an Item, which often is the result of
an Item.apply() method call; typically the last step in the business logic for the
Method. There are several ways to create an Item; the following IOM methods
return an Item Object: Item.apply(), Item.newItem(), Item.clone(),
Innovator.newItem(), Innovator.newResult(), and Innovator.newError().
C#

Item qryItem = this.newItem(this.getType(), "get");

qryItem.setID(this.getID());
qryItem.setLevels(1);
return qryItem.apply();

If the Method needs to return an Error then use the Innovator.newError(text)

method.
C#

Innovator innovator = this.newInnovator();

return innovator.newError("This method has <b>failed</b>.");

4.1.3 Handling the Wrong ItemType

Sometimes it is desirable to share the same Method for many ItemTypes. However,
there are cases in which the Method is intended to be used only by an Item of a
specific ItemType.

The way you can prevent the use of a Method with a context item of a wrong type is
to throw an exception when the wrong ItemType is used (this is what the core Item
Class methods do when the ItemType is not of the specific desired value). Here is a
sample of what should be done in a Method that needs to operate on a specific type
of Item:
JScript, C#, or J#

if (this.getType() != "My ItemType") throw("Item must be of type 'My ItemType'");

Page 20

4.1.4 Methodology

One of the principle concepts in programming Aras Innovator is to write Methods

called on Items. The "Item Action" relationships on ItemTypes simulate Object
Oriented programming, where the ItemType is the Class and "Item Action"
relationships to Methods are the Class methods. Literally the Method code is
compiled dynamically to extend the Item Class with this method and calls it (see also
notes to 4.1.1). Similar to class instance in OO programming the context item is an
object on which Methods are performed. At the same time there are some
peculiarities in how to use context item in Innovators Item Action Methods. One
important details about Item Action Methods is that they must always return an Item
which is considered as the result of work done by the Item Action Method. An Item
Action Method might work with context item but the context item is used here more
as an input value (its still must be referenced as this or Me from inside Methods).
Its highly recommended that Item Action Methods do not change the context item
but rather create a new item that will be returned from the method. You can use the
combination of the Item.getProperty() method with the Item.setProperty()
method to populate the new temporary Item or use the Item.clone() method to
construct the new Item from the context item. If developer of Methods code has
choosen to modify the context item and not create a new item, the context item
must be returned from the method.

4.2

Built in Action Methods

The Method name is passed as the action attribute for the <Item> tag in AML.
<Item type="My ItemType" action="My Method" id=""/>

But in addition to Method names as the action attribute value there is also a set of
"Built in Action Methods". These are basically the same as Methods but you will not
find them in the database when searching the Method Items. Nevertheless, they are
called the same way as ordinary Methods via the action attribute.
This is a reference for Built in Action Methods.
Built in
Action
Method

Comments

add

Add the Item as an instance of an ItemType.

update

Updates the Item.

The Item must be locked.

If the Item is versionable and is being updated the first time since being locked
the update versions the Item applying the update to the new version, unless the
version="0" attribute is specified, which disables the versioning.
Delete the version of the Item.

purge
delete
get
getItemConfig

Delete all versions of the Item. The purge and delete are the same for non-versionable
Items.
Gets the Item(s) and its configuration based on the AML Item configuration used to query
the database.
This will return the Item configuration as described by the standard AML query. The AML
in and out are no different than the standard action="get".
The GetItemConfig is optimized by limiting the logic done between the SQL call and the
AML result. The performance improvement is gained by limiting the features typically
available in Innovator GetItem (no server events or access checking on the sub level
Items).

Page 21

edit

This will lock, update, and unlock the Item.

create

This will act as a "get" if the Item exists, otherwise acts as an "add".

merge

This will act as an "edit" if the Item exists, otherwise acts as an "add".

lock

This will lock the Item and is the same as the Item.lockItem() method.

unlock

This will lock the Item and is the same as the Item.unlockItem() method.

4.3

Generic Methods

Generic Methods are used to perform arbitrary business logic. They can be used to
perform any logic you require and its input Item is up to you. They are called in the
IOM with the Innovator.applyMethod() method.
4.3.1 Context Item

The context Item is the this keyword Object in JavaScript, C#, and J#, and is the Me
Object in VB.Net. The XML data for the context Item is the XML submitted as the
payload for the request and it may not be valid AML just well formatted XML. It does
not matter it is the input for the Generic Method and can be whatever you want it to
be.
4.3.2 Methods are Item Factories

The Generic Method must return an Item or an Error just like "Item Action" Methods.
Often the result of the Generic Method is just some simply text or an HTML
fragment. The text can be returned using the Innovator.newResult(text) method
and if the Method needs to return an Error then use Innovator.newError(text)
method.
C#

Innovator innovator = this.newInnovator();

return innovator.newResult("This method was <b>successful</b>.");
Innovator innovator = this.newInnovator();
return innovator.newError("This method has <b>failed</b>.");

C# Example

Innovator innovator = this.newInnovator();

Item item = this.newItem("User", "get");
Item results = item.apply();
int count = results.getItemCount();
if (count<1) return innovator.newError("No users found.");
StringBuilder content = new StringBuilder();
content.append("<table>");
for (var i=0; i<count; ++i)
{
Item user = results.getItemByIndex(i);
content.append("<tr><td>Login Name:</td><td>");
content.append(user.getProperty("login_name"));
content.append("</td></tr>");
}
content.append("</table>");
return innovator.newResult(content.toString());

Page 22

4.3.3 Methodology

Typically all you need are simply name/value pairs as input for your Method and
those are just like Property tags for the Item. The body for the Generic Method is
nested inside an <Item> tag so you can pass name/value pair as arguments to the
Generic Methods just like ordinary Property tags.

The Item passed as the context Item can represent any Item you want including
fictitious Items, plus you have the added advantage of continuing using the IOM API
to operate on the context Item Object.

4.4

Server Events

Purpose of Server Event Methods is to either perform some custom actions either
before (OnBeforeXXX) or after (OnAfterXXX) a particular server action (like add,
delete, etc.) or fully replace the action processing on server (OnXXX). Detailed
information about available in Innovator server events could be found in section
4.4.3.
4.4.1 Context Item

In case of Server Event Method (see more on Server Event Methods in 4.5) the
context item is a direct analogy of a class instance (i.e. object) in OO programming
in a sense that the Method operates on its context item (as it was menthioned above
the context item could be referenced as the this keyword in JavaScript, C#, and J#,
and the Me keyword Object in VB.Net from inside the Method). In other words the
purpose of a Server Event could be defined as changing the context item, so
modified context item is the result of work done by Server Event Method. Of course,
Server Event Method doesnt necessarily have to alter its context item but rather
perform some other actions (e.g. log some info; send e-mail; etc.); this is usually
typical for Methods performed on OnAfterXXX event.
4.4.2 Methodology

A Server Event Method might return an Item only if it wants to return an error.
Otherwise Server Event Method may not have a return statement.
C#

Innovator innovator = this.newInnovator();

return innovator.newError("This method failed.");

In the case Method is called as the OnBeforeXXX event and it returns an error, the
context Item is replaced with an Error Item and is simply passed on through to the
client and no further server action is taken. In the case of an OnAfterXXX event the
server rolls back the transaction and passes the Error back on through to the client.

Its important to understand that Server Event Methods that are called on
OnBeforeXXX events operate on request AML sent from client; Server Event Methods
that are called on OnAfterXXX events operate on response AML that server is about
to send back to client and Server Event Methods that fully replace server actions
(OnXXX) get client request AML as context item and must replace it with response
AML that will be passed on through to the client. In other words, its important to
remember that Server Event Methods called on OnBeforeXXX events are invoked
before server parses the request and after the Method is done the context item must

Page 23

have a valid request AML format (it could be modified by the method but it still
should have a valid format so that server would be able to parse it). From other
side, Server Event Methods called on OnAfterXXX events are invoked after server
processed the request, and after the Method is done the context item must have a
valid response AML format (it could be modified, e.g. Method could populate it with
federated data, but it should be valid response AML, so that client would be able to
parse it.)
4.4.3 Available Server Events

The following Server Events are currently available in Innovator. Each event below
is followed by a short description and an example of common use.

OnBeforeAdd
o
o

o
OnAdd
o

OnAfterAdd methods can be used to synchronize with other items or

with external systems (e.g. add a new part number to ERP).
Runs in place of the built-in add action (via add, create or merge).
Neither OnBeforeAdd nor OnAfterAdd events are called when using
OnAdd.

An OnAdd method completely replaces the built-in add action, and

would typically be used for federated items. The method is expected
to create the appropriate records in the database and form a proper
AML response. Failure to do either is likely to result in an error.
Runs before an item is updated in the database (through the update,
edit or merge actions.)

OnBeforeUpdate methods are often used for validation purposes (often

along with OnBeforeAdd). The request may either be rejected
completely (by returning an error) or modified to conform to the
proper rules.

OnAfterUpdate
o

Runs after an item is added to the database (through the add, create
or merge actions), but before it is returned to the client.

OnBeforeUpdate
o

OnBeforeAdd methods are often used for validation purposes (e.g. to

make sure the property values do not violate a business rule). The
same method that is called OnBeforeAdd is often also called
OnBeforeUpdate, to perform the same validation.

OnAfterAdd
o

Runs before an item is added to the database (through the add, create
or merge actions.)

Runs after an item is updated in the database (through the update,

edit or merge actions), but before it is returned to the client.

Page 24

OnUpdate
o

OnGet
o

Runs after an item is deleted (through the delete or purge actions.)

OnAfterDelete methods would be used to synchronize with other items

or with external systems (e.g. remove a record from ERP.)
Runs in place of the built-in delete action. Neither OnBeforeDelete nor
OnAfterDelete events are called when using OnDelete.
An OnDelete method completely replaces the built-in delete action,
and would typically be used for federated items. The method is
expected to remove the appropriate records in the database and form
a proper response.
Runs before a search.

OnBeforeGet methods are typically used to add additional criteria to a

search, based on business rules. For example, the method might find
the default location of the user and add that location as criteria for the
query.

OnAfterGet
o

OnBeforeDelete methods are typically used to cancel a delete

operation based on a business rule.

OnBeforeGet
o

Runs before an item is deleted (through the delete or purge actions.)

OnDelete
o

An OnUpdate method completely replaces the built-in update action,

and would typically be used for federated items. The method is
expected to modify the appropriate records in the database and form a
proper AML response.

OnAfterDelete
o

Runs in place of the built-in update action (via update, edit or merge).
Neither OnBeforeUpdate nor OnAfterUpdate events are called when
using OnUpdate.

OnBeforeDelete
o

OnAfterUpdate methods can be used to synchronize with other items

or with external systems (e.g. updating a part description in ERP).

Runs after a search is executed, but before the results are returned.

OnAfterGet methods are commonly used to populate federated

properties. This might involved performing calculations on other
properties or extracting data from an external system. Once the value
of the federated property is set, it appears to the client just like any
other property.
Runs in place of the built-in get action. Neither OnBeforeGet nor
OnAfterGet events are called when using OnGet.

Page 25

OnBeforeCopy
o
o

OnAfterLock methods may be used to synchronize locks with other

items.
Runs before an item is unlocked.

An OnBeforeUnlock method may be used to prevent an item from

being unlocked based on business rules.
Runs after an item is unlocked.

OnAfterUnlock methods may be used to synchronize locks with other

items.
Runs before an item is versioned (through the version, update, edit or
merge actions.)
OnBeforeVersion methods are typically used to cancel a version
operation based on a business rule.

Runs after an item is versioned (through the version, update, edit or

merge actions.)

An OnAfterVersion method might be used to set properties of the new

item version.

OnBeforeMethod
o

Runs after an item is locked (via the lock or edit actions.)

OnAfterVersion
o

An OnBeforeLock method may be used to prevent an item from being

locked based on business rules.

OnBeforeVersion
o

Runs before an item is locked (via the lock or edit actions)

OnAfterUnlock
o

OnAfterCopy methods can be used to set properties of the new item

created by the copy.

OnBeforeUnlock
o

Runs before an item is copied (via the copy action.)

OnAfterLock
o

An OnBeforeCopy method might be used to cancel a copy operation

that violates a business rule.

OnBeforeLock
o

Runs before an item is copied (via the copy action.)

OnAfterCopy
o

An OnGet method completely replaces the built-in get action, and

would typically be used for federated items. The method is expected
to retrieve the appropriate records in the database and form a proper
AML response.

Runs before Server Action Method.

Page 26

OnAfterMethod
o

OnGetKeyedName
o
o

4.5

Runs after Server Action Method.

Runs when the system generates the keyed_name for an item.

Used to override the standard logic for generating keyed names.

Client Events

There are several Events available on the client side, which include:

Form Events
Field Events
Grid Events
Item Actions

4.5.1 Context Item

The this keyword context Object is an Item Object for Item Actions. However, the
context Object is not the Item Object for Form, Field, and Grid Events. The this
context Object is the browser document (DOM) Object for the Form and Grid Events
and is the Field Object for Field Events.
The context Item Object for Form, Grid, and Field Events is the document.thisItem
Object, which is an Item Object and should be used with the IOM API. For
relationship grid events use parent.thisItem, which is a pointer to the
document.thisItem Object.
4.5.2 Form Events

The Form Events are the HTML page events; for example, onLoad, onUnload,
onResize, onMouseDown, onMouseUp, and others (please, refer to the "Form Events"
List in Aras Innovator for the complete list of available events.)

You bind your Method to the Form Event using the Form Tool. Select the Form Event
tab and add the event relationships as shown below:

Page 27

4.5.3 Field Events

The Field Events are the HTML field events; for example, onSelect, onClick,
onChange, onBlur, onFocus, and others (please refer to the "Field Events" List in
Aras Innovator for the complete list of available events.)

You bind your Method to the Field Event using the Form Tool. Select the Field by
clicking on it in the canvas area in form Tool or from the Fields grid in the upper left
hand corner of the Form Tool. Select the Field Event tab and add the event
relationships as shown below:

Page 28

4.5.4 Grid Events

Grid Events are the events for the grid control, which is used in the Relationships tab
area for tear off Item windows. The grid events occur on the row (section 4.5.4.1)
and on the cell (section 4.5.4.2.)
Like Server Events you bind a Method as the callback for the event as the Grid Event
relationship on the RelationshipType Item, and as the Grid Event relationship on the
Property Item.
The Method gets at least three arguments: relationshipID, relatedID, gridApplet.
The relationshipID is the ID for the relationship Item for the selected row. The
relatedID is the ID for the related Item for the selected row. And the gridApplet is a
handle to the grid control object. The relatedID maybe empty if there is no related
Item for the relationship row. The relationshipID is also the ID for the grid control
row. Edit the RelationshipType Item and add Grid Events relationships as shown
below:

Page 29

4.5.4.1 Row Events

The row events include:

Event
onSelectRow
onInsertRow
onDeleteRow

Fires when the row is selected.

Fires when the row is inserted.
Fires when the row is deleted.

Comment

The Method for the event will be called with three arguments:
Argument
relationshipID

Type
String

relatedID

String

gridApplet

GridControl

Comment
The ID for the relationship Item. This is also the selected row
ID for the grid control.
The ID for the related Item. The relatedID maybe empty if
there is no related Item for the relationship row.
The handle to the grid control.

Page 30

4.5.4.2 Cell Events

Edit the Property Item and add Event relationships as shown below:

The cell events include:

Event
onEditStart
onEditFinish
onChangeCell
Default Search
onSearchDialog

Fires when the cell gets focus.

Fires when the cell loses focus.
Fires when the cell value changes.

Comment

The Method for the event will be called with five arguments:
Argument
relationshipID

Type
String

relatedID

String

gridApplet
propertyName
colNumber

GridControl
String
Integer

Page 31

4.5.5 Item Actions and Server Event

The Methods related to the ItemType via the "Item Action" relationship are called via
the action attribute and the Item.apply() method and can be reviewed by searching
the "Item Actions" Tab on the ItemType.
The Methods related to the ItemType via the "Server Event" relationship are called
by the server as pre and post event callbacks for the primitive server actions: add,
update, delete, and get. And can be reviewed by searching the "Server Events" Tab
on the ItemType.
The Generic Methods can be reviewed by searching the Method Items.

Page 32

5 Action Items
An Action Item is how Methods are bound to the client User Interface. Actions
provide the hooks for invoking Methods from the Action menu bar choice or from the
right mouse context popup menu. An Action is invoked on the client side but can call
either a client or server side Method. In both cases the context Item must be
defined.
The item_query Property on the Action Item is used to specify the query used to
populate the context Item. This Property is of data_type="text" because it is
actually an XSLT stylesheet. Simply put the item_query Action Property drives the
content for the context Item for the Action Methods.

The use of a XSLT stylesheet for the item_query is consistent with how Aras
Innovator sends out Email Notifications for Life Cycle promotions both on the State
and on the Transition, on Workflow Activities, and in the Report Tool. The concept is
the XSLT stylesheet is applied to the Item and the result is the AML query, which is
used to get the context Item for the Method. This allows you to basically turn an
Item into a query for the data you want as the context Item for the Method.
The default value for the item_query Action Property is:

<Item type="{@type}" id="{@id}" action="get" levels="0"/>

Note the use of the XSLT "Attribute Substitution" for the type and id attributes.

If you want all your old actions, created with Innovator 6.1.5 or earlier, that expect
relationships to work, use the following query string:
<Item type="{@type}" id="{@id}" action="get" levels="1"/>
The rules for how the content for the context Item are defined below for both client
and server Methods.

5.1

Client Side Method Rules

If has cache Item and is dirty then it is the context Item regardless if there is
an item_query stylesheet value.
If has cache Item and is not dirty and has item_query value then the
stylesheet is applied against the cache Item and the result is the AML query
to get the context Item for the Method.
If has cache Item and is not dirty and no item_query value then the cache
Item is the context Item for the Method.

If no cache Item and no item_query value then the temporary Item with just
the type and id attributes is the context Item for the Method.

If no cache Item and has item_query value then a temporary Item is used
containing just the Item tag with the type and id attributes. The stylesheet
for the item_query is applied to the temporary Item and the result is used as
the AML query for the content for the context Item for the Method.

Page 33

5.2

Server Side Method Rules

Currently the server side automatically gets the Item with levels="0" and
ignores any extra Property tags passed from the client request. This will need
to be changed in order to support more granular context Items and to pass in
context Item via the client request.
The Action needs to setup the Item for the server side Method request. This
can range from the dirty Item from the client cache to just the <Item> tag
with its type and id attributes plus the action attribute specifying the Method
name to run.
To achieve backward compatibility with existing server side Method logic the
context Item must be the Item from a server pre-GetItem call with
levels="0". The server will know to do this when the same format for the
AML we pass today is still passed, which is to put the ID for the Item as a
Property in the request not as an attribute:
<Item type="ItemType Name" action="Method Name">
<id>itemID</id>
</Item>

The stylesheet for the item_query value would be the following, which will
construct the AML format above:
<Item type="{@type}"><id><xsl:value-of select="@id"/></id></Item>

If no cache Item and no item_query value then the temporary Item with just
the type attribute and the id is nested as a Property tag as shown above is
passed as the request triggering the server to do the pre-GetItem levels="0"
as today and the result is the context Item for the Method.
If has cache Item and is dirty and no item_query value then passes the dirty
Item, which is the content for the context Item for the server Method.

If has item_query value but no cache Item then a temporary Item is used
containing just the Item tag with the type and id attributes. Plus the
doGetItem="1" attribute is included, which will force the server to do the preGetItem using this as its query criteria and its results is the content for the
context Item for the server side Method.
If has cache Item and is not dirty and has item_query value applies the
stylesheet to the cached Item and pass that as the Item request. Plus the
doGetItem="1" attribute is included, which will force the server to do the preGetItem using AML passed as the query criteria and the results is the content
for the context Item for the server side Method.

Page 34

5.3

Use Cases

5.3.1 Client side - has cache Item is dirty

Use Case Name:
Summary:
Preconditions:

Basic Course of
Events:

Client side has cache Item is dirty

Invokes client side Item Method and the content for the context Item is
the cached Item.
1. That an Item is selected and the type and id for the selected Item is
known by the client.
2. That the ItemType for the selected Item has an "Item Action"
RelationshipType and the Action type="item" and location="client".
1. User selected an Item.
2. Invokes the Action by context menu pick or menu bar Action menu
pick.

Exception Paths:
5.3.2 Client side - no cache Item - no item_query value
Use Case Name:
Summary:

Preconditions:

Basic Course of
Events:
Exception Paths:

Client side no cache Item no item_query value

Invokes client side Item Method and the only criteria known is the type
and id so the content for the context Item is just the Item tag with the
type and id attributes.
1. That an Item is selected and the type and id for the selected Item is
known by the client.
2. That the ItemType for the selected Item has an "Item Action"
RelationshipType and the Action type="item" and location="client".
1. User selected an Item.
2. Invokes the Action by context menu pick or menu bar Action menu
pick.
The type or id is unknown when the condition requires them to be
known.

5.3.3 Client side - has cache Item not dirty - no item_query value
Use Case Name:
Summary:
Preconditions:

Basic Course of
Events:

Client side has cache Item not dirty no item_query value

Invokes client side Item Method and the content for the context Item is
cached Item.
1. That an Item is selected and the type and id for the selected Item is
known by the client.
2. That the ItemType for the selected Item has an "Item Action"
RelationshipType and the Action type="item" and location="client".
1. User selected an Item.
2. Invokes the Action by context menu pick or menu bar Action menu
pick.

Exception Paths:

Page 35

5.3.4 Client side - has cache Item not dirty - has item_query value
Use Case Name:
Summary:

Preconditions:

Basic Course of
Events:
Exception Paths:

Client side has cache Item not dirty has item_query value
Invokes client side Item Method and the content for the context Item is
the result from a server request using the result of the XSLT
transformation of the cached Item with the item_query stylesheet as the
AML query server request.
1. That an Item is selected and the type and id for the selected Item is
known by the client.
2. That the ItemType for the selected Item has an "Item Action"
RelationshipType and the Action type="item" and location="client".
1. User selected an Item.
2. Invokes the Action by context menu pick or menu bar Action menu
pick.
The item_query is not a valid XSLT stylesheet.

5.3.5 Client side - no cache Item - has item_query value

Use Case Name:
Summary:

Preconditions:

Basic Course of
Events:
Exception Paths:

Client side no cache Item has item_query value

Invokes client side Item Method and the content for the context Item is
the result from a server request using the result of the XSLT
transformation of a temporary Item that only includes the type and id
attributes with the item_query stylesheet as the AML query server
request.
1. That an Item is selected and the type and id for the selected Item is
known by the client.
2. That the ItemType for the selected Item has an "Item Action"
RelationshipType and the Action type="item" and location="client".
1. User selected an Item.
2. Invokes the Action by context menu pick or menu bar Action menu
pick.
1. The type or id is unknown when the condition requires them to be
known.
2. The item_query is not a valid XSLT stylesheet.

5.3.6 Server side - has cache Item is dirty

Use Case Name:
Summary:
Preconditions:

Basic Course of
Events:

Server side has cache Item and is dirty

Invokes server side Item Method and the content for the context Item is
the cached Item passed as the request AML.
1. That an Item is selected and the type and id for the selected Item is
known by the client.
2. That the ItemType for the selected Item has an "Item Action"
RelationshipType and the Action type="item" and location="server".
1. User selects an Item.
2. Invokes the Action by context menu pick or menu bar Action menu
pick.

Exception Paths:

Page 36

5.3.7 Server side - no cache Item - no item_query value

Use Case Name:
Summary:

Preconditions:

Basic Course of
Events:
Exception Paths:

Server side no cache Item no item_query value

Invokes server side Item Method and the only criteria known is the type
and id. The AML request is the nested id tag style we pass today, which
tells the server to perform the pre-GetItem with levels="0" and the result
is the content for the context Item. This is the same as we currently do
today.
1. That an Item is selected and the type and id for the selected Item is
known by the client.
2. That the ItemType for the selected Item has an "Item Action"
RelationshipType and the Action type="item" and location="server".
1. User selects an Item.
2. Invokes the Action by context menu pick or menu bar Action menu
pick.
The type or id is unknown when the condition requires them to be
known.

5.3.8 Server side - has cache Item not dirty - no item_query value
Use Case Name:
Summary:

Preconditions:

Basic Course of
Events:

Server side has cache Item not dirty no item_query value

Invokes server side Item Method and the AML request is the nested id
tag style we pass today, which tells the server to perform the preGetItem with levels="0" and the result is the content for the context Item.
This is the same as we currently do today.
1. That an Item is selected and the type and id for the selected Item is
known by the client.
2. That the ItemType for the selected Item has an "Item Action"
RelationshipType and the Action type="item" and location="client".
1. User selects an Item.
2. Invokes the Action by context menu pick or menu bar Action menu
pick.

Exception Paths:

Page 37

5.3.9 Server side - has cache Item not dirty - has item_query value
Use Case Name:
Summary:

Preconditions:

Basic Course of
Events:
Exception Paths:

Server side has cache Item not dirty has item_query value
Invokes server side Item Method and the content for the context Item is
the result from a server pre-GetItem where the AML passed is the AML
query, which is the result of the XSLT transformation of the cached Item
with the item_query stylesheet; plus the doGetItem="1" attribute is also
set, which tells the server to do the pre-GetItem using the request AML
as the query, the results is the content for the context Item.
1. That an Item is selected and the type and id for the selected Item is
known by the client.
2. That the ItemType for the selected Item has an "Item Action"
RelationshipType and the Action type="item" and location="server".
1. User selects an Item.
2. Invokes the Action by context menu pick or menu bar Action menu
pick.
The item_query is not a valid XSLT stylesheet.

5.3.10 Server side - no cache Item - has item_query value

Use Case Name:
Summary:

Preconditions:

Basic Course of
Events:
Exception Paths:

Server side no cache Item has item_query value

Invokes server side Item Method and the content for the context Item is
the result from a server pre-GetItem where the AML passed is the AML
query, which is the result of the XSLT transformation of a temporary Item
that has just the Item tag with the type and id attributes with the
item_query stylesheet; plus the doGetItem="1" attribute is also set, which
tells the server to do the pre-GetItem passing its results as the content
for the context Item.
1. That an Item is selected and the type and id for the selected Item is
known by the client.
2. That the ItemType for the selected Item has an "Item Action"
RelationshipType and the Action type="item" and location="server".
1. User selected an Item.
2. Invokes the Action by context menu pick or menu bar Action menu
pick.
1. The type or id is unknown when the condition requires them to be
known.
2. The item_query is not a valid XSLT stylesheet.

Page 38

6 Aras Innovator Methodology

This section is a summary of the Aras Innovator Methodology. Following this
methodology will help you build better quality Aras Innovator business logic more
quickly; plus it will be easier to understand and maintain the code.

The AML is the language that drives the Aras Innovator Server.

The Aras Innovator Server is a message based system in that it accepts AML
scripts as messages and returns AML messages. AML document, AML script,
AML message all mean the same thing.

AML documents contain Items, Structure, and Logic, so they are scripts.

The IOM is the Object API used to build and apply AML messages.
Methods implement business logic using the IOM API.

Methods extend the Item Class when used as "Item Action" relationships on
the ItemType, which simulates Object Oriented programming, where the
ItemType is the Class and "Item Action" relationships to Methods are the
Class methods.

Methods are also generic arbitrary business logic that can be called like a sub
routines from other Methods using the IOM Innovator.applyMethod()
method.
Methods follow the Item Factories design pattern; they should return a new
Item and not side effect the context Item.

Server Events are the exception because the purpose is to intercept and
operate on the AML before the server parses it, and before the AML is
returned to the client after the server parses it. So you do modify the context
Item and return nothing.
Implement changes/edits to the context Item in the OnBefore Event by
altering the AML before the server parses it. Refrain from attempting to
update the context Item after the server has already operated on it in the
OnAfter Event. Use the OnAfter Events to update/include federated data in
the response AML.
Use the select, page, and pagesize attributes for the AML queries to
optimize the performance for the request.

Use the generic IOM methods to construct the AML queries rather then
convenience methods like getItemBy_, getRelationships(), or use the
levels attribute because the convenience methods typically return far more
data then required imposing a performance hit.

The context Item is the keyword this Object for JavaScript, C#, and J#, and
the Me Object for VB.Net.
The context Item for Generic Methods is any XML you want but it is highly
recommended that you continue to use AML to represent your data. This
provides the benefit of using the IOM to manage the input for the Generic
Methods.

Page 39

Attributes are used to pass control switches to the Method. You can invent
your own because they are a simple way to pass meta-data to the Method.

7 Cookbook
This section is a Cookbook of recipes to help you solve common tasks while
developing Methods. The examples are shown in JavaScript, C# and VB.Net when
possible.

7.1

Create an Aras Innovator Object

You need an Innovator Object perhaps to return a newResult() or newError() Item.

Technique
There are basically two ways to create a new Aras Innovator Object; by calling the
Class constructor or the factory method on the Item Object.
JavaScript

var myInnovator = new Innovator();

var myInnovator = this.newInnovator();

Innovator myInnovator = this.newInnovator();

VB.Net

Dim myInnovator As Innovator = Me.NewInnovator()

7.2

Create an Item Object

You need an Item Object perhaps to submit a query or to add an Item.

Technique
There are basically two ways to create a new Item Object; by calling the Class
constructor or the factory methods on the Item Object and Aras Innovator Object.
JavaScript
var
var
var
var
var
var

myItem = new Item();

myItem = this.newItem(myType,myAction);
myInnovator = this.newInnovator();
myItem
= myInnovator.newItem(myType,myAction);
myResult = myInnovator.newResult(resultText);
myError = myInnovator.newError(errorMessage);

Item myItem = this.newItem(myType,myAction);

Innovator myInnovator = this.newInnovator();
Item myItem
= myInnovator.newItem(myType,myAction);
Item myResult = myInnovator.newResult(resultText);
Item myError = myInnovator.newError(errorMessage);

VB.Net

Dim myItem As Item = Me.NewItem(myType,myAction)

Dim
Dim
Dim
Dim

myInnovator As Innovator = Me.NewInnovator()

myItem As Item = myInnovator.NewItem(myType,myAction)
myResult As Item = myInnovator.NewResult(resultText)
myError As Item = myInnovator.NewError(errorMessage)

Page 40

7.3

Query for an Item

You want to query for an Item that you know by id and type.

Technique
There are a few ways to get an Item when you know its id and type, the simplest
being the Innovator.getItemById() method. However, if you need to be granular about
your request then building the query using the IOM is required. This provides the
ability to include controls to limit the results and define the structure to be returned
for the Items found.
JavaScript

var qryItem = this.newItem(myType,"get");

qryItem.setID(myId);
var results = qryItem.apply();
var myInnovator = this.newInnovator();
var results = myInnovator.getItemById(myType, myId);

Item qryItem = this.newItem(myType,"get");

qryItem.setID(myId);
Item results = qryItem.apply();
Innovator myInnovator = this.newInnovator();
Item results = myInnovator.getItemById(myType, myId);

VB.Net

Dim qryItem As Item = Me.NewItem(myType,"get")

qryItem.setID(myId)
Dim results As Item = qryItem.Apply()
Dim myInnovator As Innovator = Me.NewInnovator()
Dim results As Item = myInnovator.GetItemById(myType, myId)

Page 41

7.4

Query and iterate over a set of Items

You want to query for the Items that match some criteria and generate an HTML
Table as the results.

Technique
There is no difference in setting up a query for a single Item or for many. Only the
criteria define the set size returned. In this recipe you create an Item and populate
the query criteria, apply it, and iterating over the Items returned producing a HTML
<TABLE> fragment.
JavaScript

var qryItem = this.newItem("Part","get");

qryItem.setAttribute("select","item_number,description,cost");
qryItem.setProperty("cost", "100", "gt");
var results = qryItem.apply();
var count = results.getItemCount();
var content = "<table>";
for (var i=0; i<count; ++i)
{
var item = results.getItemByIndex(i);
content += "" +
"<tr>" +
"<td>" + item.getProperty("item_number") + "</td>" +
"<td>" + item.getProperty("description") + "</td>" +
"<td>" + item.getProperty("cost") + "</td>" +
"</tr>";
}
content += "</table>";
return content;

Item qryItem = this.newItem("Part","get");

qryItem.setAttribute("select","item_number,description,cost");
qryItem.setProperty("cost", "100", "gt");
Item results = qryItem.apply();
int count = results.getItemCount();
int i;
string content = "<table>";
for (i=0; i<count; ++i)
{
Item item = results.getItemByIndex(i);
content += "" +
"<tr>" +
"<td>" + item.getProperty("item_number") + "</td>" +
"<td>" + item.getProperty("description") + "</td>" +
"<td>" + item.getProperty("cost") + "</td>" +
"</tr>";
}
content += "</table>";
Innovator innovator = this.newInnovator();
return innovator.newResult(content);

Page 42

VB.Net

Dim qryItem As Item = Me.NewItem("Part","get")

qryItem.SetAttribute("select","item_number,description,cost")
qryItem.SetProperty("cost", "100", "gt")
Dim results As Item = qryItem.Apply()
Dim count As Integer = results.GetItemCount()
Dim i As Integer
Dim content As String = "<table>"
For i=0 to count - 1
Dim item As Item = results.GetItemByIndex(i)
content += "" + _
"<tr>" + _
"<td>" + item.GetProperty("item_number") + "</td>" + _
"<td>" + item.GetProperty("description") + "</td>" + _
"<td>" + item.GetProperty("cost") + "</td>" + _
"</tr>"
Next
content += "</table>"
Dim innovator As Innovator = Me.NewInnovator()
return innovator.NewResult(content)

Page 43

7.5

Query for an Item and return its configuration

You want to query for an Item and return its configuration in the results.

Technique
To query for an Item and retrieve its structure you build the query as the structure
you want returned. Use the IOM methods to add the relationships you want and
build the structure in the Item. The server will return the structure that follows the
request structure.
This recipe illustrates several related concepts together, which are how to get a set
of Items from an Item and how to iterate over the set, plus how to get the related
Item from the relationship Item.
JavaScript

var innovator = this.newInnovator();

// Set up the query Item.
var qryItem = this.newItem("Part","get");
qryItem.setAttribute("select","item_number,description,cost");
qryItem.setID(myId);
// Add the BOM structure.
var bomItem = this.newItem("Part BOM","get");
bomItem.setAttribute("select","quantity,related_id(item_number,description,cost)");
qryItem.addRelationship(bomItem);
// Perform the query.
var results = qryItem.apply();
// Test for an error.
if (results.isError()) {
top.aras.AlertError("Item not found: " + results.getErrorDetail());
return;
}
// Get a handle to the BOM Items.
var bomItems = results.getRelationships();
var count = bomItems.getItemCount();
// Create the results content.
var content = "<table border='1'>" +
"<tr>" +
"<td>Part Number</td>" +
"<td>Description</td>" +
"<td>Cost</td>" +
"<td>Quantity</td>" +
"</tr>";
// Iterate over the BOM Items.
for (var i=0; i<count; ++i)
{
// Get a handle to the relationship Item by index.
var bom = bomItems.getItemByIndex(i);
// Get a handle to the related Item for this relationship Item.
var bomPart = bom.getRelatedItem();
content +=
"<td>"
"<td>"
"<td>"
"<td>"
"</tr>";

"<tr>" +
+ bomPart.getProperty("item_number") + "</td>" +
+ bomPart.getProperty("description") + "</td>" +
+ bomPart.getProperty("cost") + "</td>" +
+ bom.getProperty("quantity") + "</td>" +

}
return content + "</table>";

Page 44

Innovator innovator = this.newInnovator();

// Set up the query Item.
Item qryItem = this.newItem("Part","get");
qryItem.setAttribute("select","item_number,description,cost");
qryItem.setID(myId);
// Add the BOM structure.
Item bomItem = this.newItem("Part BOM","get");
bomItem.setAttribute("select","quantity, related_id(item_number,description,cost)");
qryItem.addRelationship(bomItem);
// Perform the query.
Item results = qryItem.apply();
// Test for an error.
if (results.isError()) {
return innovator.newError("Item not found: " + results.getErrorDetail());
}
// Get a handle to the BOM Items.
Item bomItems = results.getRelationships();
int count = bomItems.getItemCount();
int i;
// Create the results content.
string content = "<table border='1'>" +
"<tr>" +
"<td>Part Number</td>" +
"<td>Description</td>" +
"<td>Cost</td>" +
"<td>Quantity</td>" +
"</tr>";
// Iterate over the BOM Items.
for (i=0; i<count; ++i)
{
// Get a handle to the relationship Item by index.
Item bom = bomItems.getItemByIndex(i);
// Get a handle to the related Item for this relationship Item.
Item bomPart = bom.getRelatedItem();
content +=
"<tr>" +
"<td>"
"<td>"
"<td>"
"<td>"
"</tr>";

"" +
+
+
+
+

bomPart.getProperty("item_number") + "</td>" +
bomPart.getProperty("description") + "</td>" +
bomPart.getProperty("cost") + "</td>" +
bom.getProperty("quantity") + "</td>" +

}
content += "</table>";
return innovator.newResult(content);

Page 45

VB.Net

Dim innovator As Innovator = Me.newInnovator()

' Set up the query Item.
Dim qryItem As Item = Me.newItem("Part","get")
qryItem.setAttribute("select","item_number,description,cost")
qryItem.setID(myId)
' Add the BOM structure.
Dim bomItem As Item = Me.newItem("Part BOM","get")
bomItem.setAttribute("select","quantity,related_id(item_number,description,cost)")
qryItem.addRelationship(bomItem)
' Perform the query.
Dim results As Item = qryItem.apply()
' Test for an error.
If results.isError() Then
Return innovator.newError(results.getErrorDetail())
End If
' Get a handle to the BOM Items.
Dim bomItems As Item = results.getRelationships()
Dim count As Integer = bomItems.getItemCount()
Dim i As Integer
' Create the results content.
Dim content As String = "<table border='1'>" + _
"<tr>" + _
"<td>Part Number</td>" + _
"<td>Description</td>" + _
"<td>Cost</td>" + _
"<td>Quantity</td>" + _
"</tr>"
' Iterate over the BOM Items
For i = 0 To count - 1
' Get a handle to the relationship Item by index.
Dim bom As Item = bomItems.getItemByIndex(i)
' Get a handle to the related Item for this relationship Item.
Dim bomPart As Item = bom.getRelatedItem()
content += _
"<tr>" + _
"<td>" + bomPart.getProperty("item_number") + "</td>" + _
"<td>" + bomPart.getProperty("description") + "</td>" + _
"<td>" + bomPart.getProperty("cost") + "</td>" + _
"<td>" + bom.getProperty("quantity") + "</td>" + _
"</tr>"
Next
content += "</table>"
Return innovator.newResult(content)

Page 46

7.6

Query using AML to construct the query

You want to perform a query using the AML to construct the query criteria.

Technique
Create an Item Object but use the Item.loadAML() method to populate the Item.
JavaScript

var innovator = new Innovator();

var qryItem = innovator.newItem();
qryItem.loadAML(
"<Item type='Part' action='get' select='item_number,description,cost'>" +
"<item_number condition='like'>1%</item_number>" +
"<Relationships>" +
"<Item type='Part BOM' action='get' select='quantity'>" +
"<quantity condition='gt'>1</quantity>" +
"</Item>" +
"</Relationships>" +
"</Item>"
);
var resultItem = qryItem.apply();
if (resultItem.isError()) {
top.aras.AlertError("Item not found: " + resultItem.getErrorDetail());
return;
}
var count = resultItem.getItemCount();
for (i=0; i<count; ++i) {
var item = resultItem.getItemByIndex(i);
}

7.7

Query for the Item next promotion states

You want to get the next promotion states for an Item and use the states as the
choices for a dropdown control.

Technique
Use the Item.getNextStates() method to get the next state values. This recipe
assumes there is a select input field on the form for us to populate with state values.
HTML

JavaScript

var results = document.thisItem.getNextStates();

var nextStates = results.getItemsByXPath('//Item[@type="Life Cycle State"]');
var count = nextStates.getItemCount();
var oSelect = document.getElementById('mySelect');
for (var i=0; i<count; ++i) {
var item = nextStates.getItemByIndex(i);
var opt = document.createElement('option');
opt.text = item.getProperty('name');
oSelect.add(opt);
}

Page 47

7.8

Query using relationships as search criteria

You want to search for an Item using the relationship and related Items as search
criteria. In this recipe we will get the User Item that matches the Identity name as
an Alias relationship to the User Item.
Technique
The following are some key points to understand when constructing an AML query:
1. Use the get action on the relationship Items to include it as search criteria.
a. Without the get action the relationship Item is ignored as search
criteria.

b. The relationship Items are also returned. Currently there is no way to

use relationships as search criteria and not return them in the results,
as you can with the related Item described below.

2. Include the related_id property name in the select attribute for the
relationship Item if you want to return the related Item nested inside the
related_id property in the results.
<Item type="Part BOM" select="quantity,related_id"/>

a. Use () to include the select attribute value for the related Item inside
the select attribute for the relationship Item.
<Item type="Part BOM" select="quantity,related_id(item_number,description)"/>

3. The select attribute for the nested Item tag for the related_id property has
higher precedence over the select value inside the () for the relationship's
select attribute.
4. The get action is not required for the nested Item tag for the related_id
property to include it as search criteria.

These two AML scripts are equivalent queries for selecting the name property
for the related Item:
<Item type="User" action="get" select="first_name,last_name,email">
<Relationships>
<Item type="alias" action="get" select="related_id(name)"/>
</Relationships>
</Item>
<Item type="User" action="get" select="first_name,last_name,email">
<Relationships>
<Item type="alias" action="get" select="related_id">
<related_id>
<Item type="Identity" action="get" select="name"/>
</related_id>
</Item>
</Relationships>
</Item>

Clearly the first example is simpler and requires less coding (referring to the
IOM logic that would construct the AML) and is the recommended style when
all you require is specifying a select for the related Item for the query.
But the second style opens the opportunity to now include additional search
criteria for the related Item.

Page 48

AML

<Item type="User" action="get" select="first_name,last_name,email">

<Relationships>
<Item type="Alias" action="get" select="related_id">
<!-1. This get will limit root Items to only those that match the relationship criteria.
2. The get action is required otherwise the criteria are ignored.
3. To include the nested Item tag for the related_id include the property name in the
select attribute for the relationship Item.
a. Can include the select attribute value for the related Item inside ()
i.e. related_id(name)
-->
<related_id>
<Item type="Identity" action="get" select="keyed_name">
<!-1. This get has no effect and the search will work with or without it.
2. It is recommended that you include it because the AML parser may be stricter in
the future.
3. The select attribute over rules the parent relationships select.
-->
<name>Larry Bird</name>
</Item>
</related_id>
</Item>
</Relationships>
</Item>

JavaScript

var innovator = new Innovator();

var qry = innovator.newItem("User","get");
qry.setAttribute("select","first_name,last_name,email");
var alias = new Item("Alias","get");
alias.setAttribute("select","related_id");
var identity = new Item("Identity","get");
identity.setAttribute("select","name");
identity.setProperty("name", "Larry Bird");
alias.setRelatedItem(identity);
qry.addRelationship(alias) ;
var results = qry.apply();
if (results.isError()) {
top.aras.AlertError(results.getErrorDetail());
return;
}

Page 49

7.9

Add an Item configuration in one transaction

You want to add an Item configuration like a BOM as one transaction.

Technique
Adding an Item configuration is done by building the Item structure using the IOM
methods.
JavaScript

var innovator = new Innovator();

var partItem = innovator.newItem("Part","add");
partItem.setAttribute("leaveLocked","0");
partItem.setProperty("item_number", "123-456");
partItem.setProperty("description", "Blah blah");
var bomItem = new Item("Part BOM","add");
bomItem.setProperty("quantity", "10");
var relatedItem = new Item("Part","get");
relatedItem.setProperty("item_number", "555-555");
bomItem.setRelatedItem(relatedItem);
partItem.addRelationship(bomItem) ;
var resultItem = partItem.apply();
if (resultItem.isError()) {
top.aras.AlertError(resultItem.getErrorDetail());
return;
}

Technique
The following is the same thing but will use the Item.loadAML() method to populate
the Item Object with AML text.
JavaScript

var innovator = new Innovator();

var partItem = innovator.newItem();
partItem.loadAML(
"<Item type='Part' action='add' leaveLocked='0'>" +
"<item_number>123-456</item_number>" +
"<description>Blah blah</description>" +
"<Relationships>" +
"<Item type='Part BOM' action='add'>" +
"<quantity>10</quantity>" +
"<related_id>" +
"<Item type='Part' action='get'>" +
"<item_number>555-555</item_number>" +
"</Item>" +
"</related_id>" +
"</Item>" +
"</Relationships>" +
"</Item>"
);
var resultItem = partItem.apply();
if (resultItem.isError()) {
top.aras.AlertError (resultItem.getErrorDetail());
return;
}

Page 50

7.10 Add a Named Permission

You want to add a new named Permission Item.

Technique
Use the Item Class Extended Method set to add a new Named Permission Item.
JavaScript

var innovator = new Innovator();

var permItem = innovator.newItem("Permission","add");
permItem.setAttribute("leaveLocked","0");
permItem.setProperty("name", "Part Permissions");
permItem.setIdentityAccess("All Employees", "get", true);
permItem.setIdentityAccess("CM", "get", true);
permItem.setIdentityAccess("CM", "update", true);
permItem.setIdentityAccess("CM", "delete", true);
resultItem = permItem.apply();
if (resultItem.isError()) {
top.aras.AlertError(resultItem.getErrorDetail());
return;
}

7.11 Set a Private Permission for an Item

You want to set a new private Permission for an Item.

Technique
Use the Item Class Extended Method set to set a new private Permission for an Item.
JavaScript

// Set up the Part query

Page 51

7.12 Apply a Generic Method

You want to write Generic Methods that can be used as subroutines for other
Methods.

Technique
Use the Innovator.applyMethod() method to apply Generic Methods. The following
examples assume a server-side method named "Reverse String" exists, and that it
returns a result item containing the reversed contents of the <string> tag.
JavaScript

var inn = this.newInnovator();

var results = inn.applyMethod("Reverse String", "<string>abc</string>");
// You can also apply a generic client method but only from another client-side method
// var results = inn.applyMethod("Reverse String JS","<string>abc</string>","client");
return results.getResult(); // returns "cba"

Innovator inn = this.newInnovator();

Item results = inn.applyMethod("Reverse String", "<string>abc</string>");
// Return a result item with "cba" as the contents of the Result tag
return inn.newResult(results.getResult());

VB.Net

Dim inn As Innovator = Me.newInnovator()

Dim results As Item = inn.applyMethod("Reverse String", "<string>abc</string>")
' Return a result item With "cba" As the contents of the Result tag
Return inn.newResult(results.getResult())

7.13 Need a missing Namespace

You need to use a namespace that is missing from your Method.

Technique
Edit the method-config.xml file located in the Server folder for the Aras Innovator
install. Search for the <Template> tag for the language you are using and include any
additional namespaces you need by adding additional "using" lines.
<Template name="CSharp" line_number_offset="19">
using System.Text;
// Now you can use the System.Text.UTF8Encoding method in your Method.
byte[] info = new UTF8Encoding(true).GetBytes(this.dom.InnerXml);

Page 52

7.14 Need to Save text to a File

You want to save text to a file.

Technique
On the client side use the vault control to write to a text file.
JavaScript

with (top.aras.vault)
{
fileCreate(filePath);
fileOpenAppend(filePath);
fileWriteLine('<AML><Item type="MyItemType"/></AML>');
fileClose();
}

Technique
On the server side use the File and StreamWriter namespaces to write to a text file.
C#

Innovator myInnovator = this.newInnovator();

// Save the results to a file.
string path = myInnovator.MapPath("temp/yoyo.txt");
try
{
if (File.Exists(path)) File.Delete(path);
StreamWriter sw = File.CreateText(path);
sw.Write(this.dom.InnerXml);
sw.Close();
}
catch (Exception e)
{
return myInnovator.newError(e.Message);
}
return myInnovator.newResult("ok");

Page 53

7.15 Need to Send Email from a Method

You want to send an Email message from a server side Method.

Technique
Use the CCO.Email object to send email messages.
C#

System.Web.Mail.MailMessage email = new System.Web.Mail.MailMessage();

email.From = fromEmail;
email.To = toEmail;
email.Subject = subject;
email.Body = body;
CCO.Email.setup_smtpmail_server_and_send(email);
// Alternatively use the SendEmailToIdentity
// The first argument is the Identity name to send the email message.
// The second argument is the subject text.
// The third argument is the email body text.
// The last argument is a user login name as the sender and
//
if blank will use the logged in user name and
//
that User Item must have an email address as well.
CCO.Email.SendEmailToIdentity(ref identity, ref subject, ref body, ref user);
return this.newInnovator().newResult("ok");

VB.Net

Dim email = New System.Web.Mail.MailMessage()

email.From = fromEmail
email.To = toEmail
email.Subject = subject
email.Body = body
CCO.Email.setup_smtpmail_server_and_send(email)
' Alternatively use the SendEmailToIdentity
' The first argument Is the Identity name To send the email message.
' The second argument Is the subject text.
' The third argument Is the email body text.
' The last argument Is a user login name As the sender And
'
If blank will use the logged In user name And
'
that User Item must have an email address As well.
CCO.Email.SendEmailToIdentity(identity,subject,body,user)

Page 54

7.16 Need to Add a C# Control

You want to add one of new C# controls to a web page.

Technique
In HTML code use the assembly name, the control name (e.g. TreeTable and
GridContainer respectively in the code sample below), the special <object> tag and
appropriate control event handlers to download/activate control on the page. Make
sure that all the event handlers for the control are placed in HTML code above the
<object> tag:

HTML Code
- for a separate web page, the special function, named WriteUncommentedObject in
the code sample below, gives the work around for Security Update MS06013(912812):
<html>
<head>
<script type="text/javascript"
src="../javascript/AddConfigurationLink.js">TreeTable</script>
</head>
<body>
<script type="text/javascript" for="MyGrid" event="GridClick(rowId, col)">
alert("rowId:" + rowId + ", col:" + col);
</script>
<script type="text/javascript" for="MyGrid" event="GridStart(isSuccess)">
if (isSuccess) {
addRow("row1","Row 1","row1");
addRow("row2","Row 2","row2");
}
</script>
<comment id="MyGrid_commented">
<object id="MyGrid"
style="width:100px; height:100px; visibility:visible;"
classid="../cbin/TreeTable.dll#Aras.Client.Controls.GridContainer">
</object>
</comment>
<script type="text/javascript">
WriteUncommentedObject("MyGrid_commented");
</script>
</body>
</html>

- for a field on an Aras Innovator form, the form internally takes care of work around
for MS06-013(912812):
<script type="text/javascript">
top.aras.uiAddConfigLink2Doc4Assembly(document, "TreeTable");
</script>
<script type="text/javascript" for="MyGrid" event="GridStart(isSuccess)">
if (isSuccess) {
addRow("row1","Row 1","row1");
addRow("row2","Row 2","row2");
}
</script>
<script type="text/javascript" for="MyGrid" event="GridClick(rowId, col)">
alert("rowId:" + rowId + ", col:" + col);
</script>
<object id="MyGrid"
style="width:100px; height:100px;"
classid="../cbin/TreeTable.dll#Aras.Client.Controls.GridContainer">
</object>

Page 55

7.17 Need for Speed ApplySQL

You want to query the DB directly bypassing Innovator logic to get the data faster.

Technique
Use the Innovator.applySQL() method to submit SQL direct to the database. This
recipe returns the XML from the applySQL() method and forms HTML for a table to
display the data.
C#

Innovator myInnovator = this.newInnovator();

Item results = myInnovator.applySQL(
"select login_name,first_name,last_name,email " +
"from [user] " +
"order by last_name,first_name");
string content = "" +
"<style type='text/css'>" +
"table {background:#000000;}" +
"th {font:bold 10pt Verdana; background:#0000FF; color:#FFFFFF;}" +
"td {font:normal 10pt Verdana; background:#FFFFFF;}" +
"caption {font:bold 14pt Verdana; text-align:left;}" +
"</style>" +
"<table id='tbl' border='0' cellspacing='1' cellpadding='2' datasrc='#itemData'>" +
"<caption>User Directory</caption>" +
"<thead>" +
"<tr>" +
"<th>Login Name</th>" +
"<th>First Name</th>" +
"<th>Last Name</th>" +
"<th>EMail</th>" +
"</tr>" +
"</thead>" +
"<tbody>";
XmlNodeList users = results.dom.SelectNodes("//recordset/row");
for (int i=0; i<users.Count; i++) {
content += "<tr><td>" + ((users[i].SelectSingleNode("login_name") != null) ?
users[i].SelectSingleNode("login_name").InnerText : "") + "</td>";
content += "<td>" + ((users[i].SelectSingleNode("first_name") != null) ?
users[i].SelectSingleNode("first_name").InnerText : "") + "</td>";
content += "<td>" + ((users[i].SelectSingleNode("last_name") != null) ?
users[i].SelectSingleNode("last_name").InnerText : "") + "</td>";
content += "<td>" + ((users[i].SelectSingleNode("email") != null) ?
users[i].SelectSingleNode("email").InnerText : "") + "</td></tr>";
}
content += "" +
"</tbody>" +
"</table>";
return myInnovator.newResult(content);

Page 56

7.18 Need a callback for a Relationships Grid Row Event

You want to call a client side Method when the Relationships Grid row is selected to
deselect the row if it is not a new relationship row.
Technique
Add the Grid Event relationship to a Method as the callback for the OnSelectRow
event.

The Method gets three arguments: relationshipID, relatedID and gridApplet. The
relationshipID is the ID for the relationship Item for the selected row. The relatedID
is the ID for the related Item for the selected row. The gridApplet is a handle to the
grid control object.
The relationshipID is also the ID for the grid control row. This recipe will call the
gridApplet Deselect() method if the relationship Item for the selected row if the
relationship has not been modified.
JavaScript

// The row ID is the same as the relationship ID

Page 57

7.19 Need a callback for a Relationships Grid Cell Event

You want to call a client side Method when the Relationships Grid cell is selected to
blur the cell and prevent editing the cell value.
Technique
Add the Event relationship to a Property as the callback for the OnEditCell event.

The Method gets five arguments: relationshipID, relatedID, propertyName,

colNumber, gridApplet
The propertyName is the name of the Property for the cell column selected, and
colNumber is the column position number in the grid.
Simple return false and this will blur the grid cell.
JavaScript

// Get the current value of the cell

var cellValue = gridApplet.GetCellValue(relationshipID,colNumber);
// If the cell already has a value, disallow editing
if (cellValue !== "") {
return false;
}

Page 58

7.20 Show relationships in a Grid control on the Form

You want to show the relationships for the context Item in a Grid control on the Item
Form.

Technique
Add an HTML Field (positioned at Point(300,10) in the code sample below) and insert
an HTML code than defines the <object>tag to hold the dynamically populated grid
and the JavaScript to get the populating grid relationships.
HTML Field code

Page 59

var inn = item.newInnovator();

var gridDom = inn.newXMLDocument();
gridDom.loadXML(gridXml);
var tableNd = gridDom.selectSingleNode("/table");
var c = results.getItemCount();
for (var i=0; i<c; ++i) {
var bom = results.getItemByIndex(i);
var part = bom.getRelatedItem();
var trNd = gridDom.createElement("tr");
trNd.setAttribute("id", bom.getID());
var tdNd;
for (var j=0; j<propNameArr.length; j++) {
tdNd = gridDom.createElement("td");
tdNd.text = part.getProperty(propNameArr[j]);
trNd.appendChild(tdNd);
}
tdNd = gridDom.createElement("td");
tdNd.text = bom.getProperty("quantity");
trNd.appendChild(tdNd);
tableNd.appendChild(trNd);
}
document.MyGrid.InitXml(gridDom.xml);
}
window.attachEvent("onload", MyOnloadHandler);
</script>

7.21 Show relationships in an Excel component on the Form

You want to show the relationships for the context Item in an Excel web component
on the Item Form.
Technique
Using the Form Tool we add an HTML Field to the Form, which we will use to insert
the HTML and JavaScript code for displaying the Excel web component for the "Part
BOM" relationships for the document.thisItem context Part Item.

Add an HTML Field and insert the following code, which defines an <object> tag to
hold the dynamically populated Excel document plus the JavaScript code to get the
relationships to populate the control. Please note that the use of Excel components
is heavily dependent on the client security settings, and may not work in all
environments. The form internally handles the workaround for MS06-013(912812).
HTML Field code

<object classid="clsid:0002E559-0000-0000-C000-000000000046" id="excel">
<param name="DisplayTitleBar" value="false">
<b>Unable to open Excel</b>
</object>
<script language="JavaScript">
function MyOnloadHandler() {
// Make sure the context item and Excel are loaded
if (!document.thisItem || !document.getElementById("excel")) { return; }

Page 60

var item = document.thisItem;

// Get the relationships using the context item ID as the source_id for the query.
var qry = item.newItem('Part BOM','get');
qry.setAttribute('select','quantity,related_id(item_number,name,cost)');
qry.setProperty('source_id', item.getID());
top.results = qry.apply();
// Populate the excel control with the results.
populateExcel(item, top.results, document.getElementById("excel"), 1);
}
function populateExcel(item, results, sheet, row)
sheet.Cells(row,1).Value = "Part Number";
sheet.Cells(row,2).Value = "Name";
sheet.Cells(row,3).Value = "Cost";
sheet.Cells(row++,4).Value = "Quantity";

var c = results.getItemCount();
for (var i=0; i<c; ++i) {
var bom = results.getItemByIndex(i);
var part = bom.getRelatedItem();
sheet.Cells(i+row,1).Value = part.getProperty('item_number');
sheet.Cells(i+row,2).Value = part.getProperty('name');
sheet.Cells(i+row,3).Value = part.getProperty('cost');
sheet.Cells(i+row,4).Value = bom.getProperty('quantity');
sheet.Range("A1:D1").EntireColumn.AutoFit();
}
}
window.attachEvent("onload", MyOnloadHandler);
</script>

7.22 Open the relationships in an Excel Document

You want to open the relationships for the context Item in an Excel document outside
the Form.
Technique
Using the Form Tool we add an HTML Field to the Form, which we will use to insert
the HTML and JavaScript code for displaying the Excel document for the "My BOM"
relationships for the document.thisItem context Part Item.

Add a HTML Field and insert the following code, which defines a <button> tag to call
the JavaScript code to get the relationships to populate the control. Please note that
the use of Excel automation is heavily dependent on the client security settings, and
may not work in all environments.
HTML Field code

<button onclick="openExcel()">Open Excel Document</button>

Page 61

var workbook = excel.Workbooks.Add();

var sheet = workbook.ActiveSheet;
// Add the context Item to the Excel sheet.
sheet.Cells(1,1).Value = "Part Number";
sheet.Cells(2,1).Value = "Description";
sheet.Cells(3,1).Value = "Cost";
sheet.Cells(1,2).Value = item.getProperty('item_number');
sheet.Cells(2,2).Value = item.getProperty('name');
sheet.Cells(3,2).Value = item.getProperty('cost');
populateExcel(item, top.results, sheet, 5);
}
function populateExcel(item, results, sheet, row) {
sheet.Cells(row,1).Value = "Part Number";
sheet.Cells(row,2).Value = "Description";
sheet.Cells(row,3).Value = "Cost";
sheet.Cells(row++,4).Value = "Quantity";
var c = results.getItemCount();
for (var i=0; i<c; ++i) {
var bom = results.getItemByIndex(i);
var part = bom.getRelatedItem();
sheet.Cells(i+row,1).Value = part.getProperty('item_number');
sheet.Cells(i+row,2).Value = part.getProperty('name');
sheet.Cells(i+row,3).Value = part.getProperty('cost');
sheet.Cells(i+row,4).Value = bom.getProperty('quantity');
}
sheet.Range("A1:D1").EntireColumn.AutoFit();
}
window.attachEvent("onload", MyOnloadHandler);
</script>

7.23 Page Fields on the Form using Tabbar

You want to use a Tabbar control on the Form to page the various relationships for
the context Item as shown on the figure below:

Technique

Page 62

Use a Tabbar control to page between Grid styles. The code sample below shows the
HTML and JavaScript for the tabbar control only. Reuse technique illustrated in 7.17
to implement Grids the tabbar is paging.
HTML code

Page 63

7.24 Want the Identities for the User

You want to get the Identity ID's for the User.

Technique
Use the classic Aras Innovator API top.aras.getIdentityList() method, which
returns a comma delimited string of ID's.

Note that the classic API will eventually be eliminated and this method will become
available on the IOM Innovator object as Innovator.getIdentityList().
JavaScript

// This will get an array of identity IDs from the client cache
var myIdentityIDs = top.aras.getIdentityList().split(',');

// This will requery the server for the same list (for use when it's changed in-session)
// var myIdentityIDs = top.aras.buildIdentityList().split(',');

7.25 Want a field to be either a sequence or user entered value

You want to enable a field on the form to be a sequence value or allow the user to
enter a value.

Technique
Use the classic Aras Innovator API top.aras.getNetSequence() method, which returns a
the next sequence value from the server.
Note that the classic API will eventually be eliminated and this method will become
available on the IOM Innovator object as Innovator.getNetSequence().
Using the Form Tool we add an HTML Field to the Form, which we will use to insert
the HTML and JavaScript code for to provide the button to get the next sequence
value and update the Field value and client cache.
HTML Field code

<a href="javascript:getNextNumber();">
<img src="../images/icons/16x16/16x16_sequence.gif" border="0">
</a>
<script>
function getNextNumber() {
// Get a handle to the field object.
// The ID for the field is the property name with _system suffix.
var field = document.getElementById("item_number_system");
// Get the next sequence value.
var seq = top.aras.getNextSequence("","Default Part");
field.value = seq;
// This will update the client cache with the new value.
handleItemChange("item_number", field.value);
}
</script>

Page 64

7.26 Want to Vault a File

You want to save a Document with an attached File

Technique
Use the IOM newItem() and setFileName() methods to create an Item of type File and
set up the request to be submitted to the Vault Server.
JavaScript

// Create the Document item

var docItem = this.newItem("Document","add");
docItem.setProperty("item_number","123");
// Create the File item and set the path to the file.
var fileItem = this.newItem("File","add");
fileItem.setFileName("C:\\My Document.doc");
// Create the relationship between the Document and File
var relItem = this.newItem("Document File","add");
docItem.addRelationship(relItem);
relItem.setRelatedItem(fileItem);
var results = docItem.apply();
if (results.isError()) {
top.aras.AlertError(results.getErrorDetail());
} else {
// Show the new Document
top.aras.uiShowItemEx(results.getItemByIndex(0).node, 'tab view', true);
}

7.27 Want to get an existing Vaulted File and save it with a

new Document

You want to get an existing File from the Vault and attach it to a new Document
Technique
This is similar to the last recipe but will use the getItemByKeyedName() method to get an
existing File Item instead of creating a new one.
JavaScript

// Create the Document item

Page 65

7.28 Want to open a Vaulted File in Word

You want to open an existing File from the Vault in Word.

Technique
We will first download the file from the vault to our local drive and then open the file
in Word. The following code can be placed in a client side Method and called via a
generic Action with target='none' so that only the Word window is actually opened.
JavaScript

// Prompt the user for the file name and retrieve the File item
var fileName = prompt("Enter the File Name:","");
var innovator = this.newInnovator();
var fileItem = innovator.getItemByKeyedName("File",fileName);
if (fileItem.isError()) {
top.aras.AlertError("File Not Found: " +fileItem.getErrorDetail());
return;
}
// Get the URL to the file and download it
var fileURL = top.aras.getFileURLEx(fileItem.node);
var folder = top.aras.vault.GetWorkingDir();
var results = top.aras.vault.downloadFile(fileURL);
if (!results) {
top.aras.AlertError("Unable to retrieve the file from the vault");
return;
}
// Open the file in Word.
try {
var word = new ActiveXObject("Word.Application");
word.visible = true;
word.documents.open(folder + "\\" + fileName);
} catch(e) {
top.aras.AlertError("Unable to launch Word. File saved as: "+folder+fileName);
return;
}

Page 66

7.29 Need to reject an Item Promote

You want to reject an Item Promote if a value of Property is in valid.

Technique
Use the Pre Server Method on the Life Cycle Transition to call a server side Method to
validate the Item before it is promoted and if invalid rejects the Promote by
returning an Error Item.

Innovator innovator = this.newInnovator();

if (Convert.ToDecimal(this.getProperty("cost")) > 500) {
Item error = innovator.newError("Error promoting: Item costs more than $500.00");
return error;
}
return this;

VB.Net

Dim innovator As Innovator = Me.newInnovator()

If (CDec(Me.getProperty("cost")) > 500) Then
Dim Err As Item = innovator.newError("Error promoting: Item costs more than $500.00")
Return Err
End If

Page 67

7.30 How to build XML for a Grid

The XML document for a grid may contain the following tags:
<table> Tag

The <table> tag has the following attributes.

Attribute
icon0

Type
String

icon1
icon2
icon3
iconchk0

String
String
String
String

IconCheckBox0

iconchk1

String

IconCheckBox1

sort_up

String

IconSortUp

sort_down

String

IconSortDown

sel_bgcolor

String

SelBGColor

sel_textcolor

String

SelTextColor

font
draw_grid

String
Boolean

Font
DrawGrid

nosort
editable
norowselect
multiselect

Boolean
Boolean
Boolean
Boolean

NoSort
Editable
NoRowSelect

column_draggable

Boolean

ColumnDraggable

noheader
hide_on_load

Boolean
Boolean

NoHeader
HideOnLoad

input_row

Boolean

InputRow

column_resizable
fixedcols

Boolean
Integer

ColumnResizable
ColumnFixed

enterastab

Boolean

EnterAsTab

thinborder

Boolean

ThinBorder

bginvert

Boolean

BGInvert

justify
headerflat
fillheaderspace

Boolean
Boolean
Boolean

Justify
HeaderFlat
HideHeaderSpace

zebra

Boolean

Zebra

sortoninsert

Boolean

SortOnInsert

Property

Comments
Image for root nodes. The icon0 icon3 can be used
with the IM0 and IM1 parameters.
Image for terminal nodes.
Image for non-terminal opened nodes.
Image for non-terminal closed nodes.
Specifies the name of the image for checkbox state 0
(unchecked). For TreeGrid only.
Specifies the name of the image for checkbox state 1
(checked). For TreeGrid only.
Specify the images to display in header cells to show
sort direction.
Specify the images to display in header cells to show
sort direction.
Set the background for the row when selected. This
color will be ORed with each cell background color.
Set the text color for the row. This color will be Ored
with each cell text color. So #FFFFFF will make black
text be white when selected, and blue one is yellow.
The default text font.
Draw vertical and horizontal grid lines. Default is
true.
Makes grid non sortable. Default is false.
Makes cells of the grid editable. Default is false.
Disable row selection when clicked. Default is false.
Enable multi-select (with ctrl-key down). Default is
false.
Enable column dragging. Column index is not
changed, only visual feature. Default is false.
Hide the header if value = 1. Default is 0 (false).
Disables the initial paint and the control will not
appear until you call showContent() method. Default
is false.
Enables an input row not-scrollable above the
header.
Enable column resizing. Default is true.
Fix the first n columns, so they do not scroll. Must be
> 0.
If specified (true), enter key will work as tab move
to the next column, otherwise (false) move to the
next row same column. Default is true.
If true, cells have thin border, false has visible
white border. Default is false.
Enable background row color inverting when
selected. Default is true.
Enables cell content wrapping. Default is false.
Set the header with flat border. Default is false.
If specified, the free space on the right of the grid
will be filled with bgcolor rather than header color.
Default is true.
Define 2 colors (comma separated), that will
alternate between rows. Default is false.
Enables resorting as rows are inserted. Default is
false.

Page 68

enablehtml
delim

Boolean
String

EnableHTML
Delimeter

Default is true.
Set the delimiter character.

<menu> Tag

The <menu> tag has no attributes. Contains <menuitem> and <separator> tags.

<menuitem> Tag

The <menuitem> tag defines an item on the menu.

Attribute
label

Type
String

The menu item label.

Comments

<separator> Tag

The <separator> tag has no attributes.

<thead> Tag

The <thread> tag defines the header.

Attribute
height

Type
String

Height in pixels.

Comments

<th> Tag

The same as <td> tag. See below.

<columns> Tag

The <columns> tag has no attributes. Contains <column> tags

<column> Tag

Type
Integer
String
Integer
String
Boolean
Boolean
Boolean
String
String
String
Boolean

Comments
Width in pixels.
Text alignment.
The column order.
NOEDIT|FIELD:maxlen|COMBO:listId|WIDGET:class
Invert background color of selected cell from this column.
Column is resizable.
Column is visible.
NOSORT|NUMERIC|DATE
Display cell value as * in UI. To protect data.

<inputrow> Tag

The <inputrow> tag defines the input row, has no attributes, and contains <td>
tags.

<tr> Tag

The <tr> tag defines a row. Contains <td>, <tr>, and <userdata> tags.

Attribute
id
action

Type
String
String

Comments
Row ID.
Parameters to pass into GridClick event handler.

Page 69

bold
selected
height
icon0
icon1
expanded

Boolean
Boolean
Integer
String
String
Boolean

Height in pixels.
Open icon. For TreeGrid only.
Close icon. For TreeGrid only.
Display node as expanded on initial load.

<td> Tag

Type
String
String
String
String
String
Boolean
Boolean

<userdata> Tag

The

Attribute
key
value

Type
String
String

Font.
Set the foreground color.
Set the background color.

Comments

Text alignment.

tag defines user data for the row.

Key for the value.
The value.

Comments

<list> Tag

The <list> tag defines a list and contains <listitem> tags.

Attribute
id

Type
String

The ID for the list.

Comments

<listitem> Tag

The <listitem> tag defines the item for the list.

Attribute
label
value

Type
String
String

The label for the list item.

The value for the list item.

Comments

Page 70

7.31 How to build XML for a Menu

The XML document for a menu may contain the following tags:
<menuapplet> Tag

The <menuapplet> tag contains <menubar> tags.

Attribute
show

Type
String

bgcolor
fgcolor
top_border
bottom_border
left_border
right_border

String
String
Boolean
Boolean
Boolean
Boolean

Comments
The identifier of visible toolbar. If this parameter is absent, first menubar
from list will be visible.
0
0
0
0

or
or
or
or

1.
1.
1.
1.

<menubar> Tag

The <menubar> tag contains <item>, <checkitem>, and <separator> tags.

Attribute
id

Type
String

Comments

<item> Tag

The <item> tag defines a menu item.

<checkitem> Tag

The <checkitem> tag defines a toggle button menu item.

<seperator> Tag

The <seperator> tag defines a separator for the menu.

Page 71

8 .NET Controls
There are number of .NET controls that are used by the Aras Innovator Client, which
can be programmatically controlled from the client side Methods. Plus you can use
these controls when constructing your own user interfaces.
Within an HTML page, each control may be initialized by tag <OBJECT> with the
attribute classID that has two parts: the path to the .Net assembly, and the fully
qualified class name of the control, separated by the pound sign:
classid="../cbin/[assembly_name]#Aras.Client.Controls.[class_name]"

The .NET controls described in this section are listed in the table below:
Control

assembly_name

class_name

TREE GRID

TreeTable.dll

TreeGridContainer

GRID

EXCEL GRID
MENU BAR

WORKFLOW
TOOLBAR

STRUCTURE
GANTT

STATUS BAR

UTILITY CONTROL
TABBAR

CALENDAR
VAULT

COLOR DIALOG

TreeTable.dll
TreeTable.dll

MainMenu.dll
Workflow.dll
Toolbar.dll

Structure.dll
Gantt.dll

StatusBar.dll
Utils.dll

SimpleTabbar.dll
Calendar.dll
Vault.dll

ColorDialog.dll

GridContainer
ExcelGrid

MainMenu

WorkflowContainer
Toolbar

Structure

ProjectTree
StatusBar
Utils

SimpleTabbar
Calendar

VaultApplet
ColorDialog

These controls expose public methods and properties via members of COM interfaces
that in their turn return COM interfaces and get COM interfaces as parameters. This
section provides just a generic characteristic of the controls. You can get a detailed
API reference of the controls by one of the following means:
- On-line. Go to
http://www.aras.com/support/documentation/documentation.aspx?version=8.1.1
Under the section Tools, Utilities and Programmers Guides select On-Line
API Guide.html
- From Innovator Client UI. Login as Innovator Administrator. Under the Help
menu select API Reference
- In Innovator CD Image. Go to the documentation folder and open Aras
Innovator - API Guide.html

Page 72

8.1

Grid/TreeGrid/ExcelGrid Control

The TreeTable.dll assembly contains 3 controls: GridContaner (a simple Grid),

TreeGridContainer (a Grid with a Tree), and ExcelGrid (an Excel like grid that is used
in Innovator configurable grid.) Which control used is controlled by the base classId
attribute for the <OBJECT> tag.

GridContainer (simple grid)

classid="../cbin/TreeTable.dll#Aras.Client.Controls.GridContainer"

TreeGridContainer (tree grid)

classid="../cbin/TreeTable.dll#Aras.Client.Controls.TreeGridContainer"

ExcelGrid (excel grid)

classid="../cbin/TreeTable.dll#Aras.Client.Controls.ExcelGrid

8.1.1

Initialization from XML

The Grid/TreeGrid/ExcelGrid control can be initialized within HTML page:

or with JavaScript using method InitXML() that loads XML string/url into the grid.
See also How to build XML for a Gridfor more details on what tags to use when
constracting grid xml.
8.1.2

Grid Methods and Events

8.1.3

TreeGrid Methods and Events

8.1.4

ExcelGrid Methods

8.1.5

Cell Methods

Methods that are used to control a Grid: e.g. add/remove row, add cell content, etc.
are exposed via IGridComIncoming interface while IGridComEvents interface is used
to expose GridContainer events to COM clients.
Methods that are used to control a TreeGrid, e.g. add, remove, open, and close a
Tree item are exposed via ITreeGridComIncoming Interface while
ITreeGridComEvents interface is used to expose TreeGridContainer events to COM
clients. As these interfaces extend IGridComIncoming and IGridComEvents
respectively all the members of Grid control public API are available for TreeGrid
control as well.
Methods that are used to control an ExcelGrid are exposed via
IExcelGridComIncoming interface. As this interface extends the IGridComIncoming
interface all the members of IGridComIncoming are available for ExcelGrid control as
well.
Methods that are used to control a Cell Object for all grid controls are exposed via
ICellComIncoming interface. You can get a handle to the Cell Object from the Grid
using methods like Cells(), GetSelectedCell(), and GetCurCell() that return
ICellComIncoming type and then use methods from ICellComIncoming interface to
manage a Cell. A handle to a Cell may be also obtained in event handling scripts

Page 73

using methods like GridSelectCell(..) found in one of two interfaces

IGridComEvents or ITreeGridComEvents.
8.1.6

ContextMenu Methods

8.2

Menu bar

8.2.1

Initialization from XML

Methods that are used to control a popup menu associated with the Grid and other
controls are exposed via IContextMenuWrapperComIncoming interface. You can get
a handle to the ContextMenu Object from the Grid using GetMenu(). It also can be
obtained in event handling scripts using OnMenuShow() method of
IWorkflowComEvents interface. See section 8.3 for more details on Worklow control.

The menubar control supports all standard types of menu elements; you can specify
more than one menu bar for one control and switch between them via JavaScript.
The menubar control can be initialized within HTML page:
<object id="menu" classId="../cbin/MainMenu.dll#Aras.Client.Controls.MainMenu"
style="width:100%; height:100%;" align="baseline">
<param name="XML" value=[xml_url]>
</object>

See also How to build XML for a Menu for more details on what tags to use in the
menubar xml.
.
8.2.2

MainMenu Methods and Events

8.2.3

Menu Element Methods

Two methods FindMenu() and FindItem() to control menu are exposed via
IMainMenuComIncoming interface while IMainMenuComEvents interface is used to
expose MainMenu events to COM clients.
There are three types of menu items:
- Non-terminal element (controlled by methods from IMenuContainerComIncoming
interface).
- Simple terminal element (controlled by methods from IMenuElementComIncoming
interface).
- Checkbox type terminal element (controlled by methods from
IMenuCheckedElementComIncoming interface).
You can get a handle to an object that implement one of these interfaces using
FindItem() method from a MainMenu object or from any of non-terminal element
objects or obtain it in event handling scripts using OnCheck() and/or OnSelect()
methods of IMainMenuComEvents interface.

Page 74

8.3

Workflow

8.3.1

Initialization from XML

The WorkflowContainer control can be initialized within HTML page:

or with JavaScript using method Load() that loads XML string/url into the workflow.
8.3.2

Workflow Methods and Events

8.3.3

Workflow Item Methods

8.4

Toolbar

8.4.1

Initialization from XML

8.4.2

Toolbar Methods and Events

8.4.3

Active Toolbar Methods

Methods that are used to load and control a Workflow, e.g. add, delete, and get a
Workflow items are exposed via IWorkflowComIncoming interface while
IWorkflowComEvents interface is used to expose Workflow events to COM clients.

There are two types of workflow items:

- Activity (controlled by methods from IActivityComIncoming interface).
- Transition (controlled by methods from ILinkComIncoming interface).
It is important to notice that two interfaces above inherit all the methods from their
common base interface IWFItemComIncoming. You can get a handle to a Workflow
Item Object from the WorkflowContainer using method like GetNode(),
GetSelectedNode() and AddNode() for an Activity or methods like
GetTransition(), GetSelectedTransition(), and AddTransition()for a
Transition and then use members of appropriate interface to manage a Workflow
Item. A handle to a Workflow item can be also obtained in event handling scripts
using methods like onClick() of IWorkflowComEvents interface.

There are two methods LoadToolbarFromStr() and LoadXml() to load XML into
toolbar with JavaScript. First method loads XML string and second loads the given
url.
Methods that are used to load and control a Toolbar, including hide, show and get a
Toolbar items are exposed via IToolbarComIncoming interface while
IToolbarComEvents interface is used to expose Toolbar events to COM clients.

Methods that are used to control an Active Toolbar Object are exposed via
ITToolbarComIncoming interface. You can get a handle to an Active Toolbar Object
from the Toolbar using method GetActiveToolbar() and then use members of
ITToolbarComIncoming interface to manage an Active Toolbar.

Page 75

8.4.4

Toolbar Item Methods

8.5

Structure

8.5.1

Structure Container Methods and Events

8.5.2

Structure Item Methods

8.6

Gantt

8.6.1

Initialization from XML

There are three types of toolbar items:

- Button (controlled by methods from IButtonComIncoming interface).
- TextBox (controlled by methods from ITextBoxComIncoming interface).
- ComboBox (controlled by methods from IComboBoxComIncoming interface).
All three interfaces above inherit method GetId() - the only method of their
common base interface IBaseComIncoming. You can get a handle to a Toolbar
Item Object from the Toolbar using method GetItem()or from Active Toolbar using
method GetElement() and then use members of appropriate interface to manage a
Toolbar Item. A handle to a Toolbar item can be also obtained in event handling
scripts using OnChange() or Onclick()methods of IToolbarComEvents interface.

Methods that are used to

- get/set Structures root item - methods GetRootItem() and SetRootItem(),
- specify layout of a Structure - method SetLayout(),
- get a Structure item - method .GetItem() and GetSelectedItem()
are exposed via IStructureComIncoming interface while IStructureComEvents
interface is used to expose Structure Container events to COM clients.
Methods that are used to actually control a Structure, e.g. add/remove items,
expend/collapse nodes, etc. are exposed via IStructureItemComIncoming interface.
You can get a handle to a Structure Item Object
- from a Structure Container using methods GetItem() or GetSelectedItem(),
or
- from a Structure Item using methods such as AddChildItem(),
AddNextItem(), GetChildItem(), GetParentItem(), etc.
In addition, a handle to a Structure item can be obtained in event handling scripts
using methods like StructureOnDbClick() or StructureOnOpenItem() of the
IStructureComEvents interface.

The classId with Gantt.dll is used as a container for ProjectTree, Task, Dependency,
and WBS objects and their COM interfaces.
Use method Load() to load XML from the given URL into a Project Tree with
JavaScript.

Page 76

8.6.2

ProjectTree Methods

8.6.3

Task Methods

The method to load a Project Tree is exposed via IProjectTreeCOMIncoming

interface while IProjectTreeComEvents interface is used to expose ProjectTree
events to COM clients.
Methods that are used to control a Task are exposed via ITaskComIncoming
interface. You can get a handle to a Task Object by one of two means:
-

From the ProjectTree in event handling scripts using method OnTaskChanged()of

the IProjectTreeComEvents interface.
From a Task Object using methods of ITaskComIncoming interface such as
AddNextTask() and GetChildTask().

8.6.4

Dependency Methods

8.7

Status Bar

8.7.1

Initialization from XML

8.7.2

Status Bar Methods

8.8

Utility Control

8.8.1

Utility Methods

8.8.2

Balloon Methods

Methods that are used to control a Dependency are exposed via

IDependencyComIncoming interface. You can get a handle to a Dependency Object
from the Task using methods of ITaskComIncoming interface such as
AddDependency() and GetDependency().

Use method Load() to load XML from the given URL into status bar with JavaScript.

Methods that are used to load and control a Status Bar, including clear status, set
default message, set image, etc. are exposed via IStatusBarComIncoming interface.

The classid with Utils.dll is used as a container for Utility, Balloon, and Splash Screen
objects and their COM interfaces.
The collection of miscellaneous utility methods such as getter and setter for
DragFullWindows property and boolean CheckThatFullTrustIsSetForSite() as
well as methods returning instance of Balloon and Splash Screen objects are exposed
via IUtilsComIncoming interface.

Methods that are used to control a Balloon are exposed via IBalloonComIncoming
interface. You can get a handle to a Balloon Object from the Utility Control using
GetBalloon() method of IUtilsComIncoming interface.

Page 77

8.8.3

Splash Screen Methods and Events

8.9

Other Controls

8.9.1

Tabbar Methods and Events

8.9.2

Calendar Methods and Events

8.9.3

Vault Methods and Events

8.9.4

Color Dialog Method

Properties and methods to control a Splash Screen are exposed via

ISplashScreenComIncoming interface while ISplashScreenComEvents interface is
used to expose Splash Screen events to COM clients. You can get a handle to a
SplashScreen Object from the Utility Control using GetSplashScreen() method of
IUtilsComIncoming interface.

The SimpleTabbar control methods and events are exposed to the COM clients via
ISimpleTabbarComIncoming and ISimpleTabbarComEvents interfaces respectively.
There is no method available to return a handle to an individual tab Object.
The properties and methods to control a Calendar are exposed via
ICalendarComIncoming interface while ICalendarComEvents interface is used to
expose Calendar events to COM client.
Methods to control a Vault are exposed via IVaultComIncoming interface while
IVaultComEvents interface is used to expose the only Calendar event Onload() to
COM client.
The IColorDialogComIncoming interface is to expose a single method GetColor()
of a Color Dialog object.

Page 78

9 Aras Innovator Solution Studio

The Aras Innovator Solution Studio is the user interface you use to author the code
for your Innovator Methods. It is automatically launched when you open a Method
Item in Aras Innovator client.

9.1

Features

The Solution Studio offers several useful features to help aid you in the development
of your Methods.

A robust text editor with search/replace and undo/redo capabilities.

An IOM API code guide.

Color coding the keywords for the language you are developing in.

An online help interface that is context sensitive for the methods selected in
the code guide.
Syntax checking based on the language you are developing in.
Undo/Redo

Syntax checker

Search/Replace
IOM API
Code Guide

Keyword
Color Coding

IOM API
Online Help

Page 79

10 Debugging
Aras Innovator has the following features for debugging/logging your Methods:

Visual Studio to debug Methods either client or server.

Logging of debug messages to an XML formatted log file.

10.1 Setting up VS.NET 2003 to debug Server side Methods

Open "Microsoft Visual Studio .NET 2003" debugger.

Choose aspnet_wp.exe and click the 'Attach' button.

Uncheck the boxes except for the 'Common Language Runtime' and click OK.

Choose Tools->Debug Processes

Page 80

Choose Debug->Exceptions to force the method into the debugger when an

exception occurs and choose the radio buttons "Break into the debugger".

Optionally, you can include the line

System.Diagnostics.Debugger.Break()to force a breakpoint at a specific
line in your method.

10.2 Setting up VS.NET 2003 to debug Client side Methods

Open "Internet Explorer" to set debugger options.

Select the Advanced tab and make sure the "Disable Script Debugging" is
turned off and "Display notification about script errors" is turned on.

Include the line debugger to your Method.

Choose Tools->Internet Options

Page 81

Run the Method and the application will open the "Microsoft Visual Studio
.NET 2003" debugger and break on the debugger line.

10.3 Setting up the server side logging

Add the following lines to the InnovatorServerConfig61.xml file:

<operating_parameter key="debug_log_flag" value="true" />
<operating_parameter key="debug_log_prefix" value="C:/TEMP/DEBUG-" />
<operating_parameter key="debug_log_limit" value="1000" />

In order to write messages to the C:/TEMP/DEBUG-* log file, add the following lines
of code to the server side method:
Dim sc as Object = Me.serverConnection
sc.cco.startup.debuglog("Unique string to identify message in log file", "Actual
message written to log file")

Page 82

11 External APIs
There are a few ways to connect to the Aras Innovator server from other
applications. Aras provides two client controls (.NET and ActiveX) that implement
the IOM API and can be embedded in other applications. Alternatively, simple SOAP
communication can be used to connect to Aras Innovator.

11.1 .NET Component

A .NET component is included in the Aras Innovator installation which may be

embedded in other applications. This file, named IOM.dll, can be found in the
Innovator/Server/bin directory and may be copied to another location and referenced
by the application.
The IOM.HTTPServerConnection object should first be used to set the connection
parameters and credentials. A new IOM.Innovator object may then be created to
initiate a session. Once the session is started, IOM.Item objects are used to
manipulate items. The IOM.HTTPServerConnection.Close() method closes the connection.
The following is a C# example:

IOM.HTTPServerConnection Conn = new IOM.HTTPServerConnection();

Conn.innovator_server_url =
"http://localhost/InnovatorServer/Server/InnovatorServer.aspx";
Conn.http_username = "admin";
Conn.http_password = IOM.Innovator.ScalcMD5("innovator");
Conn.http_database = "innovator81";
IOM.Innovator Inn = new IOM.Innovator(Conn);
IOM.Item queryItem = Inn.newItem("User","get");
queryItem.setAttribute("select","login_name");
IOM.Item resultItem = queryItem.apply();
System.Console.WriteLine("Number of users: "+resultItem.getItemCount());
Conn.Close();

11.2 ActiveX Control

An IOM ActiveX control is included in the Aras Innovator installation and delivered as
part of the ArasIOM.cab cabinet file in the Innovator\Client\cbin directory. This
control can be used to build Windows applications (in VB6 or VC++, for example) or
Windows Scripting Host applications (VBScript or Jscript).
The ActiveX control is implemented as a DLL file that you must register in order to
use. The steps to do so are as follows:

Extract ArasIOMActiveX.dll from ArasIOM.cab

Copy ArasIOMActiveX.dll into the C:\Windows\system32 folder.
Open a DOS window and enter the regsvr32 command to register the DLL:
regsvr32 ArasIOMActiveX.dll

To connect to the Aras Innovator server, you must first create a new instance of an
Innovator object and set the connection parameters/credentials. You may then use
the Innovator.login() method to establish a session. Once the session is established,
you can create new Item objects and operate on them. To end the session, you
should call the Innovator.logout() method.
The following is a VBScript example:

Page 83

Dim myInnovator: Set myInnovator = CreateObject("Aras.IOM.Innovator.8")

Dim credentials: Set credentials = myInnovator.credentials
credentials.setInnovatorServerURL
"http://localhost/InnovatorServer/Server/InnovatorServer.aspx"
credentials.setDatabase " innovator81"
credentials.setLoginName "admin"
credentials.setPassword "innovator"
Dim stat: Set stat = myInnovator.login
If stat.IsError() Then
Wscript.Echo stat.GetErrorDetail
End If
Dim queryItem: Set queryItem = myInnovator.newItem()
queryItem.setType "User"
queryItem.setAction "get"
queryItem.setAttribute "select", "login_name"
Dim resultItem: Set resultItem = queryItem.apply()
Wscript.Echo "Number of users: " & resultItem.getItemCount()
myInnovator.logout

The following is a JScript example:

var myInnovator = new ActiveXObject("Aras.IOM.Innovator.8");
var credentials = myInnovator.credentials;
credentials.setInnovatorServerURL(
"http://localhost/InnovatorServer/Server/InnovatorServer.aspx");
credentials.setDatabase("innovator81");
credentials.setLoginName("admin");
credentials.setPassword("innovator");
var stat = myInnovator.login();
if (stat.IsError()) {
WScript.echo(stat.GetErrorDetail());
}
var queryItem = myInnovator.newItem();
queryItem.setType("User");
queryItem.setAction("get");
queryItem.setAttribute("select","login_name");
var resultItem = queryItem.apply();
WScript.echo("Number of users: "+resultItem.getItemCount());
myInnovator.logout();

11.3 SOAP Requests

Although not normally suggested, it is possible to circumvent IOM and use SOAP
requests to interact with Aras Innovator. You may use the Microsoft XMLHTTP
Object to send the AML to the Aras Innovator Server.
The following is a VBScript example:

Dim innovatorServer
innovatorServer = "http://localhost/InnovatorServer/Server/InnovatorServer.aspx"
Dim database: database = "innovator81"
Dim loginName: loginName = "admin"
Dim password: password = "607920b64fe136f9ab2389e371852af2" 'MD5 hash of the password
Dim soapStart: soapStart = _
"<SOAP-ENV:Envelope xmlns:SOAP-ENV='http://schemas.xmlsoap.org/soap/envelope/' " &_
"encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'><SOAP-ENV:Body>"
Dim soapEnd: soapEnd = "</SOAP-ENV:Body></SOAP-ENV:Envelope>"
Dim soapAction: soapAction = "ApplyItem"
Dim body: body = "<Item type='User' action='get' select='login_name'/>"
Dim soap
soap = soapStart & "<" & SOAPAction & " xmlns:m='http://www.aras-corp.com/'>" &_

Page 84

body & "</" & soapAction & ">" & soapEnd

Dim http: Set http = CreateObject("Msxml2.ServerXMLHTTP")
http.open "POST", innovatorServer, false
http.setRequestHeader "SOAPaction", soapAction
http.setRequestHeader "AUTHUSER", loginName
http.setRequestHeader "AUTHPASSWORD", password
http.setRequestHeader "DATABASE", database
http.send(soap)
Dim response: response = http.responseText
Dim responseDom: Set responseDom = CreateObject("microsoft.xmldom")
responseDom.loadXML(response)
Dim userItems: Set userItems = responseDom.selectNodes("//Item[@type='User']")
Wscript.Echo "Number of users: " & userItems.Length
soapAction = "logoff"
body = "logoff"
soap = soapStart & "<" & SOAPAction & " xmlns:m='http://www.aras-corp.com/'>" &_
body & "</" & soapAction & ">" & soapEnd
http.open "POST", InnovatorServer, false
http.setRequestHeader "SOAPaction", soapAction
http.setRequestHeader "AUTHUSER", loginName
http.setRequestHeader "AUTHPASSWORD", password
http.setRequestHeader "DATABASE", database
http.send(soap)

Page 85

12 Was/Is API Comparison

This section is a comparison chart comparing the old (Innovator 6.1.5 and earlier)
client and server API's with the new IOM API.
Was
(server VBScript)

Was
(client JavaScript)

ApplyAML inDom, outDom

aras.applyAML(String AML)

ApplySQL inDom, outDom

aras.soap.send(
'ApplySQL',
'<sql/>');
aras.applyMethod(
String method-name,
String body)

ApplyMethod inDom, outDom

Is
(JavaScript, C#, and
VB.Net)

Innovator.applyAML(
String AML)
Innovator.applySQL(
String SQL)

Innovator.applyMethod(
String method-name,
String body,
String location?)

CreateXMLDocument()

aras.createXMLDocument()

Innovator.newItem(
String itemtype-name,
String action)

SetErrorMessage outDom, faultcode,

detail
SetResult outDom, text

N/A

CreateXMLDocument

aras.createXMLDocument()

GetRequestItem inDom

Server.MapPath

itemDom.selectSingleNode('Item'
)
aras.generateNewGUID()
aras.login()
aras.logout()
N/A

Innovator.newError(String
detail)
Innovator.newResult(String
text)
Innovator.newXMLDocument
()
Innovator.getItemInDom(D
OM dom)
Innovator.getNewID()
Innovator.login()
Innovator.logout()
Innovator.MapPath(String
file-path)

ApplyItem inDom, outDom

aras.applyItem(String body)

itemDom.transformNode()

aras.applyXsltFile(
DOM itemDom,
String XSLT-filename)

GenerateNewGUID inDom, outDom

CreateXMLDocument()
itemDom.loadXML AML
itemDom.cloneNode()
itemDom.setAttribute(
"id",
NewID())
itemDom.getAttribute('isNew')
HasFault(
DOM itemDom,
Boolean ignoreZeroFault)
DOM API

N/A

aras.applyXsltString(
DOM itemDom,
String XSLT-string)
aras.createXMLDocument()
itemDom.loadXML(String AML)
itemDom.cloneNode()
itemDom.setAttribute(
'id', aras.generateNewGUID())
itemDom.getAttribute('isNew')
aras.hasFault(
DOM itemDom,
Boolean ignoreZeroFault)
DOM API

Item.apply(
String action,
String args-object,
String location)
Item.applyStylesheet(
String xsl-stylesheet,
String type)

Item.newXMLDocument()
Item.loadAML(String AML)
Item.clone(
String clone-relationships)
Item.setNewID()
Item.isNew()
Item.isError()
Item.isRoot()

Page 86

itemDom.selectNodes(XPath).length
HasFault(DOM itemDom, 1)
IsLocked(
String itemTypeID,
String itemID,
DOM outDom)
itemDom.getAttribute(
String attribute-name)
itemDom.setAttribute(
String attribute-name,
String value)
itemDom.getAttribute('action')
itemDom.setAttribute('action', String
action)
itemDom.getAttribute('id')
itemDom.setAttribute('id', String id)
itemDom.getAttribute('type')
itemDom.setAttribute('type',
String item-type-name)
GetItemProperty(
DOM itemDom,
String property-name)
SetItemProperty(
DOM itemDom,
String property-name,
String value)
itemDom.selectSingleNode(
String propertyname).getAttribute('condition')
itemDom.selectSingleNode(
String propertyname).getAttribute(String attributename)
itemDom.selectSingleNode(
String property-name).setAttribute(
String attribute-name,
String value)

itemDom.selectNodes(XPath).len
gth
aras.hasFault(DOM itemDom, 1)
aras.isLocked(DOM itemDom)

Item.isCollection

itemDom.getAttribute(
String attribute-name)

Item.getAttrribute(
String attribute-name,
?String default-value)
Item.setAttrribute(
String attribute-name,
String value)
Item.getAction()
Item.setAction(String
action)
Item.getID()
Item.setID(String id)

itemDom.setAttribute(
String attribute-name,
String value)
itemDom.getAttribute('action')
itemDom.setAttribute('action',
String action)
itemDom.getAttribute('id')
itemDom.setAttribute('id', String
id)
itemDom.getAttribute('type')
itemDom.setAttribute('type',
String item-type-name)
aras.getItemProperty(
DOM itemDom,
String property-name)
aras.setItemProperty(
DOM itemDom,
String property-name,
String value)
itemDom.selectSingleNode(
String propertyname).getAttribute('condition')
itemDom.selectSingleNode(
String propertyname).getAttribute(String
attribute-name)

Item.isEmpty()
Item.isLocked()

Item.getType()
Item.setType(
String item-type-name)
Item.getProperty(
String property-name,
String default-value)
Item.setProperty(
String property-name,
String value,
String condition)
Item.getPropertyCondition(
String property-name)
Item.getPropertyAttribute(
String property-name,
String attribute-name,
String default-value)

itemDom.selectSingleNode(
String propertyname).setAttribute(
String attribute-name,
String value)
itemDom.selectSingleNode(
String XPath)
itemDom.appendChild(Node
item)

Item.setPropertyAttribute(
String property-name,
String attribute-name,
String value)

itemDom.removeChild(Node item)

itemDom.removeChild(Node
item)

Item.removeProperty(
String property-name)

itemDom.selectSingleNode(
String XPath)

Item.getFileName()

ApplyItem(
DOM itemDom,
DOM outDom)

itemDom.selectSingleNode(
String XPath)
aras.setItemProperty(
DOM itemDom
String file-name)
aras.getRelationships(
DOM itemDom,
String itemtype-name)

itemDom.appendChild(
DOM itemDom)

Item.addRelationship(Item
item)

itemDom.selectSingleNode(
String XPath)
itemDom.appendChild(Node item)

Item.getPropertyItem(
String property-name)
Item.setPropertyItem(
String property-name,
Item item)

Item.setFileName(
String file-name)
Item.getRelationships(
String itemtype-name,
String select,
String order-by)

Page 87

itemDom.removeChild(Node item)

itemDom.removeChild(Node
item)
aras.getRelatedItem(
DOM itemDom)
itemDom.appendChild(
DOM itemDom)
itemDom.parentNode.parentNode
()
itemDom.selectSingleNode('../..')
itemDom.selectNodes(XPath).len
gth
itemDom.selectSingleNode(
String XPath)
itemDom.selectNodes(String
XPath)
itemDom.appendChild(Node
item)
itemDom.removeChild(Node
item)
DOM API or AML string
concatenation.
DOM API or AML string
concatenation.
DOM API or AML string
concatenation.

Item.removeRelationship(Ite
m item)
Item.getRelatedItem()

Item.getLogicalItems()

itemDom.removeChild(Node)

itemDom.selectNodes(String
XPath)
itemDom.removeChild(Node)

CreateXMLDocument()

aras.createXMLDocument()

Item.newItem(
String itemtype-name,
String action)

N/A
itemDom.selectSingleNode('//detail').t
ext
N/A

N/A
soapObj.getFaultDetails()

Item.newInnovator()
Item.getErrorDetail()

N/A

N/A
N/A

Item.setErrorDetail(
String detail)
Item.getErrorString()
Item.setErrorString(
String error-message)

N/A
N/A

itemDom.selectSingleNode('//Result')

soapObj.getResults()

itemDom.selectSingleNode(
String XPath)
itemDom.appendChild(
DOM itemDom)
itemDom.parentNode.parentNode()
itemDom.selectSingleNode('../..')
itemDom.selectNodes(XPath).length
itemDom.selectSingleNode(
String XPath)
itemDom.selectNodes(String XPath)
itemDom.appendChild(Node item)
itemDom.removeChild(Node item)
DOM API or AML string concatenation.
DOM API or AML string concatenation.
DOM API or AML string concatenation.
itemDom.selectNodes(String XPath)

Item.setRelatedItem(
Item item)
Item.getParentItem()
Item.getItemCount()
Item.getItemByIndex(
Number 0..N-1)
Item.getItemsByXPath(
String xpath)
Item.appendItem(Item
item)
Item.removeItem(Item
item)
Item.newOR()
Item.newAND()
Item.newNOT()

Item.removeLogical(
Item item)

Item.getErrorWho()
Item.setErrorWho(
String who)
Item.getErrorSource()
Item.setErrorSource(
String source)
Item.getResult()

Page 88

13 AML Schema
The AML dialect described above follows the following XML Schema. The majority of
this schema defines the standard set of Properties all Items have.
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="AML">
<xsd:complexType maxOccurs="unbounded">
<xsd:element name="Item">
<xsd:attribute name="id" type="xsd:ID" />
<xsd:attribute name="type" type="xsd:string" />
<xsd:attribute name="typeID" type="xsd:IDREF" />
<xsd:attribute name="action" type="xsd:string" />
<xsd:attribute name="order_by" type="xsd:string" />
<xsd:attribute name="select" type="xsd:string" />
<xsd:attribute name="pagesize" type="xsd:integer" />
<xsd:attribute name="page" type="xsd:integer" />
<xsd:attribute name="levels" type="xsd:integer" />
<xsd:attribute name="config_path" type="xsd:string" />
<xsd:attribute name="version" type="xsd:Boolean" />
<xsd:attribute name="serverEvent" type="xsd:Boolean" />
<xsd:element name="id">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="32" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="classification">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="512" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="keyed_name">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="128" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="created_on" type="xsd:dateTime" />
<xsd:element name="created_by_id">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="32" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="modified_on" type="xsd:dateTime" />
<xsd:element name="modified_by_id">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="32" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="current_state">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="32" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="state">

Page 89

<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="32" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="locked_by_id">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="32" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="is_current">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="major_rev">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="8" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="minor_rev">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="8" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="is_released">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="not_lockable">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="css">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="2147483647" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="generation" type="xsd:int" />
<xsd:element name="new_version">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="1" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="config_id">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="32" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Relationships"

Page 90

minOccurs="0" maxOccurs=" unbounded ">

<xsd:element name="Item"/>
</xsd:element>
</xsd:element>
</xsd:complexType>
<xsd:any/>
<!
Any elements defined as Properties by the ItemType for the Item.
These would be the Property Tags for the Item.
- ->
<xsd:unique name="Constraint1" msdata:PrimaryKey="true">
<xsd:selector xpath=".//Item" />
<xsd:field xpath="id" />
</xsd:unique>
</xsd:element>
</xsd:schema>

Page 91

WFM80 User Guide RevC
No ratings yet
WFM80 User Guide RevC
418 pages
Project Proposal Document
57% (7)
Project Proposal Document
27 pages
SuperMarketProject (WEKA)
0% (1)
SuperMarketProject (WEKA)
20 pages
Infor Mashup SDK Developers Guide Mashup SDK
No ratings yet
Infor Mashup SDK Developers Guide Mashup SDK
51 pages
Flutter for Beginners: An introductory guide to building cross-platform mobile applications with Flutter and Dart 2
From Everand
Flutter for Beginners: An introductory guide to building cross-platform mobile applications with Flutter and Dart 2
Alessandro Biessek
No ratings yet
Aras Innovator 9.3 - Installation Guide
No ratings yet
Aras Innovator 9.3 - Installation Guide
66 pages
Introduction To Application Development With BMC Remedy Developer Studio
No ratings yet
Introduction To Application Development With BMC Remedy Developer Studio
96 pages
Error List - Informatica
0% (2)
Error List - Informatica
216 pages
Assessment 1 - Written Questions: Task 1
No ratings yet
Assessment 1 - Written Questions: Task 1
16 pages
Construction Simulation Robot Arm Op Engl
No ratings yet
Construction Simulation Robot Arm Op Engl
27 pages
A Project Report College Website Design
50% (8)
A Project Report College Website Design
45 pages
ARAS Programmers Guide
No ratings yet
ARAS Programmers Guide
98 pages
Aras Innovator Programmers Guide
No ratings yet
Aras Innovator Programmers Guide
105 pages
Aras Innovator 2023 Release Programmers Guide
No ratings yet
Aras Innovator 2023 Release Programmers Guide
107 pages
Student Master Developers 11
100% (1)
Student Master Developers 11
410 pages
Aras Innovator ConfiguringSolutions StudentGuide July2023
No ratings yet
Aras Innovator ConfiguringSolutions StudentGuide July2023
423 pages
Aras Innovator 10.0 - Installation Guide
No ratings yet
Aras Innovator 10.0 - Installation Guide
63 pages
Aras Innovator 2023 Release - RESTful API
No ratings yet
Aras Innovator 2023 Release - RESTful API
42 pages
2023 Release-Configurable InBasket
No ratings yet
2023 Release-Configurable InBasket
33 pages
Aras Innovator 9.2 - Installation Guide
No ratings yet
Aras Innovator 9.2 - Installation Guide
61 pages
Installation of PLM
No ratings yet
Installation of PLM
68 pages
Aras Innovator 2023 Release - Release Notes
No ratings yet
Aras Innovator 2023 Release - Release Notes
46 pages
Aras Innovator 120 Installation Guide
No ratings yet
Aras Innovator 120 Installation Guide
74 pages
Aras Innovator 120 Tree Grid View Administrator Guide
No ratings yet
Aras Innovator 120 Tree Grid View Administrator Guide
71 pages
2023 Release-Package Import Export Utilities
No ratings yet
2023 Release-Package Import Export Utilities
22 pages
Aras Innovator 11.0 - Installation Guide
No ratings yet
Aras Innovator 11.0 - Installation Guide
73 pages
2023 Release-Graph Navigation User Guide
No ratings yet
2023 Release-Graph Navigation User Guide
11 pages
Aras Innovator 12.0 - Microsoft Reporting Services 2012 Guide PDF
No ratings yet
Aras Innovator 12.0 - Microsoft Reporting Services 2012 Guide PDF
43 pages
SLIDES Aras PLM Software Integration Basics
100% (1)
SLIDES Aras PLM Software Integration Basics
23 pages
Tutorial Android Studio - Preview
No ratings yet
Tutorial Android Studio - Preview
51 pages
2023 Release Platform Specifications
No ratings yet
2023 Release Platform Specifications
13 pages
Aras Innovator 30 - Release Notes
No ratings yet
Aras Innovator 30 - Release Notes
18 pages
Aras Innovator 2023 Release Client Settings For Chrome On Mac
No ratings yet
Aras Innovator 2023 Release Client Settings For Chrome On Mac
7 pages
Aras Innovator 120 Release Notes
No ratings yet
Aras Innovator 120 Release Notes
29 pages
Aras Update User Guide
No ratings yet
Aras Update User Guide
18 pages
2023 Release-Backup and Recovery
No ratings yet
2023 Release-Backup and Recovery
15 pages
Aras Innovator 2023 Release Client Settings For Chrome
No ratings yet
Aras Innovator 2023 Release Client Settings For Chrome
7 pages
2023 Release-Conversion Server Setup Guide
No ratings yet
2023 Release-Conversion Server Setup Guide
22 pages
Aras Innovator 14 - Release Notes
No ratings yet
Aras Innovator 14 - Release Notes
41 pages
VB A Developers Guide
No ratings yet
VB A Developers Guide
290 pages
DMCM Process Modeling
No ratings yet
DMCM Process Modeling
386 pages
TMF639 Resource Inventory Userguide v5.0.0
No ratings yet
TMF639 Resource Inventory Userguide v5.0.0
100 pages
Ifsm 2024.x Ifsmoeug en-us
No ratings yet
Ifsm 2024.x Ifsmoeug en-us
55 pages
IDempiere FA User Manual
No ratings yet
IDempiere FA User Manual
16 pages
799 - IA DIS Field Master Items
No ratings yet
799 - IA DIS Field Master Items
44 pages
AVEVA Area Based ADP Admin Guide
No ratings yet
AVEVA Area Based ADP Admin Guide
62 pages
ABADPAG Pdms File
No ratings yet
ABADPAG Pdms File
62 pages
Discover The Best Way To Add Products and Services: About Inventory in Xero
No ratings yet
Discover The Best Way To Add Products and Services: About Inventory in Xero
8 pages
Inventory Management - People Soft
0% (1)
Inventory Management - People Soft
564 pages
Teamcenter
No ratings yet
Teamcenter
481 pages
Teamcenter 10.1: Publication Number PLM00046 I
No ratings yet
Teamcenter 10.1: Publication Number PLM00046 I
481 pages
Afc Reference
No ratings yet
Afc Reference
752 pages
IM1x 452 ERP Hands-On Session II en
No ratings yet
IM1x 452 ERP Hands-On Session II en
3 pages
11.5.10 Inventory
No ratings yet
11.5.10 Inventory
682 pages
Aras Innovator 2023 Release Client Settings For Edge On Windows
No ratings yet
Aras Innovator 2023 Release Client Settings For Edge On Windows
7 pages
Aras Innovator 2023 Release Client Settings For Firefox On Mac
No ratings yet
Aras Innovator 2023 Release Client Settings For Firefox On Mac
12 pages
Archer Dynamic Workflow Tracker Tool & Utility 6.12 P1 Implementation Guide
No ratings yet
Archer Dynamic Workflow Tracker Tool & Utility 6.12 P1 Implementation Guide
52 pages
Inventory (001 100)
No ratings yet
Inventory (001 100)
100 pages
Build and Migrate an Solution_ICM
No ratings yet
Build and Migrate an Solution_ICM
296 pages
Mastering Ansible - Second Edition
From Everand
Mastering Ansible - Second Edition
Keating Jesse
No ratings yet
JasperReports for Java Developers: Create, Design, Format, and Export Reports with the World's Most Popular Java Reporting Library
From Everand
JasperReports for Java Developers: Create, Design, Format, and Export Reports with the World's Most Popular Java Reporting Library
David R. Heffelfinger
No ratings yet
Unleashing the Power of Astro
From Everand
Unleashing the Power of Astro
Tamas Piros
No ratings yet
Advanced Express Web Application Development
From Everand
Advanced Express Web Application Development
Andrew Keig
No ratings yet
Customer Request Form
No ratings yet
Customer Request Form
2 pages
Demat Closure Form
No ratings yet
Demat Closure Form
2 pages
Is Zc415 (Data Mining BITS-WILP)
No ratings yet
Is Zc415 (Data Mining BITS-WILP)
4 pages
Computer Networks - BITSZC481 Syllabus
No ratings yet
Computer Networks - BITSZC481 Syllabus
5 pages
C# Module 1
100% (2)
C# Module 1
81 pages
Devforce Reference
No ratings yet
Devforce Reference
759 pages
Visual Studio .NET - Guide For Developers
No ratings yet
Visual Studio .NET - Guide For Developers
305 pages
Lab Manual: School of Computing Science & Engineering
No ratings yet
Lab Manual: School of Computing Science & Engineering
36 pages
G11-TVL-ICT Programming (.Net Technology) Capslet Quarter 3-Week 4
100% (1)
G11-TVL-ICT Programming (.Net Technology) Capslet Quarter 3-Week 4
9 pages
14
No ratings yet
14
6 pages
Lession - 3 Data Types in C#
No ratings yet
Lession - 3 Data Types in C#
15 pages
Himanshu Arora
No ratings yet
Himanshu Arora
3 pages
C#
No ratings yet
C#
18 pages
C# Question Bank
No ratings yet
C# Question Bank
4 pages
BCA 6th Sem
No ratings yet
BCA 6th Sem
29 pages
Advanced Programming
50% (2)
Advanced Programming
89 pages
PM100x Visual Csharp
No ratings yet
PM100x Visual Csharp
13 pages
Amit Kumar Rai: Professional Summary
No ratings yet
Amit Kumar Rai: Professional Summary
6 pages
FUD C# Backdoor
No ratings yet
FUD C# Backdoor
7 pages
Oh No More Modern CMake
No ratings yet
Oh No More Modern CMake
163 pages
Chandhya Resume
No ratings yet
Chandhya Resume
2 pages
Using System Class Name (Public Static Void Main (Console - Writeline ("My Name Is Sujit") ) )
No ratings yet
Using System Class Name (Public Static Void Main (Console - Writeline ("My Name Is Sujit") ) )
26 pages
Dayone Unity
No ratings yet
Dayone Unity
12 pages
C# Laborator 2
No ratings yet
C# Laborator 2
5 pages
Understanding OOP Concepts With C#
No ratings yet
Understanding OOP Concepts With C#
16 pages
Online Career Guidance System Abstract
0% (1)
Online Career Guidance System Abstract
51 pages
C# MCQ
No ratings yet
C# MCQ
12 pages
CBT - Question Bank
No ratings yet
CBT - Question Bank
2 pages
04 Assembly
No ratings yet
04 Assembly
41 pages
Unit 1
No ratings yet
Unit 1
54 pages
Visualstudio Data Tools Vs 2022
No ratings yet
Visualstudio Data Tools Vs 2022
484 pages