01

Scenario: Accessing the Conditions tab
Given the recruiter is in vacancy edit mode
When they navigate to the "Conditions" tab
Then they should see sections for Start Date, Desired Salary, Working Model, Location, Travel, Experience Level, Position, Degrees, Languages, Employment Type, Workload, Age, and Team Size.

02

Scenario: Setting Start Date
Given the recruiter is in the "Start Date" section
When they select a specific date or check the "Immediately" option
Then the selected date or "Immediately" option should be saved to the vacancy conditions.

03

Scenario: Specifying Desired Salary
Given the recruiter is in the "Desired Salary" section
When they input a minimum and maximum salary range
Then the specified salary range should be saved and displayed in the vacancy conditions.

04

Scenario: Selecting Working Model
Given the recruiter is in the "Working Model" section
When they choose options like "Home office," "Working remotely," "Hybrid," or "On-site"
Then the selected options should be saved and displayed in the vacancy details.

05

Scenario: Adding Location
Given the recruiter is in the "Location" section
When they enter an address or choose a city and optionally select "All cities"
Then the location details should be saved to the vacancy.

06

Scenario: Setting Travel Preferences
Given the recruiter is in the "Travel" section
When they select options like "Europe-wide," "Throughout Switzerland," "Worldwide," "ROOF," "Individual willingness to travel," or "Not willing to travel"
Then the chosen preference should be saved in the vacancy conditions.

07

Scenario: Selecting Experience Level
Given the recruiter is in the "Experience Level" section
When they choose options such as "Junior," "Professional," "Senior," or "Executive"
Then the selected experience level should be saved in the vacancy conditions.

08

Scenario: Specifying Position
Given the recruiter is in the "Position" section
When they select options like "Specialist position," "Leading position," or "Executive"
Then the chosen position should be saved and displayed in the vacancy details.

09

Scenario: Adding Leading Experience
Given the recruiter is in the "Leading Experience" section
When they select options like "Personal management experience," "Management of project teams," or "Prof. management of employees"
Then the selected experience should be saved in the vacancy conditions.

10

Scenario: Choosing Degrees
Given the recruiter is in the "Degrees" section
When they select relevant degrees from the list (e.g., "Technical school," "Bachelor," "Masters")
Then the selected degrees should be saved to the vacancy.

11

Scenario: Adding Languages
Given the recruiter is in the "Languages" section
When they select a language and proficiency level
Then the chosen language and level should be saved in the vacancy conditions, with an option to add multiple languages.

12

Scenario: Setting Employment Type
Given the recruiter is in the "Employment Type" section
When they select options like "Permanent employment," "Temporary," or "Part time"
Then the selected type(s) should be saved and displayed in the vacancy conditions.

13

Scenario: Adjusting Workload
Given the recruiter is in the "Workload" section
When they set the workload percentage using a slider
Then the selected workload range should be saved to the vacancy.

14

Scenario: Specifying Age Range
Given the recruiter is in the "Age" section
When they set the age range using a slider
Then the specified age range should be saved in the vacancy conditions.

15

Scenario: Choosing Team Size Preference
Given the recruiter is in the "Team Size" section
When they select a team size range (e.g., "1-15," "15-20")
Then the chosen team size preference should be saved to the vacancy.

16

Scenario: Saving Changes
Given the recruiter has made changes in the "Conditions" tab
When they click "Save & Changes"
Then all entered details should be saved, and a confirmation message should appear.

17

Scenario: Cancelling Changes
Given the recruiter is in the "Conditions" tab
When they click "Cancel"
Then no changes should be saved, and the system should return to the vacancy view mode.

18

Scenario: Validating Required Fields
Given the recruiter has filled out the "Conditions" tab
When they attempt to save
Then the system should validate that all required fields are completed, displaying a message for any missing information.

01

Scenario: Accessing the Business Information tab
Given the recruiter is in vacancy edit mode
When they navigate to th e "Business Information" tab
Then they should see sections for Process Type, Industry, Categories, Skills, Contact Person, and Application Method.

