VertiGIS Studio Web & Mobile App Designer Patch 5.34.2 Released

Christian Wohlmutter

24 février 2025 23:42 Modifié

We’ve just released VertiGIS Studio Web & Mobile 5.34.2, another important patch to improve the stability of app deployments. This update fixes an issue that affected on-premises deployments using a mix of public ArcGIS Online (AGOL) content and private ArcGIS Enterprise content.

The issue stemmed from a recent update to how we handle background processes in the Designer. While the change improved overall performance, it unintentionally caused deployment errors when working with both AGOL and ArcGIS Enterprise content in the same app. The root cause was the same as what we addressed in 5.34.1 for Dutch users experiencing loading issues, so we’ve now extended the fix to cover this scenario as well.

If you ran into deployment problems when using both public and private content sources, this update should fully resolve them! 🚀

P.S. For Mobile, this was a Designer-only update, so there are no Studio Go 5.34.1 or 5.34.2 versions—nor are they needed. Studio Go 5.34 remains the latest version for all platforms.

Associé à

• Studio Web
• Release
• Mobile

1

• 

  Paal Pedersen

  28 février 2025 07:49

  Incorrect Parameter Handling in Workflow Trigger

  Description:
  In the latest version, there appears to be an issue with the internal keywords dev, test, and prod being incorrectly mapped or exchanged within external workflows triggered by a calling workflow. Specifically, the parameters passed to the external workflows are not being handled as expected.

  Steps to Reproduce:

  1. Create a switch with the dev, test, and prod ports. Accept and input containing the env keyword.
     • Expected: The workflow should use the coresponding port to the input keyword.
  2. Trigger the workflow with the parameter dev.
     • Expected: The workflow should use the dev port configuration.
     • Actual: The workflow uses the dev port, cause no keyword is translated.
  3. Trigger the workflow with the parameter test.
     • Expected: The workflow should use the test port configuration.
     • Actual: The Switch activity ports now get translated to test, test, and prod. Choses the first port which is actually the dev port in desguise, because the dev is the default port.
  4. Trigger the workflow with the parameter prod.
     • Expected: The workflow should use the prod port configuration.
     • Actual: The Switch activity ports now get translated to prod, prod, and prod. Choses the first port which is actually the dev port in desguise, because the dev is the default port.

  Issue Summary:
  The parameter switch logic seems to be defaulting incorrectly, causing the wrong port configurations to be passed regardless of the input parameter (dev, test, or prod). This suggests a possible bug in the parameter handling or switch logic within the workflow.

  Expected Behavior:
  Each parameter (dev, test, prod) should correctly map to its respective port configuration without mixing or defaulting to incorrect values.

  Additional Context:
  This issue impacts the reliability of workflows, as the incorrect port configurations could lead to unintended behavior or failures in deployment or testing environments.

  Questions:

  1. Does the latest patch address this issue?
  2. If not, could this be prioritized for a fix?

  
   

  0
• 

  Alisa Lindley

  28 février 2025 18:37

  Paal Pedersen if I understand correctly, I believe the issue you're seeing here may be a result of new, user-requested functionality in Environment Values. Do you have Environment Values for “dev”, “test”, and “prod” configured in the VertiGIS Studio Web app you are deploying by any chance?

  Essentially, the old behaviour would only apply Environment Values once per component. This meant that if you had a string like “The quick brown fox jumped over the lazy dog” and you wanted to change the animals from “fox” and “dog” to “chicken” and “cat”, you would have had to include a single Environment Value that changed the entire sentence from “The quick brown fox jumped over the lazy dog” to “The quick brown chicken jumped over the lazy cat”. Once this was done, the sentence could not be modified again.

  Many users did not like this limitation and wanted more customizability, so we updated the Environment Values tool in 5.34 so that multiple changes could be applied to the same component. In other words “The quick brown fox jumped over the lazy dog” can now be changed to “The quick brown chicken jumped over the lazy cat” by including one Environment Value for “fox” to “chicken” and another Environment Value for “dog” to “cat”.

  Though this adds convenience and usability to the Environment Values tool, the consequence of this is that you have to be much more careful with your Environment Values, as there is likely to be a greater number of places where they are applied. A demonstration of this is shown in our February 2025 Road Ahead Webinar recording: https://support.vertigis.com/hc/en-us/articles/11461033818898-Road-Ahead-Webinar-Recordings

  0

Vous devez vous connecter pour laisser un commentaire.