API Message Types

This section provides a list of the message types used by the API. A complete list of message types shipped with ASM appears on the Message Types window within System Administration.

Limited Support/End of Life Capabilities

The Classic API has been replaced by the Alemba RestFul API. While we will continue to support the Classic API for clients that are still using it, no further development will be done.

If you need to request a hotfix or support for these features, please contact Alemba Support

For more information on message transactions available in the Classic API, see Message Transactions.

Message transactions in the Classic API can specify the email template to be used in two ways:

  • by specifying the Message Type (see the table below)

  • by specifying the MessageMapRef for the HD_MESSAGE_MAP table

If Message Type is specified, the default email template from the HD_MESSAGE_MAP table is used. If a Message Type and Message Map Ref are not specified, the message type is taken from the table of defaults below:

Name

Code

Description

mTaskAPIOwner

7000

Message from API to Task Owner

mRequestAPIOwner

7001

Message from API to Request Owner

mCallAPIOwner

7004

Message from API to Call Owner

mCallAPICustomer

7005

Message from API to Call User

mCallAPIStakeholders

7006

Message from API to Call Stakeholders

mCIAPIStakeholders

7007

Message from API to CMDB item Stakeholders

mCIAPICustomer

7009

Message from API to CI User

mCustomerAPI

7010

Generic Message from API to User

mOfficerAPI

7011

Generic Message from API to Analyst

mIPGroup

7013

Generic Message from API to IPK Group

mCMGroup

7014

Generic Message from API to Workflow Group

Copyright 2023 Alemba, ASM EOS 10.4