Skip Headers

Oracle iStore Implementation and Administration Guide
Release 12.1
Part Number E13575-06
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

Customer Application Process Flows

This chapter covers the following topics:

Overview of Customer Application Process Flows Chapter

This chapter contains process flows for the Customer Application of Oracle iStore.

Note: Many of the flows depicted in this appendix display functionality that is only enabled if B2B users have specific permissions in their user roles. See the appendix, Seeded User Data, for information about the B2B permissions.

Process Flow for Specialty Sites

The flow through your specialty sites must follow a certain path, as shown in the following top-level diagram and related detail diagrams. Oracle iStore provides templates you can use for the pages illustrated in the diagrams. For more information, see the following chapters or appendices.

Process Flow for Specialty Sites

  1. Users enter the site and browse through the catalog, optionally searching for items.

  2. Users add items to the shopping cart and then check out with the cart to place an order.

  3. Users can also retrieve saved and shared shopping carts and quotes, as well as shopping lists using the Cart menu.

  4. From the shopping cart, pressing the Continue Shopping button takes users back to the Site Home Page.

  5. Users can select Profile to set their preferences, access their address data, and reset their passwords. B2B users can access company information if the administrator has enabled it.

  6. Users can also retrieve their account information --- including orders, invoices, payment information --- by accessing the Orders menu.

  7. The checkout process takes users to the confirmation page. For more information, see the "Orders Business Flow" in the chapter, Implementing Carts and Orders.

  8. Users can select Express Checkout to omit the shopping cart and checkout process; express checkout orders are picked up by a concurrent program and submitted automatically. For more information, see the "Express Checkout" section in the chapter, Implementing Carts and Orders.

The following graphic depicts this flow.

Process Flow for Specialty Sites

the picture is described in the document text

Process Flow for Product Search

Product search capability from the Site Home Page allows users to locate products by various criteria, if the administrator has enabled this functionality. Users also can browse through sections to locate products.

Process Flow for Product Search

  1. Users enter the site at the Site Home Page. Users view groupings of products within sections, and can navigate through the sections to find products.

  2. From the Site Home Page, users can conduct a Simple or Advanced search to find products.

  3. In the search Results page, users may select a product to review detailed product information.

  4. Users can Add to Cart and perform Express Checkout (if enabled) from section and product detail pages.

The following graphic illustrates this flow.

Process Flow for Product Search

the picture is described in the document text

Process Flows for Shopping Carts

The diagram and related text in this section show the shopping cart flows for the Actions drop-down menu as well as other flows available from the shopping cart. See the related detail flows for more information:

High-Level Process Flow for Shopping Cart

The Shopping Cart page features an Actions LOV that allows customers to perform various cart activities. To engage the action, the customer must press the Go button after selecting it. Following are the actions available from the Shopping Cart page:

The following diagram depicts this flow.

Shopping Cart - Actions Menu Flows

the picture is described in the document text

Shopping Cart Flows: Other Than from Actions Menu

From the Shopping Cart page, users can perform several activities in addition to those available from the Actions menu. These other activities include:

The following diagram depicts these activities.

Shopping Cart - Flows Other Than From Actions Menu

the picture is described in the document text

Process Flow for Saving Carts

Users can save a shopping cart at any time by selecting Save Cart action from the Shopping Cart page (this is the active cart).

Oracle iStore automatically saves carts with default names, if the user does not explicitly save them. See the chapter, Implementing Carts and Orders, for more information.

  1. Users select the Save Cart action in the Shopping Cart page.

  2. If the user saves the cart and the cart does not yet have a user-defined name, after selecting Save Cart, the user can either create a new saved cart or add items to an existing cart.

  3. Oracle iStore displays a confirmation message when the cart is saved.

  4. Users can then press the Continue Shopping button to continue browsing the specialty sites.

  5. To retrieve saved carts, users navigate to the Carts page within the Cart menu. In the Saved Carts area of the page, users can select several actions (Update, Express Checkout, Share, Duplicate, Delete) to perform with the cart, or can select the cart name hyperlink to retrieve the Saved Cart Details page.

  6. From the Saved Cart Details page, users can select identical actions as are available from the Saved Carts area.

  7. To activate and potentially modify the cart, the user must select the Update action. The cart then becomes the active cart, and the page is named Shopping Cart.

For more information on cart actions, see the "Common Shopping Cart Elements" section in the chapter, Implementing Carts and Orders.

The following diagram illustrates this process flow.

Cart Saving Process Flow

