Settings

Group	Key	Description
INCONTEXT	attribute.mappings	Utilized for mapping Infor PIM attributes to the Incontext widget, facilitating the display of Infor PIM attributes within the Incontext widget interface. The mapping format follows the convention [Incontext attribute ID]=[PIM attribute ID], while using commas as delimeters to separate multiple mappings within the list.
ION	oauth.token.url	Determines the URL for calling the authorization server, which is used to generate access tokens. To specify information in this field, combine the <pu> value appended with the <ot> value. You can obtain these values from the API Gateway credentials file. Download the file from Infor API Gateway, which you can access from Infor OS Portal or Infor Ming.le.
ION	rrs.client.id	Enables the application to issue requests for access tokens to the authorization server. To specify information in this field, get the client identifier <ci> value from the API Gateway credentials file. Download the file from Infor API Gateway, which you can access from Infor OS Portal or Infor Ming.le.
ION	rrs.client.secret	Enables the application to issue requests for access tokens to the authorization server. To specify information in this field, get the client secret <cs> value from the API Gateway credentials file. Download the file from Infor API Gateway, which you can access from Infor OS Portal or Infor Ming.le.
ION	rrs.service.account.access.id	Authenticates issued requests for access tokens to the authorization server. To specify information in this field, get the service account access key <saak> value from the API Gateway credentials file. Download the file from Infor API Gateway, which you can access from Infor OS Portal or Infor Ming.le
ION	rrs.service.account.secret.key	Authenticates issued requests for access tokens to the authorization server. To specify information in this field, get the service account secret key <sask> value from the API Gateway credentials file. Download the file from Infor API Gateway, which you can access from Infor OS Portal or Infor Ming.le
Infor AI	service.endpoint	Specify the endpoint for Infor AI Platform
Infor AI	item-item.similarity.endpointname	Specify the endpoint name of item-item similarity recommendation type. The endpoint name may vary depending on your tenant's Infor AI Platform setup. By default, Recommendations_Upsell is set to item-item.similarity.endpointname
Infor AI	user-user.similarity.endpointname	Specify the endpoint name of item-item similarity recommendation type. The endpoint name may vary depending on your tenant's Infor AI Platform setup. By default, Recommendations_CrossSell is set to user-user.similarity.endpointname.
Infor AI	input.params.mapping	Specify the mapping of RRS parameter names and their equivalent Infor AI Platform parameters. This field maps the parameters used by the integrating applications. The input.params.mapping use this format : <RRS parameter name>=<equivalent of that parameter in Infor AI Platform> By default, the defined values are itemNumber=ItemNumber, and userGroupId=Customer.
Infor AI	output.params	Specify the parameters that will be returned by Infor AI Platform. As of now, ItemNumber is only supported by RRS. Note: It is important to define the expected parameters that will be returned by Infor AI Platform in their proper sequence and name for RRS to correctly read the response.
Localization	default.locale	Determines the default language/locale used within the application. When users access the application for the first time or have not explicitly selected a language preference, this default locale will be applied. The input for this setting is a locale code following the format [language]-[region], such as 'en-US' for English (United States) or 'fr-FR' for French (France)
Localization	enabled.locales	Specifies the list of enabled locales within the application. Commas are used as delimiters to separate individual locale codes within the list.
Ming.le	mingle.domain	If you use the on-premises version of Infor Ming.le, use the mingle.domain setting to specify the URL of the on-premises environment.
Ming.le	mingle.cookie-domain	Do not change the value in the mingle.cookie-domain setting. This value is the domain of the common cookie that Infor Ming.le uses for session timeout in different applications in the suite.
PIM	api.bod.url	Specifies the URL for the Inriver BOD REST API. Serves as the endpoint for accessing and interaccting with Inriver PIM.
PIM	api.access.id	Specifies the ID used to authenticate with the Inriver BOD REST API.
PIM	api.access.key	Specifies the Key used to authenticate with the Inriver BOD REST API.
PIM	vendor.idAI	Specifies the PIM solution used for the tenant. It only accepts the value "INFOR_PIM" to enable the setting, indicating that Infor PIM is the designated PIM solution within the environment.
PIM	bod.process.max.retry	Determines the maximum number of retries for BOD replication processes if last attempt has failed.
PIM	default.entitytype.id	Specifies the default entity type used for replicating entities from ERP to Infor PIM. The specified entity type ID will be used when there are no entity types that match the entity type BOD mapping from a sync.ItemMaster BOD
PIM	locale.mapping	Enables the mapping of language codes from the ERP system to locale codes in the PIM system, facilitating the translation of attributes across platforms. The mapping format follows the convention [ERP language code]=[PIM locale code], while using commas as delimeters to separate multiple mappings within the list.
PIM	enabled.accounting-entity-ids	Specifies the accounting entities that are enabled within Infor PIM. Multiple accounting entity IDs can be listed, separated by commas, allowing for the inclusion of various organizational units or divisions.
PIM	enabled.item-relationship-types	Specifies the item relationship types (item cross-reference types) that are enabled within Infor PIM. By configuring this setting, users can define which relationship types are active and available for use within Infor PIM. Inputs for this setting are relationship type (item cross-reference) IDs, with multiple relationship types separated by commas. The list of enabled item cross-reference types configured in this setting will be utilized to populate a dropdown menu inside the relationship attribute panel.

