--- title: "New Features Policy" type: "wiki" space: "Axero Documentation" author: "Anonymous User" created: 2019-07-16T20:39:00Z updated: 2026-09-28T00:09:03Z tags: ["features", "policy"] url: "https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/33698/new-features-policy" --- # New Features Policy Our clients directly shape how the Axero platform grows. From the start, we've worked with them to extend communication, knowledge management, and collaboration into new areas, with a focus on features that are useful. ## Summary - While we have internal road maps for future releases, we don't publish road maps with specific release dates. - We track suggested features and improvements in our public [Suggestions and Feedback](https://my.axerosolutions.com/spaces/77/axero-online-support/forums/6118/suggestions-and-feedback) discussion forum, where comments from clients are welcome and visible to everyone. - Our product managers and Client Success Team review the suggestions regularly. - We choose and schedule new features based on several factors, including the resources they need and their expected impact and benefit. - We aim to provide consistent updates, but we cannot guarantee that our team will address every feature request. This policy does not apply to bugs. See our [Online Support](https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/33697/online-support "Online Support") to learn about our approach to bug fixing. ## How to Suggest a Feature To request a feature, start by posting it in our public [Suggestions and Feedback](https://my.axerosolutions.com/spaces/77/axero-online-support/forums/6118/suggestions-and-feedback) discussion forum. Comments from other clients there help us understand the request and how it might be valuable for all clients. Include every detail you can, with examples, use cases, user flows, or diagrams that show why you need the feature. Describe what it might look like, how it should work, and the impact it might have on your organization. For each feature request, we first ask: *Where does it fit in the Axero product roadmap?* The answer leads to one of three paths: 1. **We're not going to do it:** We tell the client, so they know whether to look for a workaround, build their own integration with our REST API, or consider switching to another product. We will help either way. 2. **We'd like to do it:** This may be a feature we've discussed internally, one already scheduled on our road map, or one on our road map that is not yet scheduled. We look into it further, starting with what the client was experiencing when they decided to submit the request. Once we know more, our product team can consider options. 3. **We don't know:** This is like the second path, but we haven't yet worked out where the feature fits in the product roadmap or what value it provides. We may explore these features in the future. Our Client Success Team may ask for more information about the feature to find out whether: - We have already implemented the feature, but the feature works differently than you expect - A workaround is already in place - We are already working on the feature - We have determined that we cannot accommodate the requested feature ## How to Track When Features are Implemented We update our products continuously. To see the latest changes, updates, bug fixes, and new features, see the [New Enhancements](https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/30048/new-enhancements "New Enhancements") page. ## How We Choose What to Implement When we plan a new feature release, we weigh many factors to decide which suggestions to implement, including: - **Client feedback:** Client interviews and other research activities, comments in our Suggestions and Feedback forum, questions, and posts on support community forums. - **Client Success Team insights:** Our support team knows which issues are the most challenging and common for clients. - **Product analytics:** Some clients opt in to send us analytics, which helps us understand how existing features are used. - **The difficulty of implementing the proposed improvement:** Some features are straightforward and provide 10x value, while others look simple but require months of complex engineering. - **Product strategy:** Our long-term strategic vision for the product. ## What Happens When We Choose to Implement Features While we have internal roadmaps for future releases, we don't publish roadmaps with specific release dates. Axero management has set internal policies so that the systems we build meet the user's requirements within the agreed cost, schedule, and quality guidelines. Our System Development Life Cycle policy \(SDLC\) gives development projects a structured process. The Axero SDLC has the following phases: - **Determine System Need:** We identify a need for an information system and decide whether to commit the resources needed to meet it. - **Define System Requirements:** We break the User Requirements down into more detailed requirements. - **Design System Components:** We turn the detailed requirements into complete, detailed specifications that guide the work of the Development Phase. - **Build System Components:** We turn the detailed system design into complete coded software units and, eventually, into an integrated product for release. - **Evaluate System Readiness:** We confirm that the system, as designed and built, meets the user's requirements. - **Deploy the System:** In this final phase, we release the system first to a pilot site and then to the production environment. ### Methodologies A process model covers the whole life cycle and defines each phase described above. It also defines the tasks and activities performed within each phase. Axero mainly follows Agile \(Scrum\) system development, which works in short, repeated cycles. It occasionally adds Waterfall methods for more structure during the Evaluate System Readiness phase. The Axero Software Development Team is self-directed. It works in successive iterations \(typically 2 to 3 weeks\) and adjusts its development plan at the end of each one. While we work through our SDLC, we often ask clients for feedback and guidance on how to meet their expectations for new features, through formal client interviews and group brainstorming sessions. Occasionally, at our discretion, and when we feel it helps our development team, we give clients access to alpha releases and/or trial installations \(early test versions\) to check that features work. ## How to Get Access to New Features and Improvements Cloud clients: Your site receives new enhancements when we upgrade it to a new General Release, usually at the end of each month. We schedule each upgrade and email you beforehand \(see [Cloud Site Upgrades](https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/34621/cloud-site-upgrades "Cloud Site Upgrades")\). On-premises clients: To get new features and software updates, upgrade to a release that contains the change. To schedule your upgrade, [open a support case](https://my.axerosolutions.com/spaces/77/axero-online-support/cases/add-edit-case/0) with our Client Success Team. #### Related pages - [Cloud Site Upgrades](https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/34621/cloud-site-upgrades "Cloud Site Upgrades") \(how a new feature reaches your site\) - [Online Support](https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/33697/online-support "Online Support") \(how to report a bug rather than suggest a feature\)