July 2016 Release Notes

ReleaseNotes_January

20160324_ReleaseNotes_blog_post_1036x463_July17
Hope everyone had a sparkling 4th of July!  We’re continuing the fireworks with the July release of QuickBase. This month we’re rolling out features and fixes geared to make advanced builders even more productive.

User Tokens

Now you can create your own user tokens in QuickBase and use them to run APIs and automation. Many API calls that use a ticket today can instead take a new parameter called usertoken. You can still use the ticket method if you prefer. The new parameter can be used with any API that doesn’t post to a db/main URL, and also with API_GrantedDBs.

User tokens offer an array of benefits, including:

  • Greater convenience, because user tokens are pre-generated, and don’t require a call to API_Authenticate.
  • SAML/LDAP customers can use QuickBase APIs without creating a robot user or Gmail user. With user tokens, now SAML users can create a token and use the API as themselves.
  • If you’re a QuickBase Solution Provider, you can add user tokens to your scripts that won’t expire, so you won’t have to find and fix authentication-error scripts for your customers.
  • Enhanced security:
    • The scope of action is limited to just the apps you’ve assigned the user token to.
    • You can easily unassign a token from an app.
    • The user token can’t be used to authenticate to the user interface (e.g., in URLs).
    • You can see when a user token was last used.
    • You can deactivate a token temporarily to debug a call or even quickly delete the user token if you suspect your app’s security has been compromised.

Example

Here’s an example of an API call using a ticket:

<qdbapi>
<udata>mydata</udata>
<ticket>auth_ticket</ticket>
<apptoken>app_token</apptoken>
<field fid=”8”>party at Lindisfarne</field>
<field fid="9">dress in style of the epoch</field>
<field fid="10">lindisfarne island</field>
</qdbapi>

Here’s the equivalent action replacing the ticket with a user token:

<qdbapi>
<udata>mydata</udata>
<usertoken>user_token</usertoken>
<apptoken>app_token</apptoken>
<field fid=”8”>party at Lindisfarne</field>
<field fid="9">dress in style of the epoch</field>
<field fid="10">lindisfarne island</field>
</qdbapi>

 

How to create a user token

To create a user token, click the user dropdown on the global bar, then choose My preferences.  Under My User Information, click the link for Manage my user tokens. Then click the New user token button.

In the Basics section, enter a Name and a Description for your token. In the Assign token to apps section, use the dropdown to select which apps you want to assign this token to. You can assign a token to as many as 20 apps.

Project Token

 

When you click Save, the new token appears in the list of user tokens. API calls containing this user token can now interact with an application.

 

MyUserTokens

 

What’s fixed in QuickBase?

Here’s what we fixed this month.

ID Issue
QBE003937

There was no easy way to remove placeholders from the Manage Users page in an application. If there are placeholder users in the Manage Users list, a Remove Placeholders button will now show on the page to remove them.

QBE005154

In certain cases, importing data into user fields resulted in placeholders that displayed the value ??? in the Manage Users page.

This issue has been resolved.

QBE010264 When adding a Text element to a form, the Help icon for the HTML (Limited) checkbox displayed a help topic with incorrect styling.

This issue has been resolved.

QBE010272 When printing an app home page in landscape mode, the printout still appeared in portrait mode. Reports and charts appeared compressed and were often not readable.

This issue has been resolved.

QBE010423 When signed into QuickBase with certain mobile devices running iOS, and using the full site, lists of reports and emails were condensed, making it difficult to read the contents of a column.

This issue has been resolved.

QBE010590 Exporting the realm directory in CSV or Excel format will now include the contents of the Is Deactivated column.
QBE010600 QuickBase API calls returned an HTTP status of 200 even if there was an API error.  This made it difficult for webhooks, scripts, and third-party integrations to determine whether the call was actually successful. There is a new header (X_QUICKBASE_RETURN_HTTP_ERROR) that, if used (and has a value of on, true, yes, y, or 1) will properly return a status of 400 for requests with errors.

This issue has been resolved.

QBE010608 If API_ChangeUserRole was used to change the app manager’s role to another role with Full Administration permissions, the call failed with the error:

“Error code 114 Manager cannot be removed from the administrator role.”

This issue has been resolved.

Do you have an idea for improving QuickBase?  Please share your suggestions by clicking the orange feedback tab on the My Apps page, or visiting the Customer Feedback for Intuit QuickBase forum (http://quickbase.uservoice.com). 

You may also like:

Posted in Release Notes | Tagged , , , , , ,