The result of a
SmsTemplateHistory request (i.e., the change
history of the given SMS Template) is represented as an XML document.
This XML document will be contained with the
<reqparams> tag of the normal 8MS API return
structure. For example, the following might be returned from
a history request:
<API8MS>
<reqid>OA03743771</reqid>
<message>
<routeid></routeid>
<termrpt>COMPLD</termrpt>
<errorcd>0</errorcd>
<reqparams>
<history templatename="*AR-CSF-01">
<change>
<activity-date>05/15/2013 13:00:01</activity-date>
<status>OLD</status>
<effective-date>05/06/2013 12:45:00</effective-date>
<control-resporg>ART10</control-resporg>
<extract-date>06/16/2013 00:01:00</extract-date>
</change>
<change>
<activity-date>06/11/2013 18:23:31</activity-date>
<status>ACTIVE</status>
<effective-date>06/11/2013 12:00:00</effective-date>
<control-resporg>ART10</control-resporg>
<extract-date>06/16/2013 00:01:00</extract-date>
</change>
</history>
</reqparams>
</message>
</API8MS>
Each
<change> within the
<history> consists
of the following:
|
activity-date
|
the date/time the SMS Template was activated
|
|
status
|
the SMS Template status at that point in time
|
|
effective-date
|
the date/time the SMS Template attained the given status
|
|
control-resporg
|
the controlling resporg of the number at that time
|
|
extract-date
|
the date/time that the record was retrieved
from the main SMS/800 DB
|