Service profiles
To create a service profile you must specify an endpoint, a request method, and a response format. The service profile makes a call to the service, passes the appropriate request body, gets a response, and maps it to objects.
For example, service profiles can be used to validate data against external sources that are only accessible via the web, or to update external systems that accept web requests.
Service profiles also integrate with the AutoComplete functionality in Operations and Regulations, providing a mechanism for fetching AutoComplete suggestion data.
See Using an external service.
After they are defined, service profiles can be used in different ways. When using a service profile for AutoComplete, you specify the service profile name in the AutoComplete configuration. You can also use service profiles in formulas to make requests to external services.
Formulas that call external services use the Hansen.Core.Net.NetService object. You can also use this object to call an external service programatically, without using a service profile.
See Calling external services.
customer notes from HPS-137642
Currently, our ServiceProfile only supports sending text-based payloads (e.g., JSON, XML, form data) when invoking external services. Customers have requested the ability to send binary data (e.g., images, PDFs, ZIP files, or other binary attachments) as part of outbound requests.
This story adds support for sending binary payloads through ServiceProfile, allowing integrations with external services that require binary uploads (such as file or image endpoints).
Standard content: Service Profile – Add support for binary data
This enhancement allows ServiceProfile to send binary data, such as images or PDF files, in outbound requests, enabling integration with external services that require binary uploads.
ServiceProfile now supports sending binary payloads in outbound POST, PUT, and PATCH requests. Users can specify the content type (such as application/octet-stream, image/png, or application/pdf) and source the binary data from a file reference, a base64-encoded string, or a binary stream from another service or variable. The system ensures that binary data is transmitted as raw bytes without corruption or re-encoding, and that appropriate headers (Content-Type and Content-Length) are set automatically. This improvement enables customers to integrate with APIs that require file or image uploads.