Add Form type about solution.js

[MikeTschudi]

• create Solution
  • Get Survey2Service relationship
  • Save attached zip to Solution item
• deploy Solution
  • Restore relationship
  • Restore zip

[shoe913]

@MikeTschudi @chris-fox

Testing this, everything looks fine. Just one quick question about the following scenario.

• Solution A contains a survey
• Solution B contains a different survey which uses the same feature service as Solution A
• Solution C contains both surveys which reference the same feature service

If Solution A is deployed, and then Solution B is deployed, a single feature service should be created and share by both solutions, correct?

Currently, Solution A and Solution B both get their own version of the feature service. This is not the behavior I expected. I was anticipating one version of the feature service which is shared by the two solutions.

Solution C works as I would expect and a single feature service is shared by both surveys.

[chris-fox]

@shoe913, did you test this with Ryan's app or the Deploy Solutions test app? Ryan's app is the only one that has the reuse logic enabled so you need to use that to see the behavior your describe.

[shoe913]

Cool, that is what I wanted verification on. I'll test in Ryan's app to verify that behavior.

Thanks!

[shoe913]

Ryan's App did the trick, this looks good to me.

[shoe913]

@MikeTschudi @chris-fox

Further testing revealed some issues with forms. It looks like they are being added as part of the template or as a dependency. Both tests use the default sample form. They copy app doesn't seem to read the form and deploying also fails.

When making both of the templates below, I shared the form to the group used to create the solution template.

Template added Manually:
https://localdeployment.maps.arcgis.com/home/item.html?id=4a52e9e465084329a769bd78c1d30ec6

Template read as Dependency:
https://arcgis4localgov2.maps.arcgis.com/home/item.html?id=7faeba4455f74bb99b380082e8dc739c

Looks a little fishy to me that the two items are not consistent. I'm guessing this is at play when actually deploying the templates.

[shoe913]

On further inspection, everything looks good.