the picture is described in the document text

Process Flow for Cart Sharing and Retrieval

Share cart functionality is available for both B2B and B2C users, and can be controlled by setting a profile option.

  1. Users can select the Share Cart action in the cart to share the cart with other users at any time.

  2. Users then select or enter cart members.

  3. Users select roles for the members and apply the selections. Oracle iStore displays a confirmation page.

  4. Shared cart members receive an e-mail with instructions detailing how to access the shared cart.

  5. To retrieve the shared cart, users can either select the URL hyperlink in the e-mail notification or navigate to the Carts page, where they can select the shared cart name hyperlink (B2B users) or enter the shared cart retrieval number (B2C users).

  6. B2B members with specific roles can then re-share the cart with other members. B2C users must be the cart owner to re-share a cart.

The following figure depicts this flow.

Cart Sharing and Retrieval Process Flow

the picture is described in the document text

Process Flow for Shopping Lists

Shopping lists enable users to store items that they may wish to purchase or that they purchase repeatedly.

  1. The user selects the Save to List action in the Shopping Cart page.

  2. The system prompts the user to enter a new name for the list or to merge the items to an existing list (if one exists).

  3. Optionally, the user can enter comments for the list in the Comments textbox.

  4. To retrieve a shopping list, the user navigates to the Shopping Lists page within the Cart menu, and selects the hyperlink of the a list name. The Shopping List Details page appears.

  5. To add items to the current, active cart, in the Shopping List Details page, the user selects the appropriate items in the shopping list and selects the Add to Cart action.

  6. To add items to an existing list, the user selects the appropriate items in the shopping list and selects the Add to List action.

  7. Optionally, in the Shopping List Details page, the user can also:

The following diagram illustrates this flow.

Shopping Lists Process Flow

the picture is described in the document text

Carts Page Process Flow

The Carts page within the Cart menu is the entry point for most of the actions that users can perform with carts. The following diagram shows the actions from the Carts page.

For the Quotes page flow, see the Quotes Page Process Flow in this chapter.

See the chapter, Implementing Carts and Orders, for additional details.

The following diagram illustrates this flow.

Carts Page Process Flow

the picture is described in the document text

Quotes Page Process Flow

The Quotes page within the Cart menu is the entry point for quote-related activities. Quotes can originate from:

Note that you must integrate with Oracle Quoting to achieve this functionality.

Published quotes and quotes created through the sales representative assistance feature become saved quotes and are shown in the Published Quotes area of the Quotes page. See the chapter, Integrating Oracle iStore with Oracle Quoting, for more information about quote publishing, and the chapter, Implementing Customer Assistance, for more information about the Sales Assistance flows.

Note that this flow assumes the Update Quote feature is not enabled. If this feature is enabled and a quote is in Draft status, users can press Update Quote in the Quote Details page to retrieve the Shopping Cart page. See the Update Quote Process Flow and the shopping carts flows in this chapter for more information.

  1. To view a list of published or shared quotes, both B2B and B2C registered users select the Cart icon in the Customer UI, and then select the Quotes subtab.

  2. The main sections on the Quotes page are:

  3. To access quote details, the user selects a quote name hyperlink.

  4. In the Quote Details page, users can view details of a quote and update payment type information for the quote before checking out.

  5. In the Quote Details page for a shared quote, the actions the users can perform depend upon their shared cart roles. For more information, see the chapter, Implementing Carts and Orders.

The following diagram shows this flow.

Quotes Page Process Flow

the picture is described in the document text

Update Quote Process Flow

By default, users are only able to update the payment type on a quote published in the Customer Application. Of course, they can always check out with a quote if the quote status allows it. Implementers can allow users to perform normal update cart actions with a published quote when retrieving the Shopping Cart page for a quote. See the chapter, Integrating Oracle iStore with Oracle Quoting, for implementation information.

See also: Implementing Carts and Orders

  1. A B2B or B2C registered user selects the Cart icon in the Customer Application, and then selects the Quotes subtab.

  2. The user selects a quote name hyperlink to retrieve the Quote Details page. Note that this flow covers shared carts as well.

  3. If the update quote feature is enabled, the Update Quote button in the Quote Details page allows access to the Shopping Cart page, where the user can perform normal cart actions.

  4. To allow updating, Oracle iStore also requires that a quote be in Draft status in Oracle Quoting.

The following diagram illustrates this flow.

Update Quote Process Flow

the picture is described in the document text

High-Level Process Flow for B2B Checkout

