Issues with Variable Usage After Orbeon Version Update

[orbeon questions]

Hi,

In our production environment, we have Orbeon version 2021.1.9.202306062351 installed, and everything works smoothly.

We updated Orbeon to version 2023.1.3.202406131619 PE and are now encountering a few issues:

1. We cannot use variables in a repeating element.
2. When attempting to edit the control formula (calculated value, initial value, etc.) in the Form Editor, where a variable is used, we receive the error "Incorrect XPath expression," even though in Form Runner, this value is properly set in the control.
Here’s the description and usage of the variables:

xml
Copy code
<xh:head>
    <xh:title>....</xh:title>
    <xf:model ......>
        <!-- Variables -->
        <xf:var name="QuestionnaireSpecificationUuid">.......</xf:var>
        <xf:var name="CheckRule" value="xxf:get-request-parameter('CheckRule')"/>
        ......
        <!-- Custom event actions -->
        <xf:action .......
        ...
        <xf:instance id="fr-form-instance" .... </xf:instance>
        <xf:bind id="fr-form-binds" ref="instance('fr-form-instance')">
            <xf:bind id="G-BI-02-bind" name="G-BI-02" ref="G-BI-02"
                     relevant="xxf:is-blank($CheckRule)">
            <xf:bind id="G-BI-02-grid-bind" ref="G-BI-02-grid" name="G-BI-02-grid">
            <xf:bind id="K0000039-bind" ref="K0000039" name="K0000039"
                     xxf:default="$QuestionnaireSpecificationUuid"/>

We use variables to capture values from the URL and utilize them in calculations. Rewriting every variable usage would be challenging. How can we define variables differently so that they can be used in repeating elements without causing errors in the Form Editor UI?

[Alessandro Vernet]

Hi Brigita,

We are aware of this issue and will work to fix it soon. If everything goes as planned, we should be able to include the fix in version 2023.1.6. We will post an update here once the issue is resolved.

https://github.com/orbeon/orbeon-forms/issues/6145

-Alex

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orbeon+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/orbeon/0663a241-9a01-4c89-a93c-0e102aa92eb0n%40googlegroups.com.

[orbeon questions]

Hi Alessandro,

Thank you for your response and for working on this issue. Do you happen to know the approximate date when the new version is planned to be released?

Best regards,
Brigita

To view this discussion visit https://groups.google.com/d/msgid/orbeon/CANrzKkmnfAu%2BAYLsNvYq%3DAUQp4MwkZtVGpy6-O8BuTaduULcLw%40mail.gmail.com.

[ebruchez]

Issue #6145 is now fixed. The fix will be included with Orbeon Forms 2023.1.6 and 2024.1.

Regards,

-Erik

[Alessandro Vernet]

Brigita, please let us know if you would like a test build that includes this fix.

-Alex

[orbeon questions]

This fix is crucial for our project, and we would appreciate receiving a test build with this update. It will allow us to assess whether the new 2023.1.6 version effectively resolves the issues we’ve encountered.

Brigita

To view this discussion visit https://groups.google.com/d/msgid/orbeon/720a2963-8134-4369-b924-ac85cc856b5bn%40googlegroups.com.

[Alessandro Vernet]

Brigita, here's a test build. Please let us know if it works for you.

https://orbeon-builds.s3.us-east-1.amazonaws.com/orbeon/orbeon-forms-pe/8261/8261.1/build/distrib/orbeon-2024.1-SNAPSHOT.202410241535-PE.zip

-Alex

[orbeon questions]

Thank you for your response. We have forwarded the test build to our developers and will be testing it shortly. Could you please inform us of the approximate release date for version 2023.1.6? Is there a specific month planned for its release?  

Brigita

--

You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orbeon+un...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/orbeon/277af9fb-a05c-4157-a8b5-9ae2319abf69n%40googlegroups.com.

[Alessandro Vernet]

Hi Brigita,

We plan to release version 2023.1.6 before the end of the month. However, several issues still need to be addressed beforehand, which may delay the release until December, depending on progress. Would this timeline align with your plans?

-Alex

[orbeon questions]

Hi,

The release of version 2023.1.6 is of great importance to our work and has a significant impact on our projects.

Could you please share if there is a more specific release date planned for this version? Thank you for your time and support.

Best regards,

Brigita  

--

You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orbeon+un...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/orbeon/CANrzKkkDSVr95Prk-5PMkp-VRA58_JLge0_0sSy-wGnhbLH18w%40mail.gmail.com.

[ebruchez]

Brigita,

We have one more issue we need to address for the 2023.1.6 release. There is a chance we will be able to release it next week.

-Erik

