Overview

Organisation users can now launch the Create Request modal — to start a Quick Form (RFx) or Detailed Form (Legacy RFQ) — directly from a Project page, the Project Folders view, or a package inside a Procurement Schedule, as well as from the existing RFQ Listing entry point. This article explains how to use the Create Request modal, how the Project and Folder fields pre-fill depending on where the modal is opened, how to optionally import Project documents into the new event, and how the resulting document groups are ordered in the RFx Attachments section.

Previously, RFx events (Quick Form requests) were primarily accessible from the RFQ Listing. These additional entry points make it faster to start a sourcing event from the Project context where the work is already happening.

Key rule: when an RFx is created through the Create Request modal, Felix always applies the Detailed Request RFx template — there is no template selection step in this flow.

Prerequisites & Permissions

• The RFx sub-feature is enabled for your organisation. If it isn't, the original Create New RFQ modal remains unchanged, with no Quick Form / Detailed Form selector shown.
• You are an organisation user with permission to create RFQs in the relevant project and folder.
• You have Project and Folder level access on the Project and Folder you wish to create a new Request for. 

How to Create an RFx Event

Launch the Create Request Modal

Open the Create Request modal from any of the following locations:

Entry point	Action
RFQ Listing	Click Create New RFQ
Project page (any sub-page except Summary and Procurement Schedule views)	Click New > Request from the page-level action dropdown
Project Folders page	Click the ellipsis (…) action on a folder, then select Add RFQ
Procurement Schedule (single package)	Click the Create RFQ ellipsis or caret action on a package row
Procurement Schedule (multiple packages)	Select qualifying packages with the bulk-select checkboxes, then click Create RFQ in the bulk action bar
Procurement Schedule page	Click New > Request from the page-level action dropdown

 

Only packages with a qualifying status (for example, In Progress — not Placeholder) can have an RFQ created from them, and a package must have a Category and Budget assigned. These pre-existing rules are unchanged by this workflow.

 

 

Confirm the Project and Folder

The Project field behaves differently depending on where the modal was opened from:

• • From a Project or Procurement Schedule: the Project field is pre-filled with the current project and is read-only — the project cannot be changed.
  • From the RFQ Listing: the Project field is editable and empty by default, and is required — clicking Create with an empty Project field shows a validation error and blocks creation.

The Folder field pre-fill logic (once a project is selected):

• • • If the project has only one folder, that folder is pre-filled.
    • If the project has more than one folder, the folder with the highest number of existing (non-deleted) RFQs is pre-filled.
    • If all folders have the same number of RFQs, the oldest folder (lowest database ID) is pre-filled.
    • Only folders your permission level allows you to see are included in the pre-fill logic and available in the dropdown.

 

Import Project Documents (Optional)

If the selected project has documents in its Documents section, the Import project documents checkbox is active and unchecked by default. If the project has no documents, the checkbox is inactive (greyed out).

To import project documents, check Import project documents.

5. • The Document Group selector appears with an All Document Groups badge pre-filled by default.
   • Click the Document Group selector to choose specific document groups — only groups that contain at least one document are listed.
   • Selecting a specific document group replaces the All Document Groups badge with your selection.
   • If you remove all selections from the Document Group selector, the Import project documents checkbox automatically unchecks. Re-check it to restore the All Document Groups default, then make new selections if needed.

 

Select Quick Form (RFx) or Detailed Form (Legacy RFQ)

In the Create Request modal, Quick Form is selected by default.

• • Select Quick Form to create an RFx event — the Detailed Request template is applied automatically, with no template step shown.
  • Select Detailed Form to create a Legacy RFQ instead.

Understand Document Group Ordering in RFx Step 1

After the RFx event is created, the Attachments section of RFx Step 1 displays document groups in the following order:

Import selected?	Default groups in RFQ Settings?	Document groups shown	Display order
No	No	Default group from the RFx template only	Template default
No	Yes	Default groups from RFQ Settings	RFQ Settings order
Yes	No	Project document groups with documents (as selected)	Alphabetical A → Z
Yes	Yes	Default groups from RFQ Settings, plus selected project document groups	RFQ Settings order first, then A → Z for project groups

Review Pre-filled Fields in the Created Request

After clicking Create, the new RFx or Legacy RFQ is pre-filled with data from the Project or Package context:

• RFx (Quick Form): the Start Date, End Date, and Description fields are pre-filled from the Project, if those fields are populated there.
• Legacy RFQ (Detailed Form): the Start Date, End Date, Description, and Location (Country and Suburb) fields are pre-filled from the Project, if populated.
• When creating from a Procurement Schedule package: the Category field in RFx Step 1 is pre-filled from the package and set to read-only, with help text and a tooltip beneath it — including the package title as a hyperlink that opens the package view in a new tab.

Location fields are not pre-filled for RFx events, because the RFx form uses a different location field structure to the Legacy RFQ form.

Troubleshooting

Issue	Likely cause	Resolution
The Create New RFQ button opens the old modal with no Quick Form / Detailed Form selector	The RFx sub-feature is not enabled for your organisation	Contact your organisation admin to enable the RFx sub-feature
The Project field is blank and editable even though the modal was opened from a Project page	The modal was actually opened from the RFQ Listing, or a page navigation issue occurred	Navigate back to the Project page and use New > Request from the page-level action dropdown
The Import project documents checkbox is greyed out	The selected project has no documents in its Documents section	Add documents to the project first, or proceed without importing project documents
A validation error appears on the Project field when Create is clicked	The Project field was left empty — this only occurs when opening the modal from the RFQ Listing	Select a project from the dropdown and try again
The Document Group selector disappears after all selections are removed	Removing every Document Group selection automatically unchecks Import project documents	Re-check Import project documents to restore the All Document Groups default, then make your selections
The Category field in RFx Step 1 is locked and cannot be edited	The RFx was created from a Procurement Schedule package — the Category is pre-filled from the package by design and is read-only	This is expected behaviour. To use a different category, create the RFx from the RFQ Listing instead

Related Resources

• Legacy RFQ vs RFx Comparison
• RFx Template Configurations