INCONTEXT

attribute.mappings

Utilized for mapping Infor PIM attributes to the Incontext widget, facilitating the display of Infor PIM attributes within the Incontext widget interface. The mapping format follows the convention [Incontext attribute ID]=[PIM attribute ID], while using commas as delimeters to separate multiple mappings within the list.

ION

oauth.token.url

Determines the URL for calling the authorization server, which is used to generate access tokens. To specify information in this field, combine the <pu> value appended with the <ot> value. You can obtain these values from the API Gateway credentials file. Download the file from Infor API Gateway, which you can access from Infor OS Portal or Infor Ming.le.

ION

rrs.client.id

Enables the application to issue requests for access tokens to the authorization server. To specify information in this field, get the client identifier <ci> value from the API Gateway credentials file. Download the file from Infor API Gateway, which you can access from Infor OS Portal or Infor Ming.le.

ION

rrs.client.secret

Enables the application to issue requests for access tokens to the authorization server. To specify information in this field, get the client secret <cs> value from the API Gateway credentials file. Download the file from Infor API Gateway, which you can access from Infor OS Portal or Infor Ming.le.

ION

rrs.service.account.access.id

Authenticates issued requests for access tokens to the authorization server. To specify information in this field, get the service account access key <saak> value from the API Gateway credentials file. Download the file from Infor API Gateway, which you can access from Infor OS Portal or Infor Ming.le

ION

rrs.service.account.secret.key

Authenticates issued requests for access tokens to the authorization server. To specify information in this field, get the service account secret key <sask> value from the API Gateway credentials file. Download the file from Infor API Gateway, which you can access from Infor OS Portal or Infor Ming.le

Infor AI

service.endpoint

Specify the endpoint for Infor AI Platform

Infor AI

item-item.similarity.endpointname

Specify the endpoint name of item-item similarity recommendation type. The endpoint name may vary depending on your tenant's Infor AI Platform setup.

By default, Recommendations_Upsell is set to item-item.similarity.endpointname

Infor AI

user-user.similarity.endpointname

Specify the endpoint name of item-item similarity recommendation type. The endpoint name may vary depending on your tenant's Infor AI Platform setup.

By default, Recommendations_CrossSell is set to user-user.similarity.endpointname.

Infor AI

input.params.mapping

Specify the mapping of RRS parameter names and their equivalent Infor AI Platform parameters. This field maps the parameters used by the integrating applications.

The input.params.mapping use this format : <RRS parameter name>=<equivalent of that parameter in Infor AI Platform>

By default, the defined values are itemNumber=ItemNumber, and userGroupId=Customer.

Infor AI

output.params

Specify the parameters that will be returned by Infor AI Platform. As of now, ItemNumber is only supported by RRS.

Note: It is important to define the expected parameters that will be returned by Infor AI Platform in their proper sequence and name for RRS to correctly read the response.

Localization

default.locale

Determines the default language/locale used within the application. When users access the application for the first time or have not explicitly selected a language preference, this default locale will be applied. The input for this setting is a locale code following the format [language]-[region], such as 'en-US' for English (United States) or 'fr-FR' for French (France)

Localization

enabled.locales

Specifies the list of enabled locales within the application. Commas are used as delimiters to separate individual locale codes within the list.

Ming.le

mingle.domain

If you use the on-premises version of Infor Ming.le, use the mingle.domain setting to specify the URL of the on-premises environment.

Ming.le

mingle.cookie-domain

Do not change the value in the mingle.cookie-domain setting. This value is the domain of the common cookie that Infor Ming.le uses for session timeout in different applications in the suite.

PIM

api.bod.url

Specifies the URL for the Inriver BOD REST API. Serves as the endpoint for accessing and interaccting with Inriver PIM.

PIM

api.access.id

Specifies the ID used to authenticate with the Inriver BOD REST API.

PIM

api.access.key

Specifies the Key used to authenticate with the Inriver BOD REST API.

PIM

vendor.idAI

Specifies the PIM solution used for the tenant. It only accepts the value "INFOR_PIM" to enable the setting, indicating that Infor PIM is the designated PIM solution within the environment.

PIM

bod.process.max.retry

Determines the maximum number of retries for BOD replication processes if last attempt has failed.

PIM

default.entitytype.id

Specifies the default entity type used for replicating entities from ERP to Infor PIM. The specified entity type ID will be used when there are no entity types that match the entity type BOD mapping from a sync.ItemMaster BOD

PIM

locale.mapping

Enables the mapping of language codes from the ERP system to locale codes in the PIM system, facilitating the translation of attributes across platforms. The mapping format follows the convention [ERP language code]=[PIM locale code], while using commas as delimeters to separate multiple mappings within the list.

PIM

enabled.accounting-entity-ids

Specifies the accounting entities that are enabled within Infor PIM. Multiple accounting entity IDs can be listed, separated by commas, allowing for the inclusion of various organizational units or divisions.

PIM

enabled.item-relationship-types

Specifies the item relationship types (item cross-reference types) that are enabled within Infor PIM. By configuring this setting, users can define which relationship types are active and available for use within Infor PIM. Inputs for this setting are relationship type (item cross-reference) IDs, with multiple relationship types separated by commas. The list of enabled item cross-reference types configured in this setting will be utilized to populate a dropdown menu inside the relationship attribute panel.