Flex Python Events Lifecycle Flow - HxGN EAM - 12.0.1 - Feature Briefs - Hexagon

HxGN EAM Python Framework and Flex Python Scripting

Language
English
Product
HxGN EAM
Search by Category
Feature Briefs
HxGN EAM Version
12.0.1

  1. EAM validates that each record contains the necessary required information. Because all records in the table have a Document code whose Python Script Type = Executable, no error will be displayed in the Errors field.

  2. EAM attempts to connect to the Flex Python executable framework API using values in the Flex Python executable framework API URL and Key installation parameters. Because EAM can connect, no error will be displayed in the Errors field for all records to be processed.

  3. EAM will process all remaining records where Status is Not Scheduled, Started, Succeeded, or Returned into the Flex Python execution framework API. These criteria should exclude records that are currently being processed by the API or have completed processing.

  4. This data will be sent to the API for each record:

    1. Document (value from each record)

      1. Parameters 1 – 10 (values from each record)

      2. EAM will set Transmission Date/Time to system date/time if transmission is attempted, overwriting the existing value

  5. EAM will clear Python Executable Job ID, that is, value assigned by Python Flex execution framework API when the record was last received.

  6. As a result of successful transmission, the Flex Python execution framework API will send a Python Execution Job ID back to EAM and the associated event record will be updated as such.

The Status may not be updated immediately upon successful transmission but when the API supplies the initial status value.