02

Scenario: Setting the Process Type
Given the recruiter is in the "Process Type" section
When they select either "Edit" or "Download" for the process type
Then the system should save the selected option and display it in the vacancy details.

03

Scenario: Selecting Industries
Given the recruiter is in the "Industry" section
When they select one or more industries from the list
Then the selected industries should appear as tags below the search box and be saved to the vacancy.

04

Scenario: Searching Industries
Given the recruiter is in the "Industry" section
When they enter a search term
Then the list should filter to show industries that match the term entered.

05

Scenario: Selecting Categories
Given the recruiter is in the "Categories" section
When they select one or more categories from the list
Then the selected categories should appear as tags and be saved to the vacancy.

06

Scenario: Adding Category Recommendations
Given the recruiter has selected relevant categories
When the system identifies recommended categories based on current selection
Then these recommended categories should appear under "Recommendation" for optional selection.

07

Scenario: Adding Skills
Given the recruiter is in the "Skills" section
When they add skills under "Hard Skills" or "Soft Skills"
Then the skills should appear as tags under each respective category and be saved to the vacancy.

08

Scenario: Searching Skills
Given the recruiter is in the "Skills" section
When they enter a search term
Then the list should filter to show skills that match the search term entered.

09

Scenario: Adding Skill Recommendations
Given the recruiter has entered certain skills
When the system identifies recommended skills based on the current selection
Then these recommended skills should appear under "Recommendation" for optional selection.

10

Scenario: Selecting Contact Person
Given the recruiter is in the "Contact Person" section
When they choose a "Department of Client" and a "Contact Person" from the dropdown
Then the selected department and contact person should be saved to the vacancy.

11

Scenario: Selecting Application Method
Given the recruiter is in the "Application Method" section
When they select "Email" or "Download" as the application method
Then the selected method should be saved and displayed in the vacancy details.

12

Scenario: Setting Secondary Process Type
Given the recruiter is in the "Process Type" section
When they select either "Success Fee" or "PaaS" as the secondary process type
Then the selected type should be saved and displayed in the vacancy details.

13

Scenario: Saving Changes
Given the recruiter has made changes in the "Business Information" tab
When they click "Save & Changes"
Then all entered details should be saved, and a confirmation message should appear.

14

Scenario: Cancelling Changes
Given the recruiter is in the "Business Information" tab
When they click "Cancel"
Then no changes should be saved, and the system should return to the vacancy view mode.

15

Scenario: Validating Required Fields
Given the recruiter has filled out the "Business Information" tab
When they attempt to save
Then the system should validate that all required fields (e.g., process type, industry, contact person) are completed, displaying a message for any missing information.

01

Scenario: Display primary fields for editing
Given the user is in the "Vacancy Edit Mode" and is viewing the "Tab Primary"
When the user accesses this tab
Then the system should display editable fields for "Order", "Staff", “Vacancy name“, "Direct Link", “Application by”, “Job model“.

02

Scenario: change/select order in vacancy edit mode
Given the user is in the "Vacancy Edit Mode" and is viewing the "Tab Primary"
When the user accesses this tab and edits the order
Then the system should display existing Orders of the company in a drop-down.

02a

Scenario: create order in vacancy edit mode
Given the user is in the "Vacancy Edit Mode" and is viewing the "Tab Primary" with company but without order
When the user clicks on the link in dropdown “+ Create order“
Then order creation mode is opened in the next tab of the browser and inherits company and vacancy’s title

https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/Rocken-Design?node-id=62789-58706&t=GFn4J1M0ycfkFe85-4

03

Scenario: Market field isn’t shown
Given the user is editing the primary details of a vacancy
When the user views the available fields
Then no field related to the market should be present because the market is related to the selected company

04

Scenario: Save changes
Given the user has made changes to the fields in the "Tab Primary"
When the user clicks the "Save" button
Then the changes should be saved, and the vacancy information should be updated accordingly.

05

