FinDock feature maturity stages
Features go through three stages of maturity. Each stage carries special significance, as explained below.
Pilot feature
This is our first phase of public testing. In this phase, FinDock requests customers to evaluate new features. Piloting often requires additional information from eligible customers and special support from FinDock. Based on the results of the pilot, FinDock decides if the features deliver the anticipated value for customers and if they are mature enough to move to the next stage. Like the features, new documentation provided during this phase is draft only and subject to change.
Beta feature
This stage involves rolling out features for general testing. Beta features might require special actions (usually by a system administrator) to be able to use them. Beta features are not covered by FinDock’s SLS. Although feedback is welcomed and used to improve the feature, FinDock cannot guarantee:
- tickets describing problems with Beta features will be handled according to the SLS.
- timely fixes for any problems you encounter with beta features.
Generally Available feature
Once a feature has passed the pilot and beta phases, it will be formally included in a FinDock release as Generally Available (GA). These features are considered complete, and FinDock provides regular, full support.
Feature maturity FAQs
Am I guaranteed participation in a pilot program?
No, each request is reviewed individually. Each pilot has a separate set of requirements and may require experience with an existing feature. Some pilot programs also have a limited number of seats.
When a feature moves to the next maturity stage, will it behave exactly the same?
Maybe, but not always. We use feedback gathered during the pilot and beta stages to decide whether to reject, modify or move the feature into GA. But the rate and range of changes is lower with each subsequent maturity stage.