B2B customers who are ready to place their orders navigate to the checkout phase, where they enter shipping and payment information.

Note: The flows in this section assume neither Express Checkout nor Smart Checkout are enabled and that there are shippable items in the cart (no shippable items means the shipping information step is eliminated).

In addition to the high-level process flow for B2B customers checkout, also refer to the following flows:

The following is the high-level process flow for B2B checkout:

  1. When B2B customers proceed to checkout by pressing the Checkout button, they begin in the Checkout: Shipping Information page, where they enter shipping information. Note that B2B users must have the IBE_CHECKOUT permission to access the Checkout button.

  2. Customers then proceed to the Checkout: Billing and Payment Information page, where they enter payment and billing information for the order.

  3. Customers then proceed to the Checkout: End Customer Information page (if this feature is enabled), where they enter end customer information.

  4. Next, customers proceed to the Checkout: Terms and Conditions page (if this feature is enabled), where they agree to the terms and conditions of the order. Customers can review/reject terms and conditions; for information about rejecting terms and conditions, see the chapter, Implementing Carts and Orders.

  5. The final page in the checkout flow is the Checkout: Review and Place Order page, where customers can place the order by selecting the Place Order button. Note that B2B customers must have the IBE_CREATE_ORDER permission in their user role to access the Place Order button.

  6. After placing the order, users can select Continue Shopping to browse the specialty sites and potentially add more items to shopping carts.

If customers request sales representative assistance in the checkout flow, they must select a reason for requesting assistance and optionally can enter comments in the How can we assist you in finalizing your order? page. If the cart is unsaved, the user must enter a cart name. After submission, the cart becomes a quote. Note that B2B users must have the IBE_ASK_SALES_ASSISTANCE permission in their user roles to be able to request sales assistance. For more information on Sales Assistance, refer to the chapter, Implementing Customer Assistance.

See also: "Checkout Flow Pages" in the chapter, Implementing Carts and Orders

The following diagram illustrates this flow.

High-Level Process Flow for B2B Checkout

the picture is described in the document text

B2B Shipping Information Process Flow

B2B customers can change and create the ship-to customer, contact or address for an order at checkout, if they have the required permissions.

  1. From the Checkout: Shipping Information page and the Update Item Shipping Information pages, B2B customers (with the required user role permissions) can change the ship-to customer, contact, or address.

  2. If customers choose to change the ship-to customer, the Search and Select: Ship to Customer page is displayed, where customers can search for and select from a list of other ship-to users within their organization. When finished, they return to the Checkout: Shipping Information page.

    Customers with the required user permissions can also create a new ship-to customer from the Search and Select: Ship to Customer page. In this case, the Create Customer page is displayed, where customers enter information to create the ship-to user. When finished, they return to the Checkout: Shipping Information page.

  3. If customers choose to change the ship-to contact, the Search and Select: Ship to Contact page is displayed. In the Search and Select: Ship to Contact page, users can search for and select another ship-to contact from within their organization. When finished, they return to the Checkout: Shipping Information page.

  4. Customers with the required user permissions can also create a new ship-to contact from the Search and Select: Ship to Contact page. In this case, the Create Contact page is displayed, where users enter information to create the ship-to contact. When finished, they return to the Checkout: Shipping Information page.

  5. If customers choose to change the ship-to address, the Search and Select: Ship to Address page is displayed. In the Search and Select: Ship to Address page, customers can search for and select a ship-to address. When finished, they return to the Checkout: Shipping Information page.

  6. Customers with the required customers permissions can also create a new ship-to address from the Search and Select: Ship to Address page. In this case, the Create Address page is displayed, where customers enter ship-to address information. When finished, they return to the Checkout: Shipping Information page.

  7. When finished with the shipping information entry, customers continue to the Checkout: Billing and Payment Information page.

For permissions details, see the chapter, Implementing Carts and Orders, and the appendix, Seeded User Data.

The following diagram depicts this flow.

Process Flow for Changing B2B Shipping Information

the picture is described in the document text

Ship to Multiple Locations Process Flow

