Document Templates of PDF Type in HR Agent Workspace

[Giuliana Martin]

Hi,

Are agents able to generate document templates of PDF type in the Agent Workspace for HR. The document template and document template category are filled out. If the agent is in the HR Agent Workspace, they do not have the Preview document UI action. This UI action is only available in the legacy view.

If the document template is of type HTML, then the agent does have the Preview document UI Action.

Are document templates of type PDF able to be used in the HR Agent Workspace?

[AijaRe]

Hey, Marcel!
If the case is assigned to me the button still does not appear.
It's true that the "Workspace Form Button" checkbox is involved just like you and @Sandeep Rajput indicated. If I select the checkbox, the button appears, but obviously nothing happens onClick since there is no script.

But my question is why HTML Document Template (still a Document Template) behaves differently. If the document template is of type HTML, the Preview Document button is available even if the "Workspace Form Button" checkbox is not selected, and on click it opens a modal with options to edit, generate and initialize document tasks.
If I select the  "Workspace Form Button" checkbox and then select HTML template on the case, two buttons appear - one fully functional and the other just a button (second being the one generated from UI Action).
So my question now is, where does the first functional button come from and how can I replicate it for PDF documents (to fill and generate the document on click)? Can you help?

[Marcel Hopp]

Hey @AijaRe,
I checked the buttons on one of our instances and saw that we have more than one "Preview document" UI Actions too.

I have three ideas left:

1. My last idea is that you double-check the HR Service Configuration as I know the UI Actions are checking against this configuration. I had issues with the Template linking to the HR Service in the past too.
2. Check if the checkbox "Format for Configurable Workspace" is checked on the UI Action. This can cause the Action not be shown/executed correctly. 
3. Check the "Restricted Caller Access" privileges 

[Nick Fajardo]

I was searching on this myself, digging through code, and I had a view things to add.

For Agent Workspace, the "Preview document" button(s) is actually a Next Experience "Declarative Action" (/sys_declarative_action_assignment_list.do?sysparm_query=model%3D360935e9534723003eddddeeff7b127d%5Eform_position%3Daction_bar%5ElabelSTARTSWITHPreview%20document&sysparm_view=form_action ), not a UI Action.

There are new Next Experience modals that are popped up, rather than the traditional GlideModal popups.

From our investigations, if you want to have PDF document templates, you'll need to create a new UI action or something to open the popup in a new UI page, rather than directly in Agent Workspace