Scenario: Cancel changes
Given the user is editing the "Tab Primary"
When the user clicks the "Cancel" button
Then any unsaved changes should be discarded, and the vacancy details should remain unchanged.

06

Scenario: Automatic order assignment to vacancy publications
Given a vacancy has one or more associated publications
When an order is ADDED/EDITED to the vacancy
AND click Save changes
AND see the modal window with text:
EN: ”The Publication(s) of this Vacancy will be assigned to the same Order.” Button [Ok] and [X] (close)
DE: “Die Publikation(en) dieser Vakanz wird/werden derselben Order zugeordnet.“ Button [Ok] and [X] (close)
AND click [Ok]
Then the order is automatically assigned to all associated publications of the vacancy 

These roles need to have permission to edit the Vacancy with order.

• Admin

• Consultant: Only for his orders

• Business Manager: Only for his business unit orders

• Content Manager

• Division Head: Only for his orders

• Sales Manager: Only for his orders

07

Scenario: Automatic order assignment to vacancy publications CANCELLED
Given a vacancy has one or more associated publications
When an order is ADDED/EDITED to the vacancy
AND click Save changes
AND see the modal window with text:
EN: ”The Publication(s) of this Vacancy will be assigned to the same Order.” Button [Ok] and [X] (close)
DE: “Die Publikation(en) dieser Vakanz wird/werden derselben Order zugeordnet.“ Button [Ok] and [X] (close)
AND click [X] (close)
Then changes is not saved and you can continue editing without reset edited data

01

Scenario: Viewing the PaaS Report on a Vacancy page
Given: I am on a Vacancy page
When: I click on the "PaaS report" tab
Then: I see a detailed report that includes the following sections: Sources, Activities, Active Sourcing, Rejection Statistics.

02

Scenario: Sources tab
Given: I am viewing the "Sources" tab in the PaaS report
When: The data loads
Then: I see a table with columns for "Source," "Applications," "Rejections," and "Interviews." Each column should display numerical values for each source, and the totals at the bottom of the table should summarize the figures.

03

Scenario: Activities tab
Given: I am viewing the "Activities" tab in the PaaS report
When: The data loads
Then: I see a table that displays "Calendar Week №," "Rocken Profile," "Sharing," "Interview 1," "Interview 2," and "Fee" columns.

04

Scenario: Active Sourcing tab
Given: I am viewing the "Active Sourcing" tab in the PaaS report
When: The data loads
Then: I see a table that includes the following columns: "Candidate," "Position," "Application," "Rejection Reason," "Note," and "Fee."
And: I can edit the rejection reason using a dropdown, and enter a note and fee in their respective fields.

05

Scenario: Rejection Statistics tab
Given: I am viewing the "Rejection Statistics" tab in the PaaS report
When: The data loads
Then: I see a pie chart representing the rejection reasons, along with a table displaying the number and percentage for each reason.

06

Scenario: Generating a PDF of the PaaS report
Given: I am viewing the PaaS report
When: I click on the "Generate PDF" button
Then: A modal should appear, allowing me to select the campaign start date, enter a campaign number, and choose whether to include rejection statistics in the PDF.
And: There should be a "Download" button to generate the PDF.

07

Scenario: Campaign start date selection
Given: I am in the "Generate PDF" modal
When: I click on the "Campaign Start" field
Then: A calendar popup should appear, allowing me to select the campaign start date.

08

Scenario: Adding a campaign number
Given: I am in the "Generate PDF" modal
When: I click on the "Campaign Number" field
Then: I can enter a unique identifier for the campaign.
And: The campaign number should be included in the generated PDF report.

09

Scenario: Including rejection statistics
Given: I am in the "Generate PDF" modal
When: I check the "Add rejection statistics" checkbox
Then: The rejection statistics should be included in the generated PDF report.
And: If I uncheck the box, the rejection statistics should not be included.

10

Scenario: Downloading the PDF
Given: I have filled in the campaign start date and campaign number
When: I click on the "Download" button
Then: The system generates a PDF file containing the data from the PaaS report based on my selections and settings.

