01

Scenario: Opening the Filters panel
Given I am on the users List page
When I click on the "Filters" link
Then the filters panel should open on the right side of the screen, displaying filter options such as

1. Title / Titel

2. OOS Keyword / Keyword

3. Status / Status

4. Business Unit / Business Unit

5. Role / Rolle

6. Division / Division

7. Position / Position

8. Categories / Kategorien

9. Market / Markt

02

Scenario: User interact with the filter panel
Given user in filter panel,
When clear/add/search some items
Then have common behaviour of the field described here: Story 1.0.12.5. CRM. Filter panel

https://api.staging.rockengroup.com/api-documentation-2000#/User/get_api_v1_users_

01

User name

Scenario: User applies Users filter.
Given the user enters a Name,
When the title exists,
Then suggestions are displayed.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags

search query

02

Keyword OOS

Scenario: User applies a keyword filter.
Given the user enters a custom keyword,
When it is find info in any Users fields without suggestions
AND data matches with keyword ,
Then relevant results are displayed

Select type:

• multi select OOS

• multi tags

• search OOS

• suggestions OOS

• custom tags

search by all fields in Users

03

Status

Scenario: User applies a status filter.
Given the user selects a status,
When the selection is made,
Then the results reflect the selected status.

Select type:

• multi select

• multi tags

• search OOS

• suggestions OOS

• custom tags OOS

should be added to API by backend developer

Options:

04

Business Unit

Scenario: User filters by business unit.
Given business units exist,
When one is selected,
Then results match the selection.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

business_units[]

05

Role

Scenario: User applies a Role filter.
Given Role exist,
When one or several are selected,
Then results show jobs managed by the selected role.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

should be added to API by backend developer

06

Division

Scenario: User applies division filter.
Given available division option,
When one division is selected,
Then results filter accordingly this division.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

should be added to API by backend developer

07

Position

Scenario: User applies a position filter.
Given position options exist,
When one or several are selected,
Then results show jobs managed by the consultant.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

should be added to API by backend developer

Options:
–
–

08

Category

Scenario: User applies a category filter.
Given the user types a category,
When matches exist,
Then suggestions are displayed.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

should be added to API by backend developer

09

Market

Scenario: User filters by country.
Given country options exist,
When one is selected,
Then only profiles in that country are displayed.

Select type:

• single select

• single tag

• search OOS

• suggestions OOS

• custom tags OOS

should be added to API by backend developer

01

Scenario: Viewing the Users List Table
GIVEN I am on the users list page,
WHEN I access the page,
THEN I should see a table displaying all users with columns for Name with Country, Role, Business Unit > Division > Position, Manager, Email, Phone, and action buttons.

02

Scenario: Action Buttons for Users
GIVEN I am viewing the users list table,
WHEN I click on the action buttons (edit or delete),
THEN I should see options to edit (edit mode) or delete (with confirmation) the corresponding user.

03

Scenario: Missing Information in User Table
GIVEN a user has missing information for any column,
WHEN I view the users list table,
THEN I should see a "-" symbol in the corresponding cell.

04

Scenario: Viewing User Details
GIVEN I am on the users list page,
WHEN I click on a user’s name,
THEN I should be taken to that user’s detail page for more information.

05

Scenario: Scrollable User List Table
GIVEN there are more users than can fit on one page,
WHEN I scroll down,
THEN I should be able to scroll through the list of users to view all entries with using pagination.

01

Given:

When:

Then:

02

Given:

When:

Then:

03

Given:

When:

Then:

01

Scenario: Display Vacancy Information
Given the CRM user navigates to the "Vacancy" tab in the Process view
When a candidate is associated with a vacancy
Then the name of the vacancy should be displayed at the top of the collapsible area.

02

Scenario: Candidate Application Notification
Given the candidate has previously applied for the vacancy
When the CRM user views the "Vacancy" tab
Then the message "Candidate was applied for this job before" should be displayed.

03

Scenario: Main Information Subtab
Given the CRM user is viewing the "Main Information" subtab
When the candidate’s data is loaded
Then matching information, skills, and most important information should be displayed, including experience level, workload, salary range, age, position, employment types, start date, and degrees.

Story 1.6.4.12. CRM. Process view. Tab Vacancy. Matching section

04

Scenario: Description Subtab
Given the CRM user clicks on the "Description" subtab
When the vacancy description is retrieved
Then the full description of the vacancy should be displayed.

05

Scenario: Company Subtab
Given the CRM user clicks on the "Company" subtab
When the company information is retrieved
Then the company logo, name, headquarters location, company size, website, and industries should be displayed.

01

Given:

When:

Then:

02

Given:

When:

Then:

03

Given:

When:

Then:

01

Scenario: Viewing notes for a process
Given I am in the "Notes" tab of the process view
When I open the "Notes" tab
Then I should see all the notes related to the process, with pinned notes displayed at the top.

01

Given:

When:

Then:

02

Given:

When:

Then:

03

Given:

When:

Then:

01

Given:

When:

Then:

02

Given:

When:

Then:

03

Given:

When:

Then:

01

Scenario: Status change logging
Given a user changes the status of a process
When the status change is recorded
Then it should be displayed in the Activity tab with the format:
EN: "{user/candidate/company name} changed status to {status name}"
DE: "{user/candidate/company name} hat Status auf {status name} geändert."

02

Scenario: Manual status change from CRM Process page
Given a user manually changes the status from the CRM Process page
When the manual change is recorded
Then it should be displayed with the format:
EN: "{user/candidate/company name} manually changed status to {status name}"
DE: "{user/candidate/company name} hat Status auf {status name} manuell geändert"
and include related comments/notes if provided.

03

Scenario: Email delivery record
Given an email is sent via SendGrid
When the email is delivered
Then the record should display in the Activity tab with the format:
EN: "Email {template name} for {status name} was delivered on {date} at {time}"
DE: "E-Mail {template name} für {status name} wurde am {date} um {time} zugestellt."

04

Scenario: Email read/opened record
Given an email is opened by the recipient
When the email read event is logged via SendGrid
Then the record should display in the Activity tab with the format:
EN: "{candidate/company contact} opened the E-Mail: status change to {Read}/{Read Shared}"
DE: "{candidate/company contact} öffnete die E-Mail: Statusänderung auf {Read}/{Read Shared}."

05

Scenario: Forecast update
Given a user updates the forecast
When the forecast changes from automatic to manual
Then the record should display in the Activity tab with the format:
EN: "{user name} updated the Forecast from {automatic forecast} to {manual forecast entry}"
DE: "{user name} hat die Forecast von {automatic forecast} auf {manual forecast entry} aktualisiert."

06

Scenario: Event creation logging
Given a user creates an event
When the event is recorded
Then the Activity tab should display the entry with the format:
EN: "{user name} created {event type} for {event date} {event time}"
DE: "{user name} hat {event type} für {event date} {event time} erstellt."

07

Scenario: Manual status indication
Given a status change is made manually from the CRM (not in vacancy or profile interaction)
When the record is created
Then the term "manual" should be included in the entry.

08

Scenario: Separation of communication and notes
Given activity records are displayed
When a user navigates to the Activity tab
Then all status changes, email interactions, event records, and forecast updates should be displayed, while communication and notes are segregated into separate tabs.

09

Scenario: Date and time format
Given an activity record is created
When it is displayed in the Activity tab
Then each entry should contain date and time in CET.

10

Scenario: Record immutability
Given an activity entry is created
When a user views the entry
Then there should be no option to delete the record, ensuring permanent logging.