• Replies 17 replies
  • Subscribers 0 subscribers
  • Views 75 views
  • Users 0 members are here
Options
3sides - Social sharing widget
Related

Display iSheet Data on Home Page/Wiki

Sean Pillai
27343

I recall that there is a simple way to display iSheet records on a site's home page (or wiki) in a table or single-item format.  I'm referring to data from each individual row as opposed to charts and other aggregate data visualizations.  However, I haven't been able to find the instructions.  Any assistance would be appreciated.  I'm trying to display iSheet data in a more user-friendly manner by, for example, placing the contents of each column in a separate row, with each iSheet row corresponding to a separate table on the home page/wiki.

 

Simplified example:

(1)  This is my iSheet record:

 

Client Name Client Jurisdiction Client Code Client Mailing Address Client Relationship Manager(s)
Acme Co. Delaware 1234567 123 5th Ave., New York, New York Bob Smith; Amy Jones

 

(2)  I'd like to generate the following on the home page/wiki (including a link at the bottom that would allow the user to edit that particular record):

 

Client Name Acme Co.
Client Jurisdiction Delaware
Client Code 1234567
Client Mailing Address 123 5th Ave., New York, New York
Client Relationship Manager Bob Smith; Amy Jones

Edit Record [THIS LINK WOULD TRIGGER AN EDIT OF THE RECORD

 

]]>
Parents

  • Andrew Quinn Big NoNo?
    I wonder why this would be a big NoNo. HighQ saves api keys in an user accessable way as well. Just take the HighQ Drive Windows App (or any HighQ app) login and let it run. If you now make a memory dump of the app, you can quite easily find the api key there. So even non admin users can get a hold of the api key.

    This seems rather unavoidable, because any programm accessing the api needs that key somewhere in memory. So every programm running on a user's machine will expose the key to this user. Same with using the api in the frontend.

    Nevertheless I would advice against using the api in the front end. This is because the timeout for the refresh token is one year (!), so if the user does not log out properly this token could be used by an attacker.

Reply

  • Andrew Quinn Big NoNo?
    I wonder why this would be a big NoNo. HighQ saves api keys in an user accessable way as well. Just take the HighQ Drive Windows App (or any HighQ app) login and let it run. If you now make a memory dump of the app, you can quite easily find the api key there. So even non admin users can get a hold of the api key.

    This seems rather unavoidable, because any programm accessing the api needs that key somewhere in memory. So every programm running on a user's machine will expose the key to this user. Same with using the api in the frontend.

    Nevertheless I would advice against using the api in the front end. This is because the timeout for the refresh token is one year (!), so if the user does not log out properly this token could be used by an attacker.

Children
No Data