While performing an import, if a member is added or removed from an organization, an email is triggered, notifying you of the new status. To trigger emails during the import, send the specific email template as a parameter in the request payload. The following example shows how you would identify using an organization_assigned template:

{
  "fileName": "accountImport.json",
  "id": "Accounts",
  "format": "json",
  "mode": "standalone",
  "params": {
    "memberAssignmentEmailTemplate": "organization_assigned_v1"
  }
}
Account email triggers in multiple site environments

When working in a multiple site environment, an email is triggered during import that contains all of the site URLs related to the account and profile. Note that up to five sites are listed per account. Additionally, account changes, role updates, approval information, and password information is also included in the email, if applicable. All event information is displayed in a table that identifies the changes that occurred.

When you add a new member to an organization, an email with the name of previous organizations and roles, if any, are added.

Work with sub-accounts

Sub-accounts can be created and updated using the parentOrganization field. An account can have a single parent account, as well as its own sub-accounts. A principal account, or one that does not have any parent account, cannot inherit any properties. There is no fixed number of account hierarchy levels.

Sub-accounts can inherit the following derived organization properties if the sub-accounts properties are not specifically designed:

Sub-accounts can be moved under other accounts if there are no circular references between the accounts. Additionally, a sub-account cannot be set to a parent account of itself. Each sub-account should have its ancestor organization details updated to provide account information. Note that a root account cannot be associated to another account either as a parent account or as a sub-account.

When working with shipping and payment methods in a sub-account and site pair, the sub-account-based methods and the use of site- based methods are either both inherited or not inherited. For example, the sub-account shipping methods and the use of all site shipping methods properties are both inherited together and cannot be inherited individually. The inherited state of the these sub-account and site pairs are determined by the Boolean properties useAllShippingMethodsFromSite and useAllPaymentMethodsFromSite . The values used in the API will override those set in the UI.


Copyright © 1997, 2017 Oracle and/or its affiliates. All rights reserved. Legal Notices