# projects management — Learning Path

_Learning Paths › projects management_

This learning path is for project operations users who need to review project-related order work, retain shipping-order updates, and prepare an Orders workspace for operational follow-up. After completing the path, learners can navigate the available project and order work areas, safely save shipping-order changes, and create, maintain, and export an Orders list layout.

## Learning objectives

- By the end of this path you can identify the appropriate project and order workspace for the task at hand.
- By the end of this path you can locate a shipping order and review its current changes.
- By the end of this path you can retain shipping-order changes using **Save** or **Save and Close**.
- By the end of this path you can create an Orders list layout with a name and selected columns.
- By the end of this path you can update, remove, and export an Orders list layout for operational review.

## Prerequisites

- Access to the [Projects Management](doc:projects-management-guide), [Orders](doc:orders-guide-2), [Production Order](doc:production-order), and [Delivered Orders](doc:delivered-orders) screens.
- Access to the [Shipping Order](doc:projects-management-shipping-order-new) screen, including the ability to use **Search**, **Save**, **Save and Close**, and **Export**.
- Access to manage layouts in the [Orders](doc:orders-guide-2) screen, including **Add Layout**, **Columns Chooser**, **Save**, **Update Current**, **Delete Current**, **Delete**, and **Export**.
- Familiarity with the project and order terminology used by your organization.

## Module 1: Establish your operational starting point

**Goal:** Learn to choose the right work area before reviewing or updating order-related work.

### Lesson 1.1: Start from the project and order workspaces

When you need to understand where operational work is being managed, begin by opening [Projects Management](doc:projects-management-guide) and [Orders](doc:orders-guide-2). Use Projects Management as your project-focused starting point, then move to Orders when your task is to review an operational list of orders. This establishes the context you need before working with a specific shipping or production record.

**Practice task:** Open [Projects Management](doc:projects-management-guide), then open [Orders](doc:orders-guide-2) and identify which workspace you would use for an operational order review.

### Lesson 1.2: Recognize production and completed-order contexts

When an order-related question concerns production activity or orders that have already been delivered, use the specialized workspaces rather than treating every task as a current Orders-list task. Open [Production Order](doc:production-order) for production-order work and [Delivered Orders](doc:delivered-orders) when reviewing delivered-order results.

**Practice task:** Open [Production Order](doc:production-order) and [Delivered Orders](doc:delivered-orders), then state which screen you would use to review a delivered order.

## Module 2: Review and retain shipping-order changes

**Goal:** Find the correct shipping order, review changes, and retain the right version of the record.

### Lesson 2.1: Find the shipping order that needs review

When a shipping-related update needs attention, work in [Shipping Order](doc:projects-management-shipping-order-new). Use **Search** to locate the shipping order, then review the changes in the record before deciding whether they should be retained. Starting with Search helps ensure that you are reviewing the intended shipping order rather than making decisions from an unfiltered view.

**Practice task:** In [Shipping Order](doc:projects-management-shipping-order-new), use **Search** to locate a shipping order that requires review.

### Lesson 2.2: Save, close, or export the reviewed shipping order

After you have reviewed a shipping order in [Shipping Order](doc:projects-management-shipping-order-new), retain the changes with **Save** if you need to continue working, or use **Save and Close** if the review is complete. When you need to share or retain the reviewed output outside the active screen, use **Export**.

**Practice task:** Review a shipping order, then use **Save and Close** to retain the changes and finish the task.

## Module 3: Build an Orders view for daily operations

**Goal:** Create a reusable Orders layout that supports focused operational review.

### Lesson 3.1: Create a layout with the columns your team needs

When the standard Orders display does not support a specific operational review, create a dedicated layout in [Orders](doc:orders-guide-2). Select **Add Layout**, enter a **Layout name**, and use **Columns Chooser** to select the columns needed for the review. Use **Save** to retain the new layout for future use.

**Practice task:** In [Orders](doc:orders-guide-2), select **Add Layout**, provide a **Layout name**, use **Columns Chooser**, and select **Save**.

### Lesson 3.2: Maintain and distribute an operational layout

As operational needs change, return to the active layout in [Orders](doc:orders-guide-2). Use **Update Current** to retain adjustments to the current layout. If a layout is no longer needed, use **Delete Current** or **Delete** as appropriate. Use **Export** when you need to distribute the results of the operational review.

**Practice task:** Open an existing Orders layout, make an adjustment through the available layout options, and select **Update Current**.

## Final assessment

1. You have been asked to review a project-related operational order list before a team meeting. Which workspace should you open first, and what is the next workspace you would use for the order list?

2. A shipping-order change has been requested, but you need to make sure you are reviewing the correct record before retaining anything. What screen and control should you use first?

3. You have completed your review of a shipping order and do not need to continue working in that record. Which control should you use to retain the changes and leave the record?

4. Your team needs a repeatable Orders view with only the columns relevant to its daily review. What sequence of controls should you use to create it?

5. An existing Orders layout is no longer needed, and the team also needs to share the output from another layout. Which controls support those two outcomes?

### Answers

1. Open [Projects Management](doc:projects-management-guide) first, then [Orders](doc:orders-guide-2).  
   Why: Projects Management provides the project-focused starting point, while Orders supports operational order-list review.

2. Open [Shipping Order](doc:projects-management-shipping-order-new) and use **Search**.  
   Why: Search helps locate the intended shipping order before it is reviewed or saved.

3. Use **Save and Close**.  
   Why: It retains the reviewed changes and closes the shipping-order record.

4. Use **Add Layout**, enter a **Layout name**, use **Columns Chooser**, then select **Save**.  
   Why: These controls create, identify, configure, and retain a reusable layout.

5. Use **Delete Current** or **Delete** to remove the obsolete layout, and use **Export** to share the other layout’s output.  
   Why: The delete controls remove layouts, while Export provides the review output for distribution.