01

Scenario: Displaying similar vacancy list
Given a vacancy is selected
When the recruiter views the "Similar Vacancy" tab
Then a list of similar vacancies should be displayed, showing columns for Name, Status, Process Type, Company, Category, Location, Publication, and Consultant.

02

Scenario: Column for "Name"
Given the "Similar Vacancy" tab is displayed
When viewing the Name column
Then it should display the title of each similar vacancy, clickable to navigate to the vacancy’s details.

03

Scenario: Column for "Status"
Given the "Similar Vacancy" tab is displayed
When viewing the Status column
Then it should show the current status of each similar vacancy (e.g., "Active", "Inactive") with a corresponding color indicator.

04

Scenario: Column for "Process Type"
Given the "Similar Vacancy" tab is displayed
When viewing the Process Type column
Then it should display the type of recruitment process for each similar vacancy (e.g., "PaaS", "Succession Fee").

05

Scenario: Column for "Company"
Given the "Similar Vacancy" tab is displayed
When viewing the Company column
Then it should display the name of the company associated with each similar vacancy.

06

Scenario: Column for "Category"
Given the "Similar Vacancy" tab is displayed
When viewing the Category column
Then it should display the job categories relevant to each similar vacancy.

07

Scenario: Column for "Location"
Given the "Similar Vacancy" tab is displayed
When viewing the Location column
Then it should display the number of job locations associated with each similar vacancy.

08

Scenario: Column for "Publication"
Given the "Similar Vacancy" tab is displayed
When viewing the Publication column
Then it should display the number of publications related to each similar vacancy.

09

Scenario: Column for "Consultant"
Given the "Similar Vacancy" tab is displayed
When viewing the Consultant column
Then it should display the profile image and name of the consultant responsible for each similar vacancy, clickable to navigate to the consultant’s profile.

10

Scenario: Sorting by Name
Given the similar vacancies list
When the recruiter clicks the Name column header
Then the list should sort by name, toggling between ascending and descending order.

11

Scenario: Filtering by Status
Given multiple similar vacancies with different statuses
When the recruiter applies a status filter
Then only vacancies matching the selected status (e.g., "Active", "Inactive") should be displayed in the list.

12

Scenario: Opening vacancy details
Given a list of similar vacancies
When the recruiter clicks on a vacancy name
Then the system should navigate to the detailed view of that vacancy.

13

OOS Scenario: Multi-select actions
Given the similar vacancies list
When the recruiter selects multiple entries
Then bulk actions (e.g., mass update) should become available in the UI.

14

Scenario: Pagination
Given a large number of similar vacancies
When there are more than a set number of vacancies displayed (e.g., 10 per page)
Then pagination controls should appear at the bottom of the list, allowing navigation through multiple pages.

15

Scenario: Edit action for each vacancy
Given the "Similar Vacancy" tab
When the recruiter edit icon for each entry
Then options to edit each similar vacancy should be available with the opening the vacancy in edit mode.

16

Scenario: Filter by Consultant
Given multiple similar vacancies with different consultants
When the recruiter applies a consultant filter
Then only similar vacancies associated with the selected consultant(s) should be displayed in the list.

17

Scenario: Filter by Process Type
Given multiple similar vacancies with different process types
When the recruiter applies a process type filter
Then only similar vacancies matching the selected process type(s) should be displayed in the list.

18

Scenario: Start process
Given the similar vacancies list
When the recruiter click the icon to start the process
Then the system should the dialog to start the process

01

Scenario: Displaying publication list
Given a vacancy is selected
When the recruiter views the "Publications" tab
Then a list of all publications associated with that vacancy should be displayed, showing columns for Date, Status, Name, Company, Category, and Consultant.

02

Scenario: Column for "Date"
Given the "Publications" tab is displayed
When viewing the Date column
Then it should show the date and time of each publication entry in the format DD MMM YYYY HH.

03

