How do I make a record producer public in the Helsinki portal?

John VanBruggen
Giga Guru

Hi there,

I am trying to make a record producer available publicly in the Helsinki Portal using the new portal configuration tool.

I promise this isn't the typical question that has been asked here 100 times, though it is similar.  

I have been successful in getting the record producer to be available to the public guest account by utilizing the following Knowledge.

ServiceNow KB: Making a record producer and catalog item public on a CMS page (KB0551300)

If I open the record producer directly (without logging in) I am able to open and submit and create records as guest without issue so I know that part is good to go.

The issue is when I try to access the record producer through the new Helsinki portal widgets.

I have been using the ICON LINK widget to link to the record producer.   It has the following configuration...

find_real_file.png

This is linking to the sc_request page to open the Create Facilities Request record producer.   I have set both sc_request and the SC Catalog Item widget on that page to be publicly accessible (see below).

find_real_file.png

find_real_file.png

I have been able to successfully configure the portal to the point where I can access the request as guest, but when I try to submit the request it fails.   No errors... it just sits and spins.

As I stated earlier, I can pull up the record producer directly without logging in and submit it and it creates that record.   The issue is just when I try to do the same thing through the portal.

Any thoughts on this?

Check out my Consultant's Survival Guide
https://youtube.com/watch?v=zYi8KhP9SUk
1 ACCEPTED SOLUTION

nathanfirth
Tera Guru

John,



That is because record producers are not available to unauthenticated users. Behind the scenes they are calling in to "angular.do" which requires authenticated user so with the current implementation... it is not going to work when public. Now that being said, we are working on our own implementation of this widget which will use Oauth and REST to handle the submission which should work for public users.


View solution in original post

5 REPLIES 5

John VanBruggen
Giga Guru

We had two solutions, each used in differing solutions.


1. Since the record producer was externally exposed, and the user did not need to log into the portal, the record producer did not need to be displayed in the portal.   So, the client was able to link directly to the record producer from their public website and when the item was submitted, the user was routed back to the public site.



2. For public requests that need to be presented publicly through the portal, we used an iFrame.   This works but you lose the flexibility of having everything look correct regardless of the platform it is being used on.   It works fine on a desktop / laptop / iPad but not so great on a small screen like a phone.


Check out my Consultant's Survival Guide
https://youtube.com/watch?v=zYi8KhP9SUk