You are viewing limited content. For full access, please sign in.

Question

Question

Feature Request: Web Client iframe to Only Show Metadata

asked on June 17, 2020

We are working on a project right now where we are doing AP approvals in Forms. The form does a lookup that can bring back over 600+ rows in a table and this ends up breaking Forms. We do not have the same issue when a document in the web client brings back 600+ field values for a multi-value field. The problem is that we want to use an iframe to embed in the form, but there is not a way to only show the metadata without the image. It would be great if there was an option for that.

0 0

Replies

replied on June 18, 2020

Hi Blake,

Can you share more about what information you're displaying in the 600+ rows?

0 0
replied on June 18, 2020

GL account data.

0 0
replied on June 18, 2020

Ah, ok. So I assume the goal is for users to be able to quickly select one or two values from a dropdown of 600+ GL codes, not to display all 600+ GL codes at once?

0 0
replied on June 18, 2020

Nope, they need to be able to see all 600+ GL codes as rows in the table for verification.

0 0
replied on June 19, 2020

How does the table help with verification? Is it something that users are using as a reference to see all the GL codes? Or is this for assigning GL codes on an invoice with 600+ line items?

0 0
replied on June 19, 2020

Users use the table to see all GL codes assigned to the invoice being approved. Some invoices can have 600+ GL codes.

1 0
replied on July 21, 2020

Thanks again for the additional context. Coming back around to make sure I address your original question: 

It sounds like this problem is better solved by improving Forms lookup performance or having paginated results. I know that functionality is waiting for the new layout designer. It's unlikely that the Web Client will add an additional embedded view for just the metadata pane. 

0 0
replied on July 22, 2020

@████████I would agree with that. If the Forms lookup performance or having paginated results could be implemented that would solve the initial issues we are facing. Preferably I would like to see both smiley.

0 0
replied on July 22, 2020

To piggyback on this slightly, Tessa, I think this and some other items could also be addressed by having better "integration" between Forms and Web Access. It's possible to show the doc in Forms if you pass the entry ID and embed as an iframe, but it's a bit clunky. And in Web Access I can embed a custom tab for a form, but I have to pass the Entry ID into a hidden field and once I submit, the document itself has no awareness of it so just sits there showing whatever message is set for the submitted form.

It would be great if Forms could have a specific item for an LF doc, and likewise Web Access could have a frame explicitly for Forms, with some simple options for behavior.

2 0
You are not allowed to follow up in this post.

Sign in to reply to this post.