During checkout, customers can enter separate shipping information for different items in their shopping carts, if the administrator has enabled this ability (see the section, "Allowing Item-Level Shipping", in the chapter, Implementing Payment Types and Shipping Methods).

  1. From the Checkout: Shipping Information page, B2B customers can enter separate shipping information for different items in their shopping carts by accessing the Ship to Multiple Locations area of the Checkout: Shipping Information page.

  2. If a customer has ordered more than one quantity of a single item, the items can be split to specify different shipping information for each duplicate item. From the Ship to Multiple Locations area of the Checkout: Shipping Information page, customers select the Split Quantity icon to retrieve the Split Quantity page. In the Split Quantity page, customers separate the quantities onto separate lines. When they finish splitting the line items, they return to the Checkout: Shipping Information page, with the items split into different rows in the Ship to Multiple Locations area of the page. From this area, customers select items to modify, as described below.

  3. To update the shipping details of a specific item, customers select the item and press the Update Shipping Information button; this retrieves the Update Item Shipping Information page for the selected item. From the update page, users can:

  4. When finished changing item-level shipping information, the customer returns to the Checkout: Shipping Information page.

  5. The customer proceeds to the billing information phase.

The following diagram shows the flow.

Process Flow for Item-Level Shipping Information

the picture is described in the document text

B2B Billing Information Process Flow

B2B customers can change and create the bill-to user, contact, and address at checkout if they have the required permissions.

  1. From the Checkout: Billing and Payment Information page and the Update Item Billing and Payment Information page, customers can choose to change the bill-to customer, contact, or address (assuming they have the appropriate role permissions).

  2. If customers choose to change the bill-to customer, the Search and Select: Bill to Customer page is displayed, where they can search for and select a new bill-to customer.

    Customers with the required user permissions can also create a new bill-to customer from the Search and Select: Bill to Customer page. In this case, the Create Customer page is displayed, where customers enter information to create the bill-to user. When finished, they return to the Checkout: Billing and Payment Information page or the Update Item Billing and Payment Information page.

  3. If customers choose to change the bill-to contact, the Search and Select: Bill to Contact page is displayed, where they can search for and select a new bill-to contact.

    Customers with the required user permissions can also create a bill-to contact from the Search and Select: Bill to Contact page. In this case, the Create Contact page is displayed. When finished, they return to the Checkout: Billing and Payment Information page or the Update Item Billing and Payment Information page.

  4. If customers choose to change the bill-to address, the Search and Select: Bill to Address page is displayed, where they can search for and select a new bill-to address.

    If customers choose to create a bill-to address from the Search and Select: Bill to Address page, the Create Address page is displayed. When finished, they return to the Checkout: Billing and Payment Information page or the Update Item Billing and Payment Information page.

  5. Customers continue to the next page in the checkout flow. See the "High-Level Process Flow for B2B Checkout" above, for the options available within the checkout flow.

For permissions details, see the chapter, Implementing Carts and Orders, and the appendix, Seeded User Data.

The following diagram illustrates this flow.

Process Flow for B2B Billing Information

the picture is described in the document text

Bill to Multiple Locations Process Flow

During checkout, B2B customers can enter separate billing information for different items in their shopping carts, if this functionality has been enabled (see the section, "Setting up Item-Level Billing", in the chapter, Implementing Payment Types and Shipping Methods).

Note: Payment type must be Cash or Invoice to use item-level billing. Also, when using line level billing, Purchase Order is not supported.

  1. B2B customers can enter separate billing information for different items in their shopping carts by accessing the Bill to Multiple Locations area of the Checkout: Billing and Payment Information page, B2B customers can enter separate billing information for different items in their shopping carts, if this functionality has been enabled.

  2. If a customer has ordered more than one quantity of a single item, the items can be split to specify different billing information for each duplicate item. From the Bill to Multiple Locations area of the Checkout: Billing and Payment Information page, customers select the Split Quantity icon to retrieve the Split Quantity page. In the Split Quantity page, customers separate the quantities onto separate lines. When they finish splitting the line items, they return to the Checkout: Billing and Payment Information page, with the items split into different rows in the Bill to Multiple Locations area of the page. From this area, customers select items to modify, as described below.

  3. To update the billing details of a specific item, customers select the item and press the Update Billing Information button; this retrieves the Update Billing and Payment Information page for the selected item. From the update page, users can change/create bill-to customer, contact, and address (assuming the update/create bill-to permissions are in their user roles).

  4. When finished changing item-level billing information, the customer returns to the Checkout: Billing and Payment Information page, where they continue with checkout.

The following diagram shows the flow.

Bill to Multiple Locations Process Flow

the picture is described in the document text

Process Flow for B2C Checkout

