Messages

Configuration of integrations along with its building blocks can lead to validation error messages. Following is the list of messages that can be expected while configuring.

Message Code	Message Text
OIG-GATE-001	Both errorDestination and functionErrorPayload should be present or absent
OIG-GATE-002	The type for destination {destination_attribute_name} in {resource_name} with code {resource_code} can only be of type(s) {allowed_destination_types}
OIG-GATE-003	The destination for {destination_attribute_name} in {resource_name} with code {resource_code} is mandatory
OIG-GATE-004	Type config is mandatory for type {integration_step_type}
OIG-GATE-005	Type {integration_step_type or destination_type} should have config defined for attributes: {mandatory_type_config_attributes}
OIG-GATE-006	Delivery Type with code {integration_step_code} does not define a valid outputMimeType {output_mime_type}
OIG-GATE-007	Integration Step with code {integration_step_code} and subtype {integration_step_subtype} should define type
OIG-GATE-008	Integration Step with code {integration_step_code} and subtype {integration_step_subtype} should define destination
OIG-GATE-009	Could not resolve function payload {function_payload_code} referred by {target code for integration step or destination}
OIG-GATE-011	For {client id} the HTTP {http method name} on {uri} failed with status code: {http response code} ({reason phrase})
OIG-GATE-012	For {client id} the HTTP {http method name} on {uri} did not result in a response
OIG-GATE-013	URL is not set of address key: {address key in destinations}
OIG-GATE-014	Credentials are not set for credential key: {credential key in destinations}
OIG-GATE-015	For {client id} the SFTP to host {hostname} failed with: {message}
OIG-GATE-016	No session(s) available for agent notification to {agents}
OIG-GATE-017	Could not resolve parameter {parameter to resolve} in {parameter source}
OIG-GATE-018	Ohi Activity invocation was not successful. The response received is {response}
OIG-GATE-019	For {client id} the HTTP {http method name} on {uri} failed with {exception message}
OIG-GATE-020	The entered agent config type {type}, is not one of the supported agent config types: {supported types}
OIG-GATE-021	The keys {keys} are missing for the agent configuration of type {type}
OIG-GATE-022	Invalid definition for user defined sequence {sequence code}
OIG-GATE-023	There are failed sub-exchanges for step {step code} in integration type {integration type code} and code {integration code}
OIG-GATE-024	The integration with type: {integration type} and code {integration code} is currently disabled, exchange creation not allowed at this time
OIG-GATE-025	In {context} the entered value {value} for {key} is not one of the allowed values: {allowed values}
OIG-GATE-026	In {context} the entered value {value} for {key} does not comply with the prescribed pattern: {pattern}
OIG-GATE-027	Exchange with id {0} for integration with type {1} and code {2} timed-out
OIG-GATE-028	Exchange with id {0} for integration with type {1} and code {2} failed
OIG-GATE-029	Exchange with id {0} for integration with type {1} and code {2} has no result
OIG-GATE-030	Exchange with id {0} for integration with type {1} and code {2} has a wrong result payload type
OIG-GATE-031	Type {0} should have config defined for one of these attributes: {1}
OIG-GATE-032	Integration step {step code}: credential key {credential key} is undefined
OIG-GATE-033	Integration step {step code}: authentication method is unknown for credential key {credential key}
OIG-GATE-034	Integration step {step code}: address key {address key} is not defined
OIG-GATE-035	Integration step {step code}: data file access links are incorrect as the base application URL specified by the property {property name} in destination {destination code} is set incorrectly or the destination cannot be accessed
OIG-GATE-036	Integration step {step code}: The credentials cannot be read {credential key} in the interfacing OHI application
OIG-GATE-038	Mandatory invocation parameter {0} is missing value
OIG-GATE-039	Integration Code {0) is unknown
OIG-GATE-041	Exchange with id {0} for integration with type {1} and code {2} and step with code {3} failed in the down stream systems and needs to be recovered
OIG-GATE-042	Exchange with id {0} for integration with type {1} and code {2} received notification in custom format for step type {3}, the system expects custom notification only for Integration Step of type Process.
OIG-GATE-043	Value {0} of invocation parameter {1} is not a {2}
OIG-GATE-044	Integration step {step code}: validation timed out
OIG-GATE-045	Payload marker {0} does not correspond with integration {1}
OIG-GATE-046	Integration with type {0} and code {1} not configured correctly. Expected: {2} but got {3}
OIG-GATE-047	It is not allowed to add a sub flow step with a self referring sub flow
OIG-GATE-048	Integration Step with code {0} and subtype {1} should define attributes {2}
OIG-GATE-049	The original request for {0} has reached its maximum redirect count {1}. The application will not redirect any more. The latest location to redirect is {2}