Scenario: Column for "Status"
Given the "Publications" tab is displayed
When viewing the Status column
Then it should show the current status of each publication (e.g., "Published", "Draft", "Offline") with a corresponding color indicator.

04

Scenario: Column for "Name"
Given the "Publications" tab is displayed
When viewing the Name column
Then it should display the title of each publication, clickable to navigate to the publication’s details.

05

Scenario: Column for "Company"
Given the "Publications" tab is displayed
When viewing the Company column
Then it should display the name of the company associated with each publication.

06

Scenario: Column for "Category"
Given the "Publications" tab is displayed
When viewing the Category column
Then it should display the category or categories relevant to each publication.

07

Scenario: Column for "Consultant"
Given the "Publications" tab is displayed
When viewing the Consultant column
Then it should display the profile image and name of the consultant responsible for each publication, clickable to navigate to the consultant’s profile.

08

Scenario: Sorting by Date
Given the publications list
When the recruiter clicks the Date column header
Then the list should sort by date, toggling between ascending and descending order.

09

OOS Scenario: Filtering by Status
Given multiple publications with different statuses
When the recruiter applies a status filter
Then only publications matching the selected status (e.g., "Published", "Draft") should be displayed in the list.

10

Scenario: Editing a publication
Given the "Publications" tab is displayed
When the recruiter clicks the edit icon for a publication
Then the system should open the publication’s details in edit mode, allowing the recruiter to update information.

11

Scenario: Deleting a publication
Given the "Publications" tab is displayed
When the recruiter clicks the delete icon for a publication
Then the system should prompt a confirmation dialog, and upon confirmation, remove the publication from the list.

12

OOS Scenario: Multi-select actions
Given the publications list
When the recruiter selects multiple entries
Then bulk actions (e.g., mass delete) should become available in the UI.

13

Scenario: Pagination
Given a large number of publications associated with the vacancy
When there are more than a set number of publications displayed (e.g., 10 per page)
Then pagination controls should appear at the bottom of the list, allowing navigation through multiple pages.

14

Scenario: Adding a new publication
Given the "Publications" tab is displayed
AND recruiter assigned on the related order or there is no order at all.
When the recruiter clicks the "+" button
Then the system should open a form to create a new publication associated with the current vacancy.
AND preselect all fields from vacancy:
– Company
– Order (if exists)
– Contact person
– Vacancy name
– Publication name
– Categories
– all fields from employment conditions
– skills
– benefits
– desriptions
– jobs ch fields

15

OOS Scenario: Filter by Consultant
Given multiple publications with different consultants
When the recruiter applies a consultant filter
Then only publications associated with the selected consultant(s) should be displayed in the list.

01

Scenario: Displaying process list
Given a vacancy is selected
When the recruiter views the "Processes" tab
Then a list of all candidate processes associated with that vacancy should be displayed, showing columns for Date, Company, Vacancy, Status (Time in Status), Consulting, Recruiting, Candidate, and Forecast.

02

Scenario: Column for "Date"
Given the "Processes" tab is displayed
When viewing the Date column
Then it should show the date and time of each process entry with a format (e.g., DD.MM.YY HH).

03

Scenario: Column for "Company"
Given the "Processes" tab is displayed
When viewing the Company column
Then it should display the name of the company associated with each process, clickable to navigate to the company’s page.

04

Scenario: Column for "Vacancy"
Given the "Processes" tab is displayed
When viewing the Vacancy column
Then it should display the title of the vacancy associated with each process and indicate if it’s an "application by download".

05

Scenario: Column for "Status" (Time in Status)
Given the "Processes" tab is displayed
When viewing the Status column
Then it should show the current status of the candidate in the process (e.g., "In Request") along with the duration (e.g., "2 days").

06

Scenario: Column for "Consulting"
Given the "Processes" tab is displayed
When viewing the Consulting column
Then it should display the profile image and name of the consultant responsible for each process, clickable to navigate to the consultant’s profile.

07

