Using Forms to display additional fields in the Portal

[#1]

This article started from a question about whether we could show fields on the Portal just for info. The original poster got the impression that having multiple forms on one request wasn’t really doable, but this article was created to show that it’s totally possible without needing any Marketplace apps. Let’s break it down.

For this example, I set up a simple request type where the only linked field is the Summary, which matches the "Describe the issue" field in the form.

I also created two automations. The first one automatically adds the description updates form to new IT support requests.

The second automation resubmits the form to grab any changes made to the description field. This uses a new action that lets us resubmit the form without needing the REST API, which is pretty cool.

Once everything is set up, let’s give it a try.

Here’s a sneak peek of the ticket in the Portal before it’s submitted.

This is how the ticket looks before we add an update to the description field. As you can see, the automation has successfully added the Description updates form, but the description field is still empty on both the work item view and the form.

After updating the description, here’s how it looks from both the agent view and the Portal view.

As you can see, the automation that reopens and submits the Description updated form makes it super easy to show extra fields on the portal when we need to. Plus, this isn’t the only way you can add more forms into a work item or request.

[Darryl Lee]

Whoa @Mikael Sandberg

That's 1) a pretty cool hack, 2) kind of a long way to go just to display field data (I think the original request was to show it in read-only form?). :-}

I mean, yes it works. But as a Customer isn't it a little odd to be looking at "Attached Forms" for field updates? Enh, I looking at your screenshot they probably won't care, as the data is what's important.

I guess if they ask you can say "This way was cheaper than buying an app". Maybe you'll get a promotion! (Ha, I know that's not how it works.)

(Found your original post. Very clever.)

[Mikael Sandberg]

@Darryl Lee Yes, I agree that it is a bit of a long way of displaying the data using a Form. But because you are using the submit action the form becomes a read-only form on the portal and only the agents can re-open the form, There is an option to lock the form, but the you would need a project admin to reopen it, and you would not be able to use automation to update the fields on the form by re-submitting it.