[orbeon questions]

Dear Orbeon Team,

We have recently updated Orbeon to the new version 2023.1.6, but we're still encountering the same error related to variable usage:

2025-01-08T12:24:49,323 INFO  lifecycle - event: {"request": "10", "session": "65939EB67A09B9341296C8F24085EB8F", "source": "xforms", "message": "ajax with update events", "uuid": "afa23156a13ec0175d2d495f5b5e70b0c61c4df2"}
2025-01-08T12:24:49,323 INFO  lifecycle - event: {"request": "10", "session": "65939EB67A09B9341296C8F24085EB8F", "source": "xforms", "message": "before document lock", "uuid": "afa23156a13ec0175d2d495f5b5e70b0c61c4df2"}
2025-01-08T12:24:49,324 INFO  lifecycle - event: {"request": "10", "session": "65939EB67A09B9341296C8F24085EB8F", "source": "xforms", "message": "got document lock", "path": "/xforms-server", "method": "POST", "uuid": "afa23156a13ec0175d2d495f5b5e70b0c61c4df2", "wait": "0"}
2025-01-08T12:24:49,670 DEBUG xbl - committing global binding index {name and attribute selectors: "22", attribute only selectors: "0", name only selectors: "66", distinct bindings: "66"}
2025-01-08T12:24:49,842 WARN  XFormsServer - xf:dispatch: cannot find target, ignoring action {target id: "fb-custom-control-settings"}

A detailed description of the issue was included in our initial email to you:

Do you know from which version this issue started appearing? Should we consider downgrading to an earlier version like 2023.1 to avoid this problem, or would it be better to upgrade to the latest 2024.1 version? Could you please advise us on the best course of action?

Thank you for your assistance.

Best regards,
Brigita

To view this discussion visit https://groups.google.com/d/msgid/orbeon/cfc73183-32ad-4840-89b9-5d6d2fe879b8n%40googlegroups.com.

[Erik Bruchez]

Brigita,

This appears to work in this demo form, running on Orbeon Forms 2023.1.6:

https://demo.orbeon.com/demo/fr/orbeon/builder/edit/9d143519e15f6e263db68872a5c4a971727ace77

In the model, I have:

        <xf:model id="fr-form-model" xxf:expose-xpath-types="true" xxf:analysis.calculate="true">
           
            <xf:var name="v1" value="42"/>
            <xf:var name="v2" value="43"/>

And I am setting an initial value as `$v1` on the single form control:

Form Builder lets me enter this variable. If I use a non-extant variable, I get the validation error:

Does a simple case like this work for you in your environment?

If not, can you share, privately if you wish, a non-working example?

-Erik

To view this discussion visit https://groups.google.com/d/msgid/orbeon/CA%2BPB9fz7fzsQFBWhWoufvCyD8Jziqrc1GK3gF0f9dX3Cjt88Tg%40mail.gmail.com.

[orbeon questions]

Hello,

We are currently trying to upgrade Orbeon Forms to version 2024.1-SNAPSHOT.202410241535 PE the earlier issue related to a variable in the Form Editor, where a variable was used, has been resolved and no longer persists. 

However, we have now encountered a new issue when constructing the HTTP service URL: http://server/path/item_guid. In the attached form1.xml, we hardcoded the value of a variable named specificationUuid. However, when Orbeon attempts to call the HTTP service, the variable value is not being passed into the URL.

On the other hand, if we set the variable value into a control (as shown in form2.xml) and then use the control's value to form the HTTP service URL, everything works as expected. The HTTP API service is fixed and cannot be modified. We need to use the variable value directly in the HTTP service URL construction. How can we achieve this?

 

Thank you in advance for your assistance. Looking forward to your reply!

You received this message because you are subscribed to a topic in the Google Groups "Orbeon Forms" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/orbeon/4Gk_Uxt9Ckw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to orbeon+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/orbeon/CAAc0PEVVj8%2Bkr%2BrdSBZnkU5KcK3oJvDcvbm2zh-RXAZnWwffNQ%40mail.gmail.com.

[Alessandro Vernet]

Hi Brigita,

This appears to be related to issue #6740. We plan to address it in the 2024.1.1 release. I encourage you to follow the linked issue below; we will ensure it is updated as we make progress. Please let me know if I have misunderstood any aspect of the issue you described.

https://github.com/orbeon/orbeon-forms/issues/6740

-Alex

To view this discussion visit https://groups.google.com/d/msgid/orbeon/CA%2BPB9fxhsAD6dv1ZGM%2BpKVYkRYtnVBTtnDMm-Fg802rNz4_ruw%40mail.gmail.com.