Configuring workflows for simultaneous use in Mobile and Web

Alex St. John

13. Dezember 2023 22:16 Bearbeitet

Are there general recommendations for when wanting to use a workflow in both Web and Mobile? 

I'm running into various, small, but effective, differences in how some values are stored and in how dynamic form elements behave (e.g. adding form elements based on feature selections or setting values of form elements at runtime).

For example, in Mobile I have some form elements that are added for each feature that has been selected by the user (geometry picker and then confirmed by item picker)

While in Web, the form elements draw at the top of the form instead of the bottom:

And I must go through an additional accessor to get my feature attributes

Figured out the need for "data" (Web only, not in Mobile) through the DevTools console:

I have used the Get Application Info activity to make runtime decisions, such as how to access the feature context variable. Is this still expected and should be relied upon to decide which way to access values? For example, the IF below checks =($appInfo1.name === "GXW")

 

The redundancy and maintenance of this concerns me, having to find and fix all the places in workflows where there is a need to distinguish between Web (GXW) and Mobile (VSM).

0

• 

  Nico Burgerhart

  14. Dezember 2023 12:38

  We internally documented these differences, for a project with a set of workflows which should be able to run in VS Web and the Go app. And indeed use Get Application Info activities to make runtime decisions.

  2

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