Drop Downs
A Drop Down is a reusable list of options you define once and then point at from anywhere in Paminga — a form field, a custom field on a contact, account, opportunity or campaign member, or a field you sync with your CRM.
That reuse is the point. Change "Mid-Market" to "Midmarket" in one place and every form and field using that Drop Down changes with it, rather than you hunting through a dozen forms hoping you got them all.
Your ability to access account settings may depend on the permissions setup by your organization.
Creating a Drop Down
To create a new Drop Down, in the top right corner of the app, select ‘Create Drop Down’.
Once selected, a drawer will appear.
Here you will give your Drop Down a name and then select ‘Create Drop Down’.
Upon creation, you will then be asked to create options for your Drop Down.
This is where you will input any fields which you would like present on your form, or match fields that are present on your Drop Down within your CRM that you would like to sync to Paminga.
To add options, on the bottom of the folder, select ‘Create New Option’. After adding your option, select the checkbox and the field will be added.
You can add as many fields as you would like to your Drop Down. You also have the ability to drag and drop to re-organize.
Editing Drop Downs
The Drop Down Dashboard allows you to edit Drop Downs created within your Paminga account.
To edit a Drop Down, from the dashboard hover over the ‘Actions’ option of the Drop Down.
Here you can select to ‘Delete’ or ‘Edit’.
Editing allows you to:
- Update the Drop Down name
- Edit each drop down option:
- Select the pencil icon of each option to edit the value of the option
- Delete an option via the trash icon
- Drag and Drop to re-organize how the options appear in the Drop Down
Localization / Internationalization
A Drop Down's options carry two pieces of information: a value, which is what gets stored on the contact record and synced to your CRM, and a label, which is what a person actually reads. Translating a Drop Down changes the labels only. Values never move, so your reporting, segments, and CRM sync are untouched no matter how many languages you add.
That matters because the same Drop Down is reused across every form that references it. Translate it once and every internationalized form using it picks up the translations.
The Drop Down's Own Language
Every Drop Down records the language its own labels are written in — the starred entry in the Languages bar at the top of the edit drawer. New Drop Downs start in whatever language your browser is set to, so if you work in French, your Drop Downs start as French rather than as English you then have to correct.
Click the pencil on the starred language to change it. You can't set it to a language you've already translated into; remove that translation first, otherwise two sets of labels would both claim to be the same language.
Adding a Language
Click "Add a Language" in the Languages bar, pick a language, and you'll get a dialog listing every option with its original label on the left and an empty field on the right.
Fill in all of them. Save stays disabled until every option has a label, and the counter at the bottom left tells you how many are done.
This is deliberate. A half-translated Drop Down would show a Spanish form with two Spanish options and four English ones, which looks worse than not translating it at all. Paminga would rather you finish the language or cancel it than ship something inconsistent.
The fields start empty rather than pre-filled with the original. Plenty of options are identical across languages — product names, for instance — and typing one out is a deliberate act, where pre-filled text lets a language be "translated" by clicking Save.
Adding Options Later
Once a Drop Down has languages, the Create/Edit Option form asks for a label in each of them. You cannot save an option without them.
This keeps the all-or-nothing promise true over time. Without it, adding a thirteenth option to a Drop Down translated into French and German would quietly leave both languages incomplete, and you would find out from a prospect looking at a form.
Removing a Language
Click the ✕ on a language to remove it. Every label for that language is deleted, and forms rendering in it fall back to the Drop Down's own labels.
How Paminga Chooses Which Labels to Show
A form's languages and a Drop Down's languages are separate. The same Drop Down gets reused across many forms, so a form can easily be published in a language nobody has translated that Drop Down into.
When someone views your form, Paminga works out the language for the form, then picks that Drop Down's labels this way:
| Situation | What the visitor sees |
|---|---|
| The language matches the Drop Down's own language | The Drop Down's own labels |
| You've translated the Drop Down into that language | Your translations |
| You've translated it into the base language — French, for a French (Canada) visitor | Your French translations |
| You haven't translated it into that language at all | The Drop Down's own labels |
That last row is the one worth remembering: a Spanish form can show Spanish field labels above a Drop Down whose options are still in English. Nothing is broken — the options simply have no Spanish labels yet. Add Spanish to the Drop Down and they'll follow.
Values are never translated. Whichever language a visitor sees, the value stored on the contact and synced to your CRM is identical.
Values and Labels
Every option carries two things, and the distinction matters more than it first appears:
- The value is what gets stored on the record and synced to your CRM. It's the data.
- The label is what a person reads on a form. It's the presentation.
Leave the value blank and it takes the label. But when the two need to differ they can, and that flexibility is what makes a Drop Down survive contact with a CRM. Your Salesforce picklist may expect ENT-001 while your form should say "Enterprise (1,000+ employees)". One option, both truths.
Because the value is the stable part, you can rewrite a label — or translate it into six languages — without touching a single stored record, breaking a segment, or re-mapping anything in your CRM.
Where Drop Downs Show Up
Once a Drop Down exists, it's available to:
- Forms — add a Drop Down element and choose which Drop Down supplies its options
- Custom fields — a contact, account, opportunity or campaign member field of type Drop Down draws its allowed values from one
- CRM sync — a picklist coming from Salesforce or Dynamics needs a matching Drop Down on the Paminga side so the two agree on what a valid value is
- Segments — because the values are constrained, segmenting on them is exact rather than a text match that misses "Mid-Market" when someone typed "mid market"
Before You Start
Two things worth deciding up front, because both are far cheaper now than later:
Match your CRM first. If a field syncs, build the Drop Down's values to match the picklist on the other side exactly. Paminga will match on value, and a near-miss is still a miss.
Think about who reads the labels. If you sell internationally, know that option labels can be translated — so write labels for humans and let the values carry the machine-readable form.
Your ability to access account settings may depend on the permissions set up by your organization.
