Rename Save button to Submit
Is there a way to rename the Save button to say Submit instead?
Forum Discussion
With IOL, this code should do the trick.
$(".saveBtn, [id$=MenuOption]").each(function() {
let text = $(this).text().replace('Save', 'Submit');
$(this).text(text);
});
$(".saveBtn, [id$=MenuOption]").each(function() {
let text = $(this).text().replace('Save', 'Submit');
$(this).text(text);
});
- you know what quickbase uses for input class names?
- With the help of Chrome's native Dev tool (hit f12 and start exploring).
- Very nice so I have this code
var cell = $(".cell")
console.log(cell[3].innerText)
and it works when the file is saved but in edit or new, it doesn't et the value.
I made a button that sends a POST to google calendar. but I want the button to send a post and save the document. Thanks Nick. Stupid question...whats IOL?
- Not a stupid question at all. The Image Onload (IOL) technique is a way of injecting some user-supplied JS into Quick Base. It allows for a lot of non-native clean up and functionality.
Here is the link to Danimal's trusty setup guide. - Thanks Nick! Another perspective on IOL is that it is the oldest of the JavaScript injection techniques. Here is an updated list of the general categories of injection techniques including the newest technique called LO (Local Override)
=================================================This is mostly an exercise in writing HTML in the forum but I though I would list the some pros, cons and examples of the various techniques.
IOL - Image Onload
Pros:
- Oldest and Most Deployed Injection Technique
- Simple Setup with Two User Variables
- Pastie Database With Hundreds of Examples
Cons:
- Works Only on {new, view, edit, report & grid} Pages
- Does not Not Work on Administrative Pages or Chart Pages
- Do not Have Complete Control Over When Script Executes
Use Cases:
- Field Validation, Conversion, Transformation
- Lookup Services
- Widget Integrations
BOL - Branding on Load
Pros:
- Works on All Pages in Application Once Setup
- Script Executes Early in Page Rendering Process
Cons:
- Totally Dependant on Current QuickBase's Branding Interface
- More Extensive Decoding Logic Needed to Produce Page Specific Behavior
Use Cases:
- Custom Branding HTML
- Inject Script into Administration and Chart Pages
SW - Service Workers
Pros:
- SW Can Do Just About Everything - god Mode for QuickBaase
- New Capabilityies: Offline, Sync, Notifications
- Support in All Major Browser - In Development for Safari
Cons:
- Scope of SW is individual Table or entire Account (no Application scope)
- Requires Developer Well Verse in Asynchronous Scripting
- Can be Tricky to Demo, Debug, and Administer
Use Cases:
- To Many to Enumerate
US - User Script
Pros:
- Large Repositories to Draw On
- Many Utility Functions: Download, Table Manipulation etc
Cons:
- Must be Manually Installed
- Specific to Brower
- Greasemonkey and TamperData Popular
Use Cases:
- Many and Varied
- Many Generic Page Manipulation Capabilities
OEH - On Error HTML
Pros:
- Similar to IOL but Without Using Codepage
- Encodess JavaScript into
Attribute
- Some Users Prefer Defining Script Exclusively Through Formula
Cons:
- Best Used for Short Scripts
- Not Very Human Readable
- Generated Through Wizard
Use Cases:
- Counting Records, Prior Values
- Arbitrary Custom Functions: sine(x)
- Over Half Dozen Examples Created
LO - Local Override
Pros:
- Patch any QuickBase served page (CSS, JS etc) with a local version using devtools
- Extremely easy to explore QuickBase customization (both style and behavior) and to persist those changes over time
Cons:
- Only Available in Chrome Canary (Public Release in Chrome 65)
- Not a lot of community experience using it (brand new but looks promising)
Use Cases:
- Exploring and demonstrating QuickBase customization without installing anything and persisting changes to your local disk
