![]() This would be useful for a full 30 to 40% of the sites in my database. Strongbox West is Atlanta's biggest and most bad-ass coworking facility, providing funky-but-professional. I realize this is likely more complex than I'm imaging, but would love to see such a feature if it is technically feasible. A small decorator or new column could be used to distinguish between custom fields with mappings specified versus those without. ![]() So as in this example, a dropdown to select " id" and a textbox to enter " account". What I'm envisioning in my head is something like an additional " Map to Form" checkbox which would display a couple of new form elements asking a user to select from common attributes (such as id, name, class) or specify a custom attribute - then enter the value for which the custom field should be mapped. When creating a Custom Field, Strongbox allows fields to be marked Concealable. In this example, the form's inputs appear as below: For sites that don't utilize the ID attribute, other attributes could be specified for use in determining where to map and populate custom fields. In this example, AWS uses the ID attribute to identify form fields. Specify an attribute for form elements to which the custom field should be be mapped (for example, " input field where id = account") ? ![]() Mark specific custom fields (such as Account ID) as "populatable", and Safari: Strongbox populates only the IAM User Name fieldįor each of the entries, I have a custom field defined that holds either the Account ID or Account Alias. When selecting one of these entries to populate on the page:Ĭhrome: Strongbox places the username in both the Account ID and IAM User Name fields I have multiple entries in my database for AWS. It would be phenomenally helpful to be able to mark custom fields as "populatable" for websites.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |