BUG FIX: Solution to error message received when trying to generate PDF for BIAs in BCM Workspace

[Rana Baghdar]

When upgrading the GRC: Business Impact Analysis plugin to version 2.2.2 released on the 18th of November, one of the new features is the ability to generate BIA PDF. But, OOTB doesn't work. I tried it out in one of our company demo instances and in a PDI, both with all the recent updates, and it didn't work in any of them.  

Below, I have created step-by-step instructions on how to fix this with the use of cross-scope access privileges. There might be multiple ways to fix it, but this is how I did it, and it worked. 

The following error message is received when trying to generate the BIA PDF:

Step 1

• Navigate to System Applications > Application Cross-Scope Access > New
• A new record modal form with the name “Cross Scope Privilege” is now open.
• Fill out the form as described in step 2

Step 2

• Source Scope: Document Templates
• Target Scope: GRC: Business Impact Analysis            -
• Target Name: sn_doc_template
• Target Type: Table
• Application: Document Templates
• Operation: Read
• Status: Allowed

Save the record and go back to the list view.

Step 3

In the list view, locate the record created in step 2.
Do not click the info icon to preview, but in the column Source Scope, click on Document Templates.

You will now automatically be sent to the Store Application for Document Templates.

On top of the Document Templates  record, a red warning banner is present with the following message:

“Click here” is a link that sends you to the next step.

Step 4

After clicking on the link in the warning banner, you will be sent to a new page for Restricted Caller Access Privileges.  A filter is already set for the list that you are viewing.
Locate the record we created in Step 2 in this list view and open the record.

Make sure the record matches what you can see below:

• Source Scope: GRC: Business Impact Analysis
• Source type: Script Include [sys_script_include]
• Source: Script Include: GenerateBiaPdfUtilBase
• Status: Allowed
• Target Scope: Document Templates
• Target Type: Table: Document Template
• Operation: Read

Click the Update button to save the changes.

Step 5

Navigate to the Business Continuity Workspace, either open an existing BIA or create a new one.

Click the “Generate PDF” button, and a PDF will be generated that can be downloaded.

[NS16]

Hi @Rana Baghdar 

I am unble to generate BCP PDF,

As you mentioned I checked version of GRC: Business Impact Analysis plugin and its in 2.3.2 released.

Scenario- I have two BCP templates for template- A BCP pdf generated as expected but for template- B I am getting below error.

Could you please help me with this issue 🙂

Thanks,

Neha

[Rana Baghdar]

Hi Neha, 

Have you checked the steps mentioned above?

I suggest you take a look at the step by step instructions above and see if that can fix the issue. 

I'd reccomend that you update all plugins related to BCM before you go through the steps to see if the issue is solved. 

Please mark as helpful if this helps! 

R

[Sayalim]

Hi Neha,

Did you get any solution on the error. I am also getting it

[NS16]

Hi @Sayalim ,

I was getting this error becuase I changed the charater limit of Name field (of BCP record) from 40 to 100.

I reseted that to 40 now its working fine.

Hope this will help you 🙂

[Community Alums]

You can also check to see if the Document Template you are using has any reference to a sys_id that does not exist.  For example a sys_id of an attachment if you attached a logo file to the template.  Sometimes that needs to change or you need to re-add the attachment.  Or if you have it pointed to an image location make sure that exists.   And don't just trust the preview option as it may preview ok - but when the template is called from the GeneratePDF action / script includes is when it may die out.   

[Rana Baghdar]

Hi @Sayalim @NS16 

I don't know what the root cause to the issues you are facing is.  This post is related to version 2.2.2, and patch release 4.0.0 was released on the 2nd of Feb.

I suggest that you update your plugins and see if this helps, as this issue was fixed by ServiceNow after a while. 

- R