Differences

This shows you the differences between two versions of the page.

--- 2500_config_apps:0500_add_edit_objects:0600_intelligent_bo [2026/08/13 03:37] – localdev
+++ 2500_config_apps:0500_add_edit_objects:0600_intelligent_bo [2026/08/13 07:20] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
-{{tag>Config Intelligent_Business_Object Email Outgoing SOAP URL Index}}
+{{tag>Config Intelligent_Business_Object Email Outgoing SOAP URL REST Index}}
 [<10>]
 ====== Defining Intelligent Business Objects ======
@@ Line 33: / Line 33: @@
 To discover services press the Discover button next to the Services table. Discovered services (if any) will be displayed in the Services table. You can now define a process that would call the discovered services using the REQUEST SERVICE action of the //**AwareIM**// Rule Language.
-<callout type="primary" icon="true" title="note"> Business objects declared as service input and reply are automatically added to the business space version once you save the changes for the intelligent business object you are defining or editing.</callout>
+<alert type="primary" icon="fa info-circle">
+**note**
-<callout type="primary" icon="true" title="note"> If the service provider changes definitions of services the services may be re-discovered in the same way as described above. The Configuration Tool will automatically replace all services and business objects declared as service input and replies with the new definitions.</callout>
+ Business objects declared as service input and reply are automatically added to the business space version once you save the changes for the intelligent business object you are defining or editing.</alert>
-==== Setting Properties of the URL Channel =====
+<alert type="primary" icon="fa info-circle">
+**note**
+ If the service provider changes definitions of services the services may be re-discovered in the same way as described above. The Configuration Tool will automatically replace all services and business objects declared as service input and replies with the new definitions.</alert>
+===== Setting Properties of the URL Channel =====
 Communication with an intelligent business object via the URL channel assumes that //**AwareIM**// sends service requests to the specified URL. It is expected that when this URL is called the browser will go to the web site of the service provider. When this web site finishes its task it will return to the //**AwareIM**//-based application, A typical scenario for the URL channel service is a payment system (such as PayPal) that collects credit card details and returns to the web site of the merchant.
@@ Line 119: / Line 125: @@
 If your service provider requires that you provide binary content as a parameter along with some primitive values (for example, text or number) you should specify each parameter in its own part. For example, if you need to provide a binary value and a number, you should define two parts – the first part (binary) should have “application/octet-stream” as Content Type and it should refer to the attribute of some object in Context of the Picture or Document types. The second part should have “text/plain” as Content Type and then refer to some attribute of the Number or Plain Text type.
-<callout type="primary" icon="true" title="note"> If you are referring to the entire object in Context and this object has an attribute of the Picture or Document type, the picture or document will be automatically encoded without you having to define an additional part.</callout>
+<alert type="primary" icon="fa info-circle">
+**note**
+ If you are referring to the entire object in Context and this object has an attribute of the Picture or Document type, the picture or document will be automatically encoded without you having to define an additional part.</alert>
+<alert type="primary" icon="fa info-circle">
+**note**
+ If a provider requires that the value of some attribute is an array of primitive values and you are referring to the entire object in Context, make sure that the value of the “array” attribute is a string that concatenates all array members delimited by the “#” symbol, for example <code aim>Object.Attribute = "Value1#Value2#Value3" </code></alert>
-<callout type="primary" icon="true" title="note"> If a provider requires that the value of some attribute is an array of primitive values and you are referring to the entire object in Context, make sure that the value of the “array” attribute is a string that concatenates all array members delimited by the “#” symbol, for example <code aim>Object.Attribute = "Value1#Value2#Value3" </code></callout>
+<alert type="primary" icon="fa info-circle">
+**note**
-<callout type="primary" icon="true" title="note"> If a provider requires that the value of some attribute is a dictionary and you are referring to the entire object in Context, make sure that the value of the “dictionary” attribute is a string containing pairs of key/values separated by the "|" symbol. Each key/value pair must be separated by the "~" symbol, for example <code aim>Object.Attribute = "Key1~Value1|Key2~Value2|Key3~Value3" </code></callout>
+ If a provider requires that the value of some attribute is a dictionary and you are referring to the entire object in Context, make sure that the value of the “dictionary” attribute is a string containing pairs of key/values separated by the "|" symbol. Each key/value pair must be separated by the "~" symbol, for example <code aim>Object.Attribute = "Key1~Value1|Key2~Value2|Key3~Value3" </code></alert>
 To add a part, click on the “Add” button above the list of the defined parts.

config intelligent business object email outgoing soap url rest index