Scenario: Column for "Recruiting"
Given the "Processes" tab is displayed
When viewing the Recruiting column
Then it should display the profile image and name of the recruiter assigned to each process, clickable to navigate to the recruiter’s profile.

08

Scenario: Column for "Candidate"
Given the "Processes" tab is displayed
When viewing the Candidate column
Then it should display the profile image and name of the candidate in the process, clickable to navigate to the candidate’s profile.

09

Scenario: Column for "Forecast"
Given the "Processes" tab is displayed
When viewing the Forecast column
Then it should show the forecast value or symbol associated with each process (if applicable).

10

Scenario: Filtering by process status
Given there are multiple processes with different statuses
When the recruiter applies a status filter
Then only processes matching the selected status (e.g., "In Request", "Interview 1") should be displayed in the list.

11

Scenario: Sorting by Date
Given the processes list
When the recruiter clicks the Date column header
Then the list should sort by date, toggling between ascending and descending order.

12

Scenario: Sorting by Company
Given the processes list
When the recruiter clicks the Company column header
Then the list should sort by company name in alphabetical order, toggling between ascending and descending.

13

Scenario: Sorting by Status (Time in Status)
Given the processes list
When the recruiter clicks the Status column header
Then the list should sort by status and time duration, toggling between ascending and descending.

14

Scenario: Pagination
Given a large number of processes associated with the vacancy
When there are more than a set number of processes displayed (e.g., 10 per page)
Then pagination controls should appear at the bottom of the list, allowing navigation through multiple pages.

15

Scenario: Filter by "Rejects Statistics"
Given the "Processes" tab is displayed
When the recruiter clicks the "Rejects Statistics" button
Then a modal or overlay should display rejection-related statistics for the vacancy, breaking down rejection reasons and stages.

16

Scenario: Filtering by Candidate and Company Interaction Status
Given a process with no response from either candidate or company
When viewing the summary bar
Then indicators should show "No reply-candidate", "No reply-company", "Enquiry-company", or "Read" statuses based on recent interactions.

17

Scenario: Multi-select actions
Given the processes list
When the recruiter selects multiple entries
Then bulk actions (e.g., mass status update) should become available in the UI.

18

Scenario: "Filters" button functionality
Given the "Processes" tab
When the recruiter clicks the "Filters" button
Then a panel should open, allowing the recruiter to filter processes by date range, company, vacancy title, consultant, recruiter, candidate, and status.

19

Scenario: Vacancy-specific process statistics
Given the "Processes" tab is viewed for a specific vacancy
When the summary bar at the top is displayed
Then it should show the number of processes at each stage (e.g., Request, Interview 1, Offered, etc.) for that specific vacancy.

01

Scenario: Display candidate list
Given the user is on the "Tab Candidates List" within the "Vacancy view mode"
When the list of candidates is displayed
Then the table should include columns for Name, Status, Salary, Location, Position, Active Source, Company Feedback, and List Type (Favourite, Long, Short).

02

Scenario: Row actions
Given the candidate list is displayed
When the user views a row in the table
Then each row should include icons for "Start Process", "Add to list", and "Delete candidate from the list". "Start Process" is absent if the process has already been created between the candidate and the taken vacancy.

03

Scenario: Row actions. Start Process
Given the candidate list is displayed
When the user views a row in the table and the “rocket” button is present
Then the user clicks on "Start Process" and sees a modal window with the pre-selected candidate and taken vacancy in the modal. Launching the process proceeds by clicking on the blue button in the bottom of the modal.

04

Scenario: Row actions. Add to list
Given the candidate list is displayed
When the user views a row in the table
Then the user clicks on "Add to list" and sees a modal window with the pre-selected candidate and empty vacancy in the modal. Adding the candidate to another vacancy’s list proceeds by clicking on the blue button in the bottom of the modal.

05

Scenario: Preview options
Given the user is on the "Tab Candidates List"
When the user clicks the "Eye" icon at the top
Then a dropdown should appear with options for "Short List Preview" and "Long List Preview".

Story 1.2.5.4. Short list preview

Story 1.2.5.5. Long list preview

