JoelHickok
Qrew Assistant Captain
Joined 6 years ago
User Profile
User Widgets
Contributions
Exchange a SAML assertion for a Quickbase token
Hello, I am looking to use a SAML assertion for authentication of a custom web app that uses the QB JSON API. In the linked documentation, it is described that you can use an API endpoint to do this, thereby authenticating your app using the currently logged in user with a SAML assertion exchange. But the documentation is super vague and provides little for one to go off if you are not a SAML expert. https://developer.quickbase.com/operation/exchangeSsoToken The line from this documentation I linked to that I am focusing on, is this: You must be able to create a SAML assertion in your code to use this endpoint. Does anybody have documentation or advice on how to put the SAML assertion together? I want to link to my app from Quickbase using a Formula URL. Then I want my app to authenticate the current user so they can perform some tasks in my custom app under the same identity they were using in the QB app. I would love to see a full example, code and all, to help with this. (Minus any secure pieces you need to obscure.)20Views0likes1CommentRe: FastField Integration Is Inappropriate
Hi Ben, Thanks for the message. The main thing that I think both of us are pointing out is that FastField is a paid add-on, yet shows up by default in several places in the UI. We shouldn't see that unless we have opted in to that product. My org does now have at least one user trying out FastField, but even before that, I was seeing it promoted as a first-class citizen of the Quickbase platform, taking up space in the UI menus, etc. See Kristas screenshots for a couple examples. Joel29Views0likes0CommentsUp-vote Full-width Formula URL Buttons for Reports
In reports, Formula URL buttons are truncated. You can use a Rich Text button and see the full button by default. I use Rich Text buttons now for reports where it is critical to see the whole button. Please up-vote my feedback on this: https://feedback.quickbase.com/app/#/case/474496?cpid=b2f09471-062b-455b-afda-96efb605ab38§ion=requests20Views0likes0CommentsFastField Integration Is Inappropriate
Am I the only one who feels it is not appropriate for Quickbase to so ardently push a paid add-on product towards it's consumer base, to the point of giving it first-class representation in the main navigation menu? Ever since Quickbase acquired FastField, references to FastField have become more and more abundant. What's the deal Quickbase? It's a 3rd Party add-on! Please stop integrating it into the baseline User Interface, even if you acquired FastField. If you want to make it an integral part of Quickbase, please do so. If you want to offer it on Business Plans, or Enterprise Plans, please do so. Don't start integrating FastField directly into the User Interface if it's NOT part a core features. Is this the new precedent? How many other companies are doing this kind of paid add-on integration directly into your every day UI? Examples... is this normal?103Views1like7CommentsRe: Pipeline Jinja url decode
Well, there is always this. But who wants to do this when it would be easier to just use a built-in filter? {{ a.body_json[0].changesUrl | replace("%3a", ":") | replace("%2f", "/") | replace("%3f", "?") | replace("%3d", "=") | replace("%5b", "[") | replace("%2c", ",") | replace("%5d", "]") | replace("%26", "&") }}112Views0likes0CommentsPipeline Jinja url decode
In a Pipeline, you can use the Jinja urlencode filter to encode a value that needs to be safely encoded for use somewhere else. However, how can you use the URL Decode function? I am used to Python, JavaScript, and other languages where you can easily use a URL Decode function. In fact, it seems in the full subset of Jinja filters or function, there actually IS a urldecode but that Quickbase hasn't implemented it in their build of Jinja for Pipelines. Any ideas? Desired: {{a.json.url | urldecode}}138Views0likes1CommentRe: Jinja for User List field
I think the original post was just trying to take one user from a User List and put that user ID into antother user tpye field. This is easy, unless there are more than one users in the user list. In that case, you have to somehow decide which one to select and add to the single user field, and I can't help with that. If all you want to do is update a List - User field with another user, than just add the user id into that value in the Pipeline, and it will update the single user. My problem was that I was trying to iterate over a loop of users in a List User field, and then access the email property for each user to make a list of the email addresses for the List - User field. I ended up solving this by using a Formula - Text field to just list the user emails for me, and then I access that field in the Pipeline using Jinja.290Views0likes0Comments