Use this workflow to ask the PAX team for a new capability or an improvement to an existing PAX workflow.
When to use this workflow
Use Feature Request when PAX does not do something you need, when an existing workflow could be easier, or when a repeated workaround should become part of the system.
Do not use a feature request for something that is broken right now. Use How to Report a Bug when PAX shows an error, saves the wrong result, blocks a valid workflow, or behaves differently than expected.
Before you start
You need:
- Access to the main PAX dashboard.
- A clear description of what you want PAX to do.
- The screen, module, report, or workflow where the request belongs.
- Any workaround you are using today.
Screen path
Dashboard > Feedback > Feature Request
Steps
- Open the main PAX dashboard.
- Select
Feedback. - Confirm
Feature Requestis selected. - In
Description, explain what you want PAX to do. - Include the screen, workflow, report, or business process the request relates to.
- Include any workaround you use today.
- Select
Send. - Wait for
Feature request sent. Thank you. - Select
Closewhen finished.
Feature request format
Use a format like this when it helps make the request clear:
Screen or workflow:
What I want PAX to do:
Why this would help:
Current workaround:
Example record or situation:
Good feature requests are specific. For example, mention the exact report, dashboard card, button, field, or workflow where the improvement would fit.
What happens behind the scenes
PAX sends the feature request through the tenant's saved Email Configuration.
The message includes your description, the current page URL, browser information, tenant, submission time, and user identity where available. Feature requests do not include screenshots.
PAX records successful and failed sends in email logs. A successful send does not automatically create a ticket, schedule work, or change PAX behavior.
Feature requests do not affect accounting, inventory, costing, lot traceability, statuses, audit history, or business records.
Troubleshooting
I am not sure whether this is a feature request or a bug report
Likely cause: The request involves an existing workflow that may be incomplete or may be malfunctioning.
Safe fix: If PAX is working as designed but you need something more, use Feature Request. If PAX is showing an error or doing the wrong thing, use Bug Report.
Contact support if: The issue blocks work and you are not sure which option to use.
Send is disabled
Likely cause: Description is blank or PAX is already sending the request.
Safe fix: Enter a description and wait for any active send to finish.
Contact support if: A description is present but Send remains unavailable.
Please enter a description
Likely cause: The description contains only blank space.
Safe fix: Enter a short explanation of the feature you want and try again.
Contact support if: A non-empty description still triggers this message.
Description must be at most 5000 characters
Likely cause: The request is longer than the allowed description length.
Safe fix: Shorten the request to the main workflow, desired result, and workaround. Send a follow-up if more detail is needed later.
Contact support if: A shorter request still triggers the limit.
I need to include a screenshot
Likely cause: Screenshots are only available on Bug Report.
Safe fix: If the screenshot shows a broken or confusing current behavior, use Bug Report. If this is still a feature idea, describe the screen and workflow in the request.
Contact support if: You cannot explain the feature clearly without a screenshot.
Email is not configured for this tenant
Likely cause: The tenant does not have saved Email Configuration.
Safe fix: Ask an admin or executive user to configure and test outgoing email.
Contact support if: Email Configuration is saved and test emails work, but feature requests still cannot send.
Failed to send report
Likely cause: The outgoing email service rejected the message or returned an error.
Safe fix: Retry once. If it fails again, ask an admin or executive user to send a test email from Email Configuration.
Contact support if: Test emails work but feature requests continue to fail.