13.2. Feature Requests
In addition to error diagnosis, SuCri thrives on the ideas of its users. In this chapter, you will learn how to suggest new features, which channels are available to you, and what information is necessary for an efficient review by our team. We structure this process into objectives, submission methods, required content, and the subsequent procedure after your submission.
Objective of Feature Requests
The continuous submission of suggestions for improvement primarily pursues the following goals:
- Further development of SuCri according to the specific needs of the users.
- Integration of industry-specific requirements.
- Improvement of efficiency and user-friendliness through practical suggestions.
Channels for Feature Requests
You can send your requests to us in two ways:
1. Directly from within SuCri:
Using the command SuCriSendSupportRequest, you can submit not only errors but also feature requests. Please select the option Feature Request in the Subject field.
2. Via Email:
- Send your request directly to the helpdesk at: helpdesk@integadesign.de
Content of a Feature Request
To help us review your idea as effectively as possible, we recommend providing the following information:
- Description: A brief explanation of the desired feature.
- Use Case: At which point in the workflow should the feature support you?
- Benefit: What specific advantages does the feature bring to you or your team?
- Urgency: Is it a "nice-to-have" or a critical requirement?
Procedure after Submission
Once your request has been received by us, processing takes place according to this pattern:
- Your request will be thoroughly reviewed by the IntegaDesign team.
- Depending on relevance and feasibility, it will be included in the strategic development roadmap.
- The Release Notes transparently document which feature requests have been successfully implemented.