06

Scenario: Send list to the company
Given the user is on the "Tab Candidates List"
When the user clicks the "Send List to the Company" button
Then the system should send the list of candidates to the company.

Story 1.2.5.3. Send list to the company

07

Scenario: Add new candidates
Given the user is on the "Tab Candidates List"
When the user clicks the "+ Add Candidates" button
Then a modal should appear allowing the user to add new candidates to the list.

Story 1.2.5.1. Add candidates to the "Favourites" list for sending

08

Scenario: Pagination
Given there are multiple candidates
When viewing the candidate list
Then the list should include pagination controls to navigate through multiple pages of candidates.

OOS Scenario: Upload candidate list
Given the user is on the "Tab Candidates List"
When the user clicks the "Upload New List of Candidates" button
Then the system should add the list of candidates from the file.

OOS Scenario: Filter button
Given the candidate list is displayed
When the user clicks the "Filter" button
Then a filter modal should open, allowing the user to filter by categories, employment type, industries, skills, desired salary, and search radius.

OOS Scenario: Search field
Given the candidate list is displayed
When the user enters a keyword in the search field
Then the list should be filtered based on the search criteria.

OOS Scenario: Default prefilters
Given the candidate list is displayed
When the user views the list
Then the candidates should be prefiltered according to the vacancy criteria.

OOS Scenario: Reset filters
Given the user wants to see all candidates
When the user clicks the "Reset Filters" button
Then all filters should be cleared and the user should see the complete list of candidates.

01

Scenario: Display candidate list
Given the user is on the "Tab Matching" within the "Vacancy view mode"
When the list of candidates is displayed
Then the table should include columns for Name, Status, Salary, Location, Degree, Languages, Categories, and Rocken Contact.

02

Scenario: Add note and create process icons
Given the candidate list is displayed
When the user views a row in the table
Then each row should include icons for "Add Note" and "Create Process".

03

Scenario: Pagination
Given there are multiple candidates
When viewing the candidate list
Then the list should include pagination controls to navigate through multiple pages of candidates.

04

Scenario: Default prefilters
Given the candidate list is displayed
When the user views the list
Then the candidates should be prefiltered to match the vacancy criteria most closely.

05

Scenario: Reset prefilters
Given the user wants to see all candidates
When the user clicks the "Reset Filters" button
Then all prefilters should be cleared and the user should see the complete list of candidates.

06

Scenario: Filter button
Given the candidate list is displayed
When the user clicks the "Filter" button
Then a filter modal should open, allowing the user to filter by categories, employment type, industries, skills, desired salary, and search radius.

07

Scenario: Prefilter visibility
Given the filter modal is open
When the user views the filter options
Then the prefilters that match the vacancy should be displayed by default, with the ability to modify them as needed.

01

Scenario: Display notes
Given the user is on the "Sub tab Notes" within the "Tab Detail" of the "Vacancy view mode" page
When the user accesses the notes section
Then all notes related to the vacancy should be displayed in a list format with the most recent notes at the bottom.

02

Scenario: Note structure
Given notes are displayed in the list
When viewing a note
Then each note should include the text of the note, the name of the user who created it, and the date and time it was posted.

03

Scenario: Add a new note
Given the user wants to add a new note
When the user clicks on the "Add Note" button
Then a modal should open with a text area for the note and buttons "Add" and "Cancel".

04

Scenario: Save new note
Given the user has entered a note in the modal
When the user clicks "Add"
Then the new note should be added to the list and displayed at the bottom.

05

Scenario: No editing or deletion
Given the user is viewing the notes
When interacting with a note
Then the user should not be able to edit or delete any notes.

06

Scenario: Scrollable list
Given there are multiple notes
When the user views the notes
Then the notes list should be scrollable if it exceeds the visible area of the screen.

07

Scenario: Automatically scroll to latest note
Given the user opens the "Sub tab Notes"
When the notes are displayed
Then the view should automatically scroll down to show the most recent notes at the beginning of the list.