Understanding distributed operation use cases

The information in this topic is applicable only for on-premises deployments.

Consider the following use case to understand the start-to-finish process of how basic distributed operations are implemented between two geographically distinct servers at Apex Global Industries.

Apex Global makes custom office furniture that is distributed to and returned from vendors such as office supply stores. Assume you are a manager with administrator privileges and a fixed license at the Apex Global plant in San Francisco, California. Apex Global recently opened another plant in Chicago, Illinois. Labor is divided between the plants as follows:

Plant

Manufactures and repairs

Request ID prefix

San Francisco

  • Prize Desks
  • Prize Printer Stands

AW (Apex Global West)

Chicago

  • Choice Desk Chairs
  • Superior Side Chairs

AE (Apex Global East)

Information about Apex Global's vendors is stored in Apex Global's customer information forms. Products returned from vendors for various faults are entered into Apex Global's bug-tracking forms. You must set up distributed operations between the bug tracking form on the sanfrancisco server and the bug tracking form on the chicago server. Both servers have DSO licenses.

All the examples in this section assume that you have created the Apex Global West Bug Tracking form on the sanfrancisco server and the Apex Global East Bug Tracking form on the chicago server.

See the topics listed in the following table to know about the different distributed operation scenarios:

Action

Reference

Create a filter with DSO transfer action

Create a DSO update action for the forms

Create a DSO return action for the forms

Create a DSO delete action for the forms

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*