Action – Add

AML Query

<!-- SOAP_ACTION = AddItem, ApplyAML, or ApplyItem -->
<Item action='add'>
  <property>value</property>
</Item>

Attributes

Attribute	Type	Usage
do_skipOnAfterAdd	Boolean	If 1 then don't run onAfterAdd server events. Default is 0
serverEvents	Boolean	If 0 then disable server events when running the doGetItem only. onBefore/AfterAdd events are not disabled. Default is 1.

Examples

You can use the current time in an add query using the constant __now().

<Item action='add'>
  <date_start_act>__now()</date_start_act>
</Item>

Pipeline

.

Event	Context	Notes
onBeforeAdd	<Item action='add' id='1234'> <property>value</property> </Item>
Permission Checks		Permission checks occur after the `onBeforeAdd` methods in case the classification is modified which impacts CanAdd permissions.
GetKeyedName	<Item id='1234'> <!-- All property data** --> </Item>
Life Cycle		No methods are called, but this is when the state is associated with the item.
onGet		Only called if there are one or more onAfterAdd v1 methods
onAfterAdd (v1)	<Item id='1234'> <!-- All property data --> </Item>	OnAfterAddEventArgs { IdList = {"1234"}, TypeId = "A1B2", Id = "1234" } Version 1 methods are called once per Item ID
onAfterAdd (v2)	<Item/>	OnAfterAddEventArgs { IdList = {"1234"}, TypeId = "A1B2", Id = "1234" } Version 2 methods are only called once per request.
Workflow Set Up		Same methods called as with voting except that OnActivate is called for the start state
onGet		Can be suppressed by adding the attribute doGetItem='0' to the AML request