Hello everyone,

I have just started using Joget v3 and am facing an issue.

I created a form with only a Text Field component in it. In the Text Field's properties I have specified "Qwerty" as its default value. And I have set "delayedActivityName"  as the workflow variable in its properties. "delayedActivityName" is the variable i have created in the Workflow designer for this process.

When i ran the process, i expected to see a form with a text field having a default value "Qwerty" in it. But the text field did not have a default value set in it. It was empty.

And when i monitored the process i saw that the workflow variable "delayedActivityName" was also empty. And it remained empty even after i manually inserted a string in the Text Field.

Kindly help me resolve this issue and let me know where i am going wrong.

Thanks and regards,

Anisha

  • No labels

4 Comments

  1. Hi,

    Can you attach your app here together with steps to reproduce the problem?

    Thanks.

    1. Hi,

      Please find the app attached. In order to reproduce the issue, run the app and and click on  'Run Test Process'. The form with a single text field would be displayed. The workflow variable  "delayedActivityName" has been set in this text field's property. And so I assume that this variable would be assigned the value contained in the text field. But when you monitor the app the "delayedActivityName" workflow variable remains empty, while the process is running and even when you complete it.

      The issue of default value "Qwerty" not being set in the text field is resolved. The only thing different I did this time was that I deployed the process in the workflow designer, whereas earlier I was simply saving the xpdl file and then using the "Update via saved xpdl" feature to update the process.

      Kindly help me resolve the issue of the workflow variable not getting updated. Thanks for your time.

      Regards,

      Anisha

      APP_testApp-1-20140129193443.zip

      1. Hi,

        Any insight on this would be a real help.

        Thanks & regards,

        Anisha

        1. Hi there,

          We have managed to replicate your said issue. We will update you again when possible on the resolution. As of now, it should not be a blocker for activity routing based on workflow variable value.

          Thanks.