BODFromEAM_V2

BODFromEAM_V2 connects to HxGN EAM’s Databridge, retrieving all outbound BOD messages published for the tenant. A flowfile is created for each message retrieved. The flowfile content is not re-formatted or validated during retrieval.

Properties

• (BOD Types): Supported EAM BODs are listed as a separate ‘BOD Type’ properties (e.g., Sync.AssetMasster), which can be set to true or false. When ‘true,’ the processor creates a relationship for that BOD type to route them accordingly.

Relationships

• (BOD Type): Relationship is created for each BOD Type property set to ‘true.’ A flowfile is created from each message retrieved from EAM Databridge and routed according to the appropriate relationship.

• Unmatched: Flowfiles created which do not match any available BOD Type relationship are transferred to this relationship. This includes Confirm or Acknowledgement, as well as any BOD message received which BOD Type property set to ‘false.’

Attributes

• databridge.contentType: reflects the publication format (json or xml) sent from HxGN EAM’s Databridge.

• bodType : reflects the BOD Type sent from HxGN EAM’s Databridge (ex. Sync.Requisition).

Publication format is controlled within the HXGN-DFS partner record in HxGN EAM. See EAM documentation for more details.

Usage

BODFromEAM_V2 should only be used once within a tenant canvas, as it reads all outbound messages published by EAM Databridge. Multiples of BODFromEAM_V2 will cause unintended outcomes and behaviors.

For better organization and manageability, it is recommended to connect all relationships from BODFromEAM_V2 to separate process groups that contain specific flows for each BOD type as well as handling for any unmatched flowfiles.