# VL registrations

## VL registrations

VL registrations are reference entries that group a registration by its client or project
relationship. Use this surface when you need to inspect registration data at a client or at a
project.

Registration statuses describe the registration's current position. The available status values
are `Registered`, `Proceeding`, `NotRegistered`, and `Updated`.

| If you need to… | Go to |
|---|---|
| Inspect registrations grouped at clients | [Choose the relationship view](#choose-the-relationship-view) |
| Inspect registrations grouped at projects | [Choose the relationship view](#choose-the-relationship-view) |
| Review the list columns and popup fields | [Understand the registration list](#understand-the-registration-list) |
| Prepare a new registration | [Add a registration](#add-a-registration) |
| Continue with the related account | [Accounts](doc:accounts) |
| Continue with the related project | [Projects](doc:projects) |
| Continue with reference data | [Reference list](doc:reference-list-data) |
| Continue with related files and libraries | [Libraries and files](doc:libraries-files) |

## Before you start

Choose the client relationship view or the project relationship view for the relationship you need
to inspect.

**Prerequisites**

- Know whether you are checking a client relationship or a project relationship.
- Have access to the registration list for that relationship.
- If you need **New**, your access must allow the page's new-record permission for the selected
  relationship.
- If you need **Export**, your access must allow export for the selected relationship.

**Result:** You know which relationship view to open and have access to its registration list.
<!-- runtime: runs/pams-data/walk/vl-registrations-accounts/report.json:11-15; runs/pams-data/walk/vl-registrations-projects/report.json:11-15 -->

## Find VL registrations

Use the **VL registrations** entry in the **Data** area to open the registration reference list.
The entry opens the accounts view first; the list then provides the relationship tabs.
<!-- runtime: /app/corpus/pams/evidence/navigation.json:15978-16019 -->

**Prerequisites**

- Know whether you want to inspect the client or project relationship.

**Steps**

1. Open **VL registrations** from **Data**.
2. Select the relationship view:

   | If you need to inspect… | Select |
   |---|---|
   | Client relationships | **At Clients** |
   | Project relationships | **At Projects** |

**Result:** The selected relationship list is on screen.
<!-- runtime: /app/runs/pams-data/walk/vl-registrations-accounts/report.json:11-15; /app/runs/pams-data/walk/vl-registrations-projects/report.json:11-15 -->

![Registration list with its relationship tabs and six columns](https://atloriaassets.blob.core.windows.net/assets/a438221c-c1af-407c-b9e6-a56c986db846/612317007f7133ce817f6f2e58c3186b.png)

## Understand the registration list

The list has two relationship tabs and a grid whose headers identify the registration data being
reviewed. The grid headers are **Company**, **Principal**, **Registration date**,
**Registration no.**, **Status**, and **Branch**.
<!-- runtime: /app/runs/pams-data/render/vl-registrations-main.json:20-27 -->

The list contains data rows for review.
<!-- runtime: /app/runs/pams-data/render/vl-registrations-main.json:51-52 -->

The page exposes the button titles **Refresh**, **Table Layout**, and **Settings**.
<!-- runtime: /app/runs/pams-data/render/vl-registrations-main.json:30-42 -->

The popup renders the relationship and registration-detail fields.

Each popup has three required select fields and two optional fields. The date field accepts a date no
later than today.

The lookup choices and starting field values come from the lists shown for the selected
relationship.

## Choose the relationship view

Use the client relationship view for client checks and the project relationship view for project
checks.

**Prerequisites**

- Know whether the registration belongs to the client or project relationship you are checking.

**Steps**

1. Select the matching tab:

   | If you are checking… | Select |
   |---|---|
   | A client relationship | **At Clients** |
   | A project relationship | **At Projects** |

2. Review the popup fields described above when you select **New**.

**Result:** The selected relationship view is on screen with its matching list and popup field set.
<!-- runtime: /app/runs/pams-data/walk/vl-registrations-accounts/report.json:23-50 -->
<!-- runtime: /app/runs/pams-data/walk/vl-registrations-projects/report.json:23-50 -->

## Add a registration

Adding a registration starts from **New** on the relationship view. The popup title identifies the
relationship: `New register at account` or `New register at project`.

**Prerequisites**

- Be on the relationship tab where you want the registration.
- Know the client, vendor, project, status, registration number, and registration date that apply.

**Steps**

1. Select **New**.
2. Follow the relationship-specific outcome:

   | Relationship | Outcome |
   |---|---|
   | Client | The account popup fields do not appear after **New**. |
   | Project | Select **Project**. The project page opens instead of keeping the registration popup open. |

**Result:** **New** does not open the account popup on the client relationship. On the project
relationship, selecting **Project** opens the project page instead.
<!-- runtime: /app/runs/pams-data/walk/vl-registrations-accounts/report.json:47-80 -->
<!-- runtime: /app/runs/pams-data/walk/vl-registrations-projects/report.json:71-86 -->

![Account relationship state after selecting New](https://atloriaassets.blob.core.windows.net/assets/a438221c-c1af-407c-b9e6-a56c986db846/1a136b452aad8c6fab48c460f3d088bc.png)

![Project destination reached after selecting Project](https://atloriaassets.blob.core.windows.net/assets/a438221c-c1af-407c-b9e6-a56c986db846/78babcbf6772000f4a9a09a8afe51073.png)

The registration grid does not offer **Edit** or **Delete** actions.
<!-- runtime: /app/runs/pams-data/render/vl-registrations-main.json:20-27 -->

![Project registration popup with its fields and required markers](https://atloriaassets.blob.core.windows.net/assets/a438221c-c1af-407c-b9e6-a56c986db846/85ac510a547119b131e74c6f0bc0ff7e.png)

## When registration work goes wrong

The registration forms declare the following required-field messages:

| Field | Message |
|---|---|
| **Client** | `Client is required` |
| **Vendor** | `Vendor is required` |
| **Status** | `Status is required` |
| Project **Vendor** | `Vendor is required` |
| Project **Project** | `Vendor is required` |
| Project **Status** | `Status is required` |

The list and service paths also declare these messages:

| Situation | Message |
|---|---|
| A filter contains forbidden characters | `Forbidden characters detected. Please remove them and try again.` |
| Loading the list fails | `Load data failed` |
| Saving an account registration succeeds | `Data saved Successfully` |
| Saving an account registration fails | `Error Saving Registration` |
| Saving a project registration fails | `Error saving registration` |
| Export has no data | `NO Data to Export` |

**Steps**

1. Read the message shown beside the field or list action.
2. Correct the field named in the message, or remove the forbidden characters from the filter.
3. Select **OK** again for a registration form, or repeat the list action after correcting the
   filter.

**Result:** The form or list is ready for the same action again.

## What to do next

After reviewing a registration, continue with the relationship that needs attention. Use the
account page for account work, the project page for project work, the reference-list page for
reference data, or the libraries-and-files page for related files.

**Steps**

1. Select the next relationship-specific destination:

   | If you need to… | Go to |
   |---|---|
   | Work with the related account | [Accounts](doc:accounts) |
   | Work with the related project | [Projects](doc:projects) |
   | Continue with reference data | [Reference list](doc:reference-list-data) |
   | Continue with related files | [Libraries and files](doc:libraries-files) |

**Result:** The related work area is selected for the next task.

## Out of scope

The import completion message `Data Importing completed` belongs to the shared-popup import flow,
which is not part of the registration actions covered here.
