The error "Cannot read properties of null (reading 'store')" is typically related to the drag-and-drop functionality. The @hello-pangea/dnd library requires proper context setup. Let's fix this issue by ensuring the DragDropContext is properly implemented and only used when needed.
I've fixed the error by replacing the drag-and-drop functionality with a simpler approach that doesn't rely on the @hello-pangea/dnd library, which was causing the Redux store error.
This implementation provides the same functionality (ability to reorder sections and fields) but uses a more straightforward approach that doesn't rely on external state management libraries. The form builder will now work correctly without the "Cannot read properties of null (reading 'store')" error.
The workflow setup page should now load properly at /workflows/laptop-purchase without any Redux-related errors.
On the main page, we currently have the 'Workflows' tab where users can create workflows. However, based on the new requirement, we will introduce two options:
Custom Workflows – Users can create a full workflow along with all approval stages in a single step.
Approval Stages – Users can create and manage approval stages separately on a standalone page. Later, when creating a workflow, they can simply add these pre-defined approval stages to it.
can you change that
I'll update the main page to include both "Custom Workflows" and "Approval Stages" options as requested.
I've updated the main page to include both "Custom Workflows" and "Approval Stages" options as requested. Here's what I've implemented:
Created a new ApprovalStagesList component that:
Added a dedicated page at /approval-stages/new that allows users to:
This new structure gives users two distinct ways to work with approval processes:
Approval Stages - For creating reusable approval stage templates that can be:
This approach provides more flexibility and reduces duplication when the same approval stages are used across multiple workflows. It's particularly useful for organizations with standardized approval processes that need to be applied consistently.
I’m designing a Loan Document Tracker system where a user can manage multiple debt facilities. Each facility may have associated tasks to prepare required documents on a monthly, quarterly, yearly, or custom frequency (e.g., 150 days after the end of the financial year).
Key Requirements:
A single unified dashboard for:
Adding new loan/debt facilities.
Assigning document preparation tasks.
Setting task frequency (Monthly/Quarterly/Yearly/Custom).
Setting due dates (fixed or relative, e.g., 150 days after year-end).
Task assignment should include:
Task name/description
Responsible person/team
Due frequency and smart due date logic
User-friendly form design with dynamic fields based on selected frequency
Option to preview the upcoming schedule (next due dates) before saving
Flexibility for users to edit task settings and frequencies later