Forge JSM portalRequestDetailPanel : Impossible to invoke functions

Forge Forge UI Kit and Custom UI
1

Hello!

i tried to use the forge portalRequestDetailPanel template from Forge create.

Sadly it is impossible to invoke a function from the JSM portal, i’m getting this error:

global-bridge.js:2 Uncaught (in promise) Error: Invocation of the function is forbidden
    at https://jsm-help-center-ui.prod-east.frontend.public.atl-paas.net/assets/js/252.chunk.49d5c2d6eb5216a636ae.js:2:75184
    at h (https://jsm-help-center-ui.prod-east.frontend.public.atl-paas.net/assets/js/servicedesk-vendor.chunk.808963186cd887af0c4f.js:2:1218160)
    at Generator.<anonymous> (https://jsm-help-center-ui.prod-east.frontend.public.atl-paas.net/assets/js/servicedesk-vendor.chunk.808963186cd887af0c4f.js:2:1219487)
    at Generator.next (https://jsm-help-center-ui.prod-east.frontend.public.atl-paas.net/assets/js/servicedesk-vendor.chunk.808963186cd887af0c4f.js:2:1218570)
    at n (https://jsm-help-center-ui.prod-east.frontend.public.atl-paas.net/assets/js/servicedesk-vendor.chunk.808963186cd887af0c4f.js:2:1789616)
    at s (https://jsm-help-center-ui.prod-east.frontend.public.atl-paas.net/assets/js/servicedesk-vendor.chunk.808963186cd887af0c4f.js:2:1789827)

Error: Invocation of the function is forbidden
    at fe.error (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:2:153277)
    at Object.<anonymous> (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:2:161050)
    at JSON.parse (<anonymous>)
    at Te.o (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:2:160909)
    at Te (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:2:161062)
    at s.on (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:2:165722)
    at je (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:2:165859)
    at https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:2:171845
    at e.try (https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:2:144329)
    at https://forge.cdn.prod.atlassian-dev.net/global-bridge.js:2:171642

I tried to add some additional scopes but that doesn’t work either.

Is there some configuration to make those request working ?

1 Like
2

Hey, @KevinCalmant

Did you manage to find a solution to this? Currently I am having the same issue.

Best regards

3

Hey @VentsiBorislavov, @KevinCalmant

Did you manage to find any solution for this?

I am having the same issue.

Regards,

4

Hi people,

I have followed the following instructions (https://developer.atlassian.com/platform/forge/build-a-custom-ui-app-in-jira-service-management/) and the result is KO

I have also tried to make a clone of Bitbucket changing the id and performing the deploy, with the same KO result:

image

I haven’t found any documentation explaining
what happened, but I’m inclined to think that the UI KIT upgrade has caused this regression.

I’ll keep looking for a work-around, when I find one I’ll leave it written here.

Regards

5

Hello teammates,

After spending hours testing Forge/Bridge APIs and components (storage, webtriggers, invoke, invokeRemote…) and following several tutorials from the UI KIT, UI KIT 2, and Custom UI documentation (https://developer.atlassian.com/platform/forge/build-a-custom-ui-app-in-jira-service-management/), as well as cloning example app repositories from Atlassian, I have made no progress. Not even the example apps created with “forge create” seem to work properly.

None of the Forge/Bridge APIs or components are behaving as expected (they don’t function) for any Jira Service Management module.

So, It seems necessary to conduct a more in-depth review of Forge’s integration with Jira Service Management, as there appears to be a lack of compatibility or sufficient documentation for these specific modules.

If someone found a solution, please share it.

Thanks and regards

6

Hey @DonAlcantara , just wanted to share here our findings.

On this case, at first we were not able to reproduce the behavior on our lab instances. But at some point we noticied we were able to hit the same error when changing the user’s Product access to Jira Service Management to “Customer ”, only.

To fix it:

  • Went to admin.atlassian.com >> “Directory ” >> user profile
  • Clicked on the user we are logging into your test instance with to replicate the issue.
  • Added/edited “Jira Service Management” by selecting the Product role “User (agent)”

That did the trick.

1 Like
7

Hi Gustavo,
I have built an Atlassian Forge app using the module “jiraServiceManagement:portalRequestCreatePropertyPanel.” Inside the UIkit-2 frontend, I’m invoking a resolver but get the same error (denied: “Invocation of the function is forbidden”).

It is not suitable to give all portal users JSM agent licenses!
Do you have any hints on how to overcome this limitation?

Kind regards,
Frank

8

I have found out how to solve this issue by updating my app’s manifest.yml:

  unlicensedAccess: [unlicensed, customer]

So, you do not need to be an agent having the related license to properly access that Forge panel on a JSM portal.

Kind regards,
Frank

1 Like
9

You rock it, Gustavo!

¡Thx a lots!