01

Scenario: Filter by Statuses
Given the processes list page,
When selecting from the available status filters,
Then the list should display only processes that match the selected status.

02

Scenario: search field location
Given I am on the Process List page,
When I view the page,
Then the search field should be placed on the top-right side of the page.

https://cheitgroup.atlassian.net/wiki/spaces/RD/pages/1027670215/Story+1.6.3.7.+CRM.+Process.+Search+field?force_transition=26fa9d9b-a588-4fe8-b360-f828a0fa4642

03

Scenario: Opening the Filters panel
Given I am on the processes 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. Sales/Account / Sales/Account

2. Management consultant / Management consultant

3. Responsible / Verantwortlich

4. Recruiter / Recruiter

5. Process creation date / Process Erstellungsdatum

6. Last Update / Letzte Aktualisierung

7. Market / Markt

8. Candidate / Kandidat

9. Company / Unternehmen

10. Interview date / Interview Zeit

11. Candidate rejected: reason / Kandidat abgelehnt: Grund

12. Company rejected: reason / Unternehmen abgelehnt: Grund

04

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#/Process/get_api_v1_processes

01

Sales/Account

Scenario: User applies a Sales/Account filter.
Given Sales/Account field,
When select CRM user (all CRM users),
Then results show processes with this CRM users.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

should be added to API by backend developer

02

Management consultant

Scenario: User applies a Management consultant filter.
Given Management consultant field,
When select CRM user (all CRM users),
Then results show processes with this CRM users.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

should be added to API by backend developer

03

Responsible

Scenario: User applies a Consultant filter.
Given Consultant field,
When select CRM user (all CRM users),
Then results show processes with this CRM users.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

should be added to API by backend developer

04

Recruiter

Scenario: User applies a Recruiter filter.
Given Recruiter field,
When select CRM user (all CRM users),
Then results show processes with this CRM users.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

should be added to API by backend developer

05

Process creation date

Scenario: User filters by process creation date.
Given the user inputs "From" and "To" values for process creation date,
When valid,
Then results show processes in the range.

should be added to API by backend developer

06

Last Update

Scenario: User filters by Last update.
Given the user inputs "From" and "To" values,
When valid,
Then results show processes in the range.

updated_from

updated_to

07

Market

Scenario: User filters by market.
Given market options exist,
When one is selected,
Then only processes for that market (country) should be shown.

Select type:

• single select

• single tag

• search OOS

• suggestions OOS

• custom tags OOS

should be added to API by backend developer

08

Candidate

Scenario: User applies a Candidate filter.
Given Candidate field,
When select talent profile,
Then results show processes with this talent profiles.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags OOS

should be added to API by backend developer

09

Company

Scenario: User applies a Company filter.
Given the user enters a Company name,
When the name exists,
Then suggestions are displayed.

Select type:

• multi select

• multi tags

• search

• suggestions

• custom tags

should be added to API by backend developer

10

Interview date

Scenario: User filters by creation date.
Given the user inputs "From" and "To" values for process creation date,
When valid,
Then results show processes in the range.

should be added to API by backend developer

11

Candidate rejected: reason

Scenario: User applies the reason of candidate rejected
Given user interact with dropdown rejection reasons,
When select one of rejection reason,
Then filter automatically applied.

Select type:

• multi select

• multi tags

• search OOS

• suggestions OOS

• custom tags OOS

candidate_rejected[]

Available values :

• working location / Arbeitsort

• qualifications / Qualifikationen

• company profile / Firmenprofil

• already applied / bereits beworben

• custom reason / individueller Grund

12

Company rejected: reason

Scenario: User applies the reason of company rejected
Given user interact with dropdown rejection reasons,
When select one of rejection reason,
Then filter automatically applied.

Select type:

• multi select

• multi tags

• search OOS

• suggestions OOS

• custom tags OOS

company_rejected[]

Available values :

• experience / Erfahrung

• education / Ausbildung

• industry knowledge / Branchenkenntnisse

• salary / Gehalt

• references / Referenzen

• skills / Fähigkeiten

• overqualification / Überqualifizierung

• underqualification / Unterqualifizierung

• custom reason / individueller Grund