Partner attribute
note
Modifying this entity requires certain user authorization. For more information, see User Groups.
A Partner attribute allows you to define individual settings to be applied to information going to and coming from a business partner. A Partner attribute may apply to all Node Types, or to a certain Node Type only. The Component definitions check the Partner attributes to direct the processing.
Properties
Partner attribute group
| Name | Type | Description |
|---|---|---|
| CLR-name | String | Specifies the name that will be used to refer to the instance of the entity from Code Expressions in Adapterflows. The CLR-name is automatically generated from the Name property, but can be modified. For details and restrictions, see CLR-name property. |
| Created | DateTime | Date and time when the Partner attribute group was created. Automatically generated by the system. |
| Description | String | Brief description of the Partner attribute group. |
| ID | Guid | The entity ID of the Partner attribute. Automatically generated by the system. |
| Modified | DateTime | Date and time of the latest modification of the Partner attribute group. Automatically generated by the system. |
| Name | String | Name of the Partner attribute group. |
| System Internal | Boolean | Specifies whether the Partner attribute group is a generic system attribute group, or a customized application attribute group created to meet the requirements of the business flows. System groups may only be added by certified iCore personnel. A system internal attribute group cannot be deleted, as it may be used by system scripts. This property is read-only. |
Partner attribute
| Name | Type | Description |
|---|---|---|
| CLR-name | String | Specifies the name that will be used to refer to the instance of the entity from Code Expressions in Adapterflows. The CLR-name is automatically generated from the Name property, but can be modified. For details and restrictions, see CLR-name property. |
| Default Value | Object | The default value of the attribute, which is automatically set when the group is added to a Partner. The default value is used if no other value has been entered specifically. |
| Description | String | Brief description of the Partner attribute. |
| Mandatory | Boolean | Specifies whether the Partner attribute is mandatory. |
| Modified | DateTime | Date and time of the latest modification of the Partner attribute. |
| Name | String | Name of the Partner attribute. |
| Node type | INodeType | Specifies whether the attribute applies to a certain Node type. |
| Parameter type | ScriptVarType | Specifies the parameter type of the attribute value. Available types are String, Integer and Float. |
| System Internal | Boolean | Specifies whether the entity is a built-in system entity (True) or a customized application entity created to meet the requirements of the business flows (False). A system entity is read-only and cannot be deleted since it may be used by system script(s). New system entities can only be added by certified iCore personnel. |
| Entity type | EntityType | Specifies the entity type. The property is Read-only and is only displayed in filter listings to identify the entity type. It can be used for example when filtering on entities with a filter containing an 'All' part. For more information, see Entity filters. |
| Protected | Boolean | Specifies whether values of this attribute type are protected or not. The property applies to the Partner attribute value and the default value of the attribute. See also Data protection. |
Default value property
If a Partner attribute value is missing when a Script performs Get Attribute Value, the default value must be managed from the Script.
Remarks
Examples of attributes are communication program, communication setting, EDI-code and virtual filename.
When defining a Partner Attribute, you start by creating a Partner attribute group. You then add the individual attributes to the group. An individual Partner attribute must belong to a group.
The Partner attribute groups are used when configuring Partners. An example of a typical attribute group is “SMPT receiver”. An attribute group naturally contains attributes. Below you find an example of attributes that can be found in an attribute group called “SMPT receiver”. As shown in the image, an attribute may be Node type specific.
The information (attributes) connected to the Partner is used by Components. If a Component requires certain information from a Partner, the creator of the Component usually defines the required Attribute groups, but this procedure may vary from company to company.
When configuring a Partner you select from a list of Partner attribute groups. This procedure is analogous with the procedure of installing and configuring a network protocol in a computer and should thus be familiar to most system administrators.
If no attributes groups are set to a Partner, the Component definitions will use default values.