PeakZebra template applications are designed to get the core job done. But you may want some changes to make the application really fit your needs.
No problem. Queue up a change and it’ll be processed in two days.
| Enqueue
| Request |
Description |
Level |
Actions |
|
Add a field to an existing table | Tell us what you\’d like the field to be called (that is, what appears above the edit field in a form or at the top of a column in a table. | two | |
|
Create a calculated field (column) in a PZ database table. | Add a column to a database table that is calculated using a formula that works with other fields in the table and possibly with other outside data (such as the current date). | 4 | |
|
Create new custom table | Not a common request, but if you have a particular data set that doesn\’t lend itself to being stored in the preset data tables used by PZ, we can construct a new one to your specs. | Custom | |
|
Change the name of a column in a PZ table in the database | This changes the name of the field in the database. It doesn\’t directly affect the name with which that field will appear in any forms or grids that use it. Usually, it\’s better to just change how the name appears as a prompt or column head in relevant grid and table blocks. | 3 |
|
| Enqueue
| Request |
Description |
Level |
Actions |
|
Change column order in grid block | Move around columns so that they display in the order you\’d prefer users saw them. Note that in the case of React-based grids, users will still be able to reorder columns on the fly, for that session only. | 3 | |
|
Add or drop a column from a grid (table) display. | This changes the display name at the top of a column. It does not change the actual field/column name within the PZ database. | 1 | |
|
Change the CSS for elements of a grid (table) display. | You can change the look of pretty much any element of a grid display in terms of color, margin, and interior padding. | 2 | |
|
Change the name that appears at the top of a column | This doesn\’t change the column name in the underlying database table, just the column display name. It\’s useful for using tables in different contexts. | 1 |
|
| Enqueue
| Request |
Description |
Level |
Actions |
|
Add calculated display value to a form. | If you want to show the extended value of an invoice item on a form, you could use this to show unit price multiplied by quantity. | 2 | |
|
Change the layout of a form block. | If you don\’t like the default order in which fields appear in a form, you can change that here, along with details such as whether fields appear in one column or two. | 3 | |
|
Enable or disable standard validation for a form field. | Use this when you want basic validation (phone number is all numbers and punctuation, for example) for field input. If it\’s on and you don\’t want it, use this request as well. | 1 | |
|
Change or add placeholder text in form field | Placeholder text is the light gray text that appears in the input fields of forms before the user has added data. This text can be useful for giving users guidance about how to fill in that field. | 1 | |
|
Add custom validation for form field. | Custom validation enables you to ensure that the user is entering valid data in a form field. Usually, custom validation will take place on the server and the page will reload with an error message if the field entry isn\’t correct. | 3 |
|
| Enqueue
| Request |
Description |
Level |
Actions |
|
Add dashboard display block. | If you have a key metric either stored in a PZ table or calculated from data stored there, we can build a custom block to display that data as a number, gauge, or chart. | 4 | |
|
Add new user role to access control block. | If you create a new role that a user might have (not just subscriber, editor, and so on), this enables you to refer to that role in controlling access to a page. | 2 | |
|
Add custom shortcode | Creates a shortcode either for an existing field in the PZ database that doesn\’t already have a shortcode or for a calculated or system-level value. | 3 | |
|
Add or alter a conditional workflow branch | When a form is submitted, different answers in the form can lead to redirecting to different pages. | 4 |
|
When you place a request into your queue, you’re charged $59 for that month. During that month, you can put as many requests as you want in the queue, and we’ll knock them off them one at a time, with a turnaround time of two days or less for each request (for level one requests — each level above one adds a day to the turnaround time window, to allow for more complex tasks).
It’s the most cost-effective development team you’re ever going to hire, but don’t take our word for it. You can start using a template and making change requests right now. We’ll give you a week of change requests for free, no credit card required.
Get started
| ID |
Category |
Request |
Description |
Details |
| workflow-logic | logic | Add or alter a conditional workflow branch | When a form is submitted, different answers in the form can lead to redirecting to different pages. | none |
| grid-add-drop | grid | Add or drop a column from a grid (table) display. | This changes the display name at the top of a column. It does not change the actual field/column name within the PZ database. | none |
