Forge: Display Condition -> entityPropertyExists is not working on Confluence

Forge
,
1

I’m using forge 4.2.0 and entityPropertyExists from displayconditions was working okay with a content action (Confluence) until May 17, after that this stopped working.
This is manifest.yml

  confluence:contentAction:
    - key: contentaction-hello-world-content-action
      resource: main
      resolver:
        function: resolver
      viewportSize: medium
      title: contentAction
      displayConditions:
        and:
          entityPropertyExists:
            entity: content
            propertyKey: CONTENT_ACTION_PROPERTY

and this is property:

image
image938×900 74.7 KB

But content action does not appear .
My project is here
Why I have this problem?
Thanks

2 Likes
2

Hi Forge team this is still not resolved. I have logged a bug here for tracking Jira Service Management

Please take a look a it as this is basic forge functionality that is broken now.

1 Like
3

Hi @sromero and @jhuertas,

Thanks for flagging this. I can confirm that I could reproduce the behaviour and that we are looking at this.

Caterina

2 Likes
4

Hi,

A quick update to let you know that the problem only occurs to properties containing at least an uppercase character in their keys.

This could be a workaround while we fix the underlying problem.

Caterina

1 Like
5

Hi Team,

We’ve identified the issue and a fix is being rolled out at the moment. I’ll update this when I have confirmation the fix is in production.

James.

6

Hi all,

The fix has been deployed to all production sites 12 hours ago.

Our tests confirm that the problem is now resolved, but let us know if you still see a problem.

Thank you for your patience with this issue,
Caterina