Zum Hauptinhalt gehen

Why can't I run my server workflows ?

Kommentare

5 Kommentare

  • Stefan Schweigert

    Hi Guillaume,

     

    Could you give me a bit more information on the type of workflow and which activities you are running, like are you running a client workflow that calls a server workflow then outputs the file back? Not all server workflow activities can be run in the sandbox directly. That error seems to indicate that perhaps the path to the file might be incorrect when run in GXM, possibly GXM is looking for the file on the device.

     

    Thanks, Stefan

    0
  • Guillaume Ruelle

    For now it's just for testing, so I just create a value in the server workflow (Create Value activity), then set the workflow output with that value, then try to display that value in the console, client-side. So it's basically two "two-activities-workflows", nothing big. I tried in other environment and it's working.

    And I am running it from GVH, not GXM, that's why I don't understand the error message.

    0
  • Guillaume Ruelle

    Hi @Stefan Schweigert? ,

     

    Even if I run from the sandbox, I got the same error message. Attached, you can find my workflows and the error message.

    Could it be linked with the custom activities we developed ? I really don't know why it's looking for 'VertiGIS.Mobile.Composition', since we don't run it from GXM...

    0
  • Stefan Schweigert

    Hi Guillaume,

     

    The VertiGIS.Mobile.Composition assembly is part of GXM. If you are trying to create a Custom Activity for GXM in a Server Workflow, that is not supported because the server has no access to GXM so it would need to be installed in GXM and run on the client.

     

    In the GW5_RunServerWorkflow, you'll want to log the output using this syntax: =$runWorkflow1.result["TestValue"]

     

    Thanks, Stefan

    0
  • Guillaume Ruelle

    Hi,

    Thanks for your answer.

     

    We removed the custom assembly from where Geocortex Workflow is installed and it is now working back again. I guess we did something wrong when installing the CustomActivityPack...

     

    And, the syntax "$runWorkflow1.result.TestValue" is also correct, but thanks anyway for the suggestion.

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.