B2C customers who are ready to place their orders go to the checkout area of the site, where they enter shipping and payment information.

  1. When a B2C customer chooses to check out, the Checkout: Shipping and Billing page is the first checkout page displayed. The customer chooses a shipping method, and can either select an existing shipping address or add a new address. Users also can enter shipping instructions, if this functionality has been enabled (see the section, "Allowing Users to Enter Shipping Information", in the chapter, Implementing Payment Types and Shipping Methods).

  2. Customers can choose separate shipping details for different items in their carts after selecting the Need to ship to multiple addresses? link. If they choose to use item-level shipping, the Ship to Multiple Addresses page is displayed.

  3. In the Ship to Multiple Addresses page, customers can update an item's shipping details by selecting the item and pressing the Update Shipping Details button. This retrieves the Update Item Shipping Information page for the selected item. From this page they can enter different shipping information for the cart items.

  4. If customers have entered more than one quantity for a single item in their carts, they can split the quantities to enter different shipping information for each one. They do this by pressing the Split Quantity icon from the Update Item Shipping Information page.

  5. Once finished entering shipping information, customers return to the Checkout: Shipping and Billing page.

  6. In the billing area of the Checkout: Shipping and Billing page, customers select a billing address and select a payment method.

  7. Next, customers proceed to the Checkout: Terms and Conditions page (if this feature is enabled), where they agree to the terms and conditions of the order. Customers can reject terms and conditions as well; for information about rejecting terms and conditions, see the chapter, Implementing Carts and Orders.

  8. After customers agree with the terms and conditions, the Checkout: Review and Place Order page displays. From the review page, customers can update quantities, as well as change payment and shipping information.

  9. In the Checkout: Review and Place Order page, customers place the order by selecting the Place Order button.

  10. After placing the order, customers can select Continue Shopping to browse the specialty sites and potentially add more items to shopping carts.

From the cart or checkout pages, customers can request Sales Assistance, if implemented. If customers request sales representative assistance, they must select a reason for requesting assistance and optionally enter comments in the How can we assist you in finalizing your order? page. If the cart is unsaved, the user must enter a cart name. After submission, the cart becomes a quote on the My Quotes page.

See also: "Checkout Flow Pages" in the chapter, Implementing Carts and Orders

The following diagram shows this flow.

Process Flow for B2C Checkout

the picture is described in the document text

Process Flow for User Account

Customers can select the Profile, Orders, or Cart icons from any page to update their information, check on orders and invoices, work with shopping carts and shopping lists, or directly enter an item to purchase.

  1. Within the account menu, users can select the Cart icon to view their shopping carts and quotes; B2B users can use Direct Item Entry.

  2. Users can select the Orders icon to view information about their orders, such as payment information and shipment tracking. See Process Flow for Order Tracker to view the expanded diagram.

  3. Selecting the Profile icon takes users to user information and the personal information page. See Process Flow for User Profile to view the expanded diagram.

  4. B2B primary users can access the Administration menu where they can create and maintain other users for their organizations.

The following diagram shows the flow.

Process Flow for User Account

the picture is described in the document text

Process Flow for User Profile

B2B and B2C customers manage their own personal, address, and payment information using the Profile menu in the Customer Application. Note that the following flow covers the non-administrative user flow and assumes no other application integrations. No organization information is included in the B2B flow.

When customers select the Profile icon to edit their information, the My Profile subtab provides links to the following:

  1. Personal Information Page: Customers can enter/change their personal information, such as name, default e-mail address, and password.

  2. Address Book Page: Customers can enter/change their addresses (Address Book link) to be used during checkout, and set an address as the primary address to use when shopping. They also can store e-mail addresses (Email Addresses link) and phone numbers (Phone Book link).

  3. Customers can enter/change their addresses (Address Book link), e-mail addresses (Email Addresses link), and phone numbers (Phone Book link).

  4. Payment Book Page: Users can store credit cards to be used when ordering, and can mark a single credit card as the preferred one.

  5. Accounts Page: Users can view available accounts and set the preferred account.

  6. Preferences Page: In the General page, users can set preferred date format, preferred e-mail delivery language, and opt-in/opt-out of marketing communications. In the Orders page, users can: set preferred shipping method for order; enable their accounts for Express Checkout (if Express Checkout is enabled by the administrator); and set up shipping, billing, and payment information for their Express Checkout orders.

The following diagram shows the flow.

Process Flow for User Profile

the picture is described in the document text

Process Flow for Order Tracker

Customers can select the Orders icon to review their orders, invoices, payments, and returns.

  1. Customers choose the Orders icon, and the Orders page displays summarized information about their orders. From the Orders page, customers can select an order number hyperlink to access the Order Details page. Customers also can select the Shipping Details icon to view the Shipment Details page.

  2. If Express Checkout is enabled, customers select Pending Orders to view a list of Express Checkout orders that have not yet been submitted. From the Pending Express Checkout Orders page, customers can select the Item Details icon to view details of the items in the queue, including shipping and billing information for the items. If the orders have not yet been submitted, the user can press Cancel Order to cancel an order.

  3. Customers choose Invoices to view a list of their invoices, with payment and order information. Customers can select an invoice number hyperlink to view details of a particular invoice. Customers can select the Payment Details icon to access the Payment Details page.

  4. Customers choose Payments to view a summary of recent payments, or a payment number hyperlink to view details of a particular payment in the Payment Details page.

  5. Customers select Returns to view a list of their submitted returns. From the Returns page, customers can access the Pending Returns page or create a new return.

For more information about the activities that can be performed from these pages, see "Orders and Related Pages" in the chapter, Implementing Carts and Orders.

The following diagram illustrates the flow.

Process Flow for Order Tracker

the picture is described in the document text

Sample User Registration Flows

This section contains the following user registration flows:

Also see the sample registration flows in the "Integrating Oracle iStore with Oracle iSupport" and "Integrating Oracle iStore with Oracle Partner Management chapters.

Note: The registration pages are not displayed in a specific site context, since the target page of the registration depends on the selected user type and related responsibilities.

Individual User Registration

Following is a sample registration flow for individual users (B2C users). This flow assumes B2C users are automatically approved.

In the case of Oracle iSupport integration, the flow is the same, except that new users should be awarded Oracle iStore and Oracle iSupport individual user roles and responsibility.

  1. From the Registration page, user selects the hyperlink to register as an individual user.

  2. The user enters required information.

  3. The user selects Send me marketing communications checkbox or not.

  4. The user submits the registration form.

  5. The user receives an e-mail notification with username and password information.

The following diagram depicts the flow.

Individual (B2C) User Registration Flow

the picture is described in the document text

Business User Registration - New Organization

Following is a sample registration flow for business users (B2B users) whose organizations have not yet been registered. Typically, the first person to register his organization is considered the primary user and is charged with user management for business users within his organization. This flow assumes that the user will be automatically approved.

In the case of Oracle iSupport integration, the flow is the same, except that new users should be awarded Oracle iStore and Oracle iSupport primary business user roles and responsibility.

In case of Oracle Partner Management integration, the user would select the Oracle Partner Management link, Register as a partner.

  1. The user accesses the Registration page and selects the link to register as the first user of an organization.

  2. The user enters required information.

  3. The user submits the registration.

  4. The user receives an e-mail notification that his registration has been approved. He can access the Profile > Organization Information area of the Customer UI to view his Organization ID/Registry ID and communicate it to other users.

The following diagram depicts the flow.

Business User (B2B) Registration Flow - New Organization

the picture is described in the document text

Business User Registration - Existing Organization

Following is the registration flow for business users (B2B users) whose organization has already been registered. This flow assumes that a primary user must approve the B2B user's registration.

In the case of Oracle iSupport integration, the flow is the same, except that new users should be awarded Oracle iStore and Oracle iSupport business user roles and responsibility.

In case of Oracle Partner Management integration, the user would select the Oracle Partner Management link, Register as a user of an existing partner.

  1. The non-primary user accesses the Registration page and selects the link to register as user of an existing organization. The user should know his Organization ID/Registry ID before beginning registration.

  2. The user enters required information, including Organization ID/Registry ID.

  3. The user submits the registration.

  4. The user receives an e-mail notification that his registration request has been submitted.

  5. The primary user receives an e-mail notification that a self-registered user asked for approval.

  6. The primary user approves the registration.

  7. The non-primary user receives a notification that his registration is approved.

The following diagram depicts the flow.

Business User (B2B) Registration Flow - Existing Organization

the picture is described in the document text

Registration in Combined Store-Support-Partner Implementation

Following is a sample registration flow a common implementation of Oracle iStore, Oracle iSupport, and Oracle Partner Management using Oracle iStore framework.

  1. The user arrives at the registration page through one of the following paths:

  2. From the Registration page, the user selects the appropriate user type for which he is registering. Depending upon his user type selection, he follows one of the following registration flows:

The following diagram depicts the flow.

Registration in Implementation of Oracle iStore-iSupport-Partner Management

the picture is described in the document text