Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Production Management

GetFinalizationHistory request message

  • Last UpdatedSep 06, 2023
  • 2 minute read

This is an example of the full structure of a GetFinalizationHistory request.

<GetFinalizationHistoryRequestMessage xmlns="http://www.citect.com/Ampla/Inventory/2010/03">

<Request>

<Credentials>

<Password>********</Password>

<Session />

<Username>User</Username>

</Credentials>

<Filter>

<TopN>2</TopN>

</Filter>

<Localization>

<Language>fr-FR</Language>

<Localization>

</Request>

</GetFinalizationHistoryRequestMessage>

Request parameters: Credentials section

The Credentials section contains the security details for authentication. You can provide the Username and Password values to use the Basic security method. If you do not provide explicit security values, Web services will attempt to use Integrated authentication. You must provide either Basic credentials, Integrated credentials, or a Session ID.

<Credentials>

<Username>User</Username>

<Password>********</Password>

<Session />

</Credentials>

Parameter

Description

Username

The login name of the AVEVA™ Production Management user. This is a string value. Username and Password together are mutually exclusive with Session.

Password

The password that is associated with the AVEVA Production Management user. This is a string value. Username and Password together are mutually exclusive with Session.

Session

A GUID string value that identifies the session. This is a string value. Mutually exclusive with Username and Password.

Request parameters: Filter section

<Filter>

<TopN>2</TopN>

</Filter>

Parameter

Description

TopN

Enables you to specify the N number of finalization operations (going backwards in time from the present). For example, the last 2 finalizations.

  • Returns the latest N finalizations, from most recent to oldest.

  • If specified N is greater than number of history items available, then all history is returned.

  • If never there has never been a finalization, no data is returned.

Request parameters: Localization section

The Localization section contains parameters that are relevant to localizing the data for display.

<Localization>

<Language>fr-FR</Language>

< /Localization>

Parameter

Description

Language

The Windows regional setting to determine the language display of data in the client. This can be any Windows regional setting value, for example, en-AU, en-GB, fr-FR. If no language is specified, the default en-US is used.

In This Topic
TitleResults for “How to create a CRG?”Also Available in