Extension-point request — ask for a new extension point, or for more from a published one
For: an iVendNext Partner, a licensed customer's IT team or the CitiXsys Consulting Team whose blueprint has a need that no rung of the ladder can meet. These forms are for onboarded members (who can file). Reference: the extension-point catalogue (guide chapter 9, The extension points, and how to ask for a new one).
An extension point is a fixed question we ask your service at a published moment, with a closed set of answers and a stated behaviour when your service is down or the till is offline. It is the last rung of the ladder. Describe the need, not the mechanism: a request that needs money changed in a hook, an override or in-tenant code is read as a request for the need to be met another way.
When to use it
- Your blueprint has a row with no door, or whose door is marked needs a point request.
- A published extension point lacks something you need: a field in the data in, an answer, a moment in the sale. Say which one and what is missing.
Use another form if: the page that explains a door is wrong → recipe or document gap; a kit piece misbehaves → kit defect; you only want to see a pattern worked → sample request.
The form
# Extension-point request: <one-line title>
## 1. What you need to do
<The need in the customer's business terms, and the step it concerns: sale, return, scan, customer add or back office. No names, no shoppers' data.>
## 2. The closest extension point
<Its name as guide chapter 9 gives it and what is missing, or "none".>
## 3. If it is never built
<What you do instead, and what it costs the customer.>
- [ ] It touches a sale, a price or a payment
What we may ask you next, in the issue
Your blueprint and the rows this concerns · the doors you tried and why each falls short · the facts your service needs (the data in, with any personal data marked) · the closed list of answers you need · what the till should do when your service is down · the longest the cashier should wait · what should happen on a till with no network · one sample request and answer, including a refusal · the busiest hour's volume (calls, stores, tills).
A request that does not say what happens when your service is down, slow or offline gets those three questions back.
What happens after you send it
- It is given an id, which comes back to you in the issue.
- It is answered in the issue with one of: answered (a published door already meets it, and the answer says which), needs more, planned (an extension point is specified or extended, and you can follow it) or declined (with the reason, for example that it breaks one of the four rules).
- A planned extension point joins the catalogue. The ladder class of your blueprint's rows changes only when it ships. We give no date.