Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Access Policy transformation
  6. Aggregator transformation
  7. B2B transformation
  8. Chunking transformation
  9. Cleanse transformation
  10. Data Masking transformation
  11. Data Services transformation
  12. Deduplicate transformation
  13. Expression transformation
  14. Filter transformation
  15. Hierarchy Builder transformation
  16. Hierarchy Parser transformation
  17. Hierarchy Processor transformation
  18. Input transformation
  19. Java transformation
  20. Java transformation API reference
  21. Joiner transformation
  22. Labeler transformation
  23. Lookup transformation
  24. Machine Learning transformation
  25. Mapplet transformation
  26. Normalizer transformation
  27. Output transformation
  28. Parse transformation
  29. Python transformation
  30. Rank transformation
  31. Router transformation
  32. Rule Specification transformation
  33. Sequence transformation
  34. Sorter transformation
  35. SQL transformation
  36. Structure Parser transformation
  37. Transaction Control transformation
  38. Union transformation
  39. Vector Embedding transformation
  40. Velocity transformation
  41. Verifier transformation
  42. Web Services transformation

Transformations

Transformations

Dynamic service name

Dynamic service name

Use a dynamic service name with the Data Services transformation to process messages for message types from different standards and usage types. When you use a dynamic service name, you pass the data service names to the transformation as parameters.
The name of a data service indicates the industry standard, the version of the standard, the message type, and the service usage type, in the following syntax:
<industry standard>_<version>_<message type>_<usage type>
The usage type can be one of the following types:
  • Parser. Use a parser service to receive messages from your partners.
  • Serializer. Use a serializer service to send messages to your partners.
  • Restricted serializer. Use a restricted serializer service to send messages to your partners, including validation messages. Applies to HIPAA messages.
For example, the name of the service you use to receive HIPAA message 270 version 5010A1 is HIPAA_5010A1_270_Parser.
To use a dynamic service name, complete the following tasks when you configure the mapping:
  1. Configure the mapping to pass the data service names to the Data Services transformation as parameters. For example, add an Expression transformation to the mapping and configure the Expression transformation to extract the data service names from the messages and pass the names to the Data Services transformation.
  2. When you configure Data Services properties, select the option to use a dynamic service name.
  3. In the field mapping of the Data Services transformation, map the incoming field that contains the service name to the service_Name field.

Using the Message Discovery Service

When you use a dynamic service name, you can optionally enable the Message Discovery Service. It detects the name of a parser data service from the upstream transformation and invokes the parser data service from the data services repository.
To use the Message Discovery Service, complete the following tasks when you configure the mapping:
  1. Add an Expression transformation to the mapping that receives incoming messages.
  2. In the Expression transformation, create an expression field to pass an empty string to the Data Services transformation.
  3. In the Data Services transformation, select the option to use a dynamic service name. Then, enable the Message Discovery Service and select the mode and type.
  4. In the field mapping of the Data Services transformation, map the incoming expression field with the empty string to the service_Name field.
The Message Discovery Service only detects the names of parser data services. It doesn't detect the names of serializers or restricted serializers.

0 COMMENTS

We’d like to hear from you!