Rewrite the FME-Server plugin

[maan002]

Update from @Hallbergs: The old FME-plugin will be removed and replaced by a completely new plugin. Here's some information about the new one:

FME-Server Plugin

The main purpose for this plugin is to run FME-workspaces that are published to an FME server.
The plugin allows for both Data-download (targeting /fmeproxy/fmedatadownload/repository/workspace) as well as running with the REST-api (v3) (targeting /fmeproxy/fmerest/v3/transformations/submit/repository/workspace). Currently, the plugin is only available for users with the nodeJS backend, simply because the plugin relies on the fact that mapServiceBase/fmeProxy exists (and this is currently only implemented in the nodeJS backend).

Developer info

The FmeServer-plugin is built as a functional component, and might seem a bit strange at first sight if you've only dealt with class components. However, remember that React is leaning toward more and more functional components, and in my opinion all new plugins should be built as functional components.
Functional components are really fun to build! I suggest you give it a go if you are planning on building/rewriting a plugin.

TODO:s

Further development

Ideas for the future:

• Add possibility to extract all features from the draw-layer, so that these could be sent to FME-server

Feel free to add more!

Setup

There are a few steps that an admin must complete before the plugin will function:

• Add a user to FME-server that can access and run workspaces in some repository.
• Enter details about the FME-server instance and the user created above in the .env-file (located in /new-backend).
• Enable the plugin in the admin-UI.
• Add a couple of products (workspaces) in the admin-ui.
• Make sure that everything works!

The Admin UI

In the Admin UI, the administrators can add and remove products. Unfortunately, the Admin UI does not allow for editing of already added products. (Which means that the admin must remove the old product, then add it again with the new value if they want to change anything). There are a few settings on the products that might need some explanation:

• Name: The name of the product
• Group: Which group should the product belong to?
• Repository: In which repository is the workspace located?
• Workspace: Which workspace should the product target?
• geoAttribute: Which published parameter should we save the geometry to? (If no geometry is needed, set "none").
• maxArea: To avoid killing the FME-server instance, we allow for a max area for the drawn geometries (-1 can be used for no restrictions).
• infoUrl: If set, the plugin will display an IconButton pointing to the url supplied.
• availableForGroups: Set to comma-separated string of AD-groups if some products should only be visible for some users.

The Admin UI fetches information such as available repositories and workspaces (for the user specified in the .env-file) automatically to simplify the work for the administrators.

Usage

The plugin is (should) be really simple to use. it is based on the idea of a stepper, where the user can move on only when they have completed the step they are on. The stepper should lead to a minimum of errors in the end, since we can force the user to make good choices.

---

Original issue, by @maan002:
Enhancements identified to the FME Server Datadownload plugin:

• Both "YTA" and "REKTANGEL" draws a rectangle.
• Workspace parameters must be specified in map_1.json (see readme.txt for instructions). Add support in backend to fetch them from FME Server.
• The following workspace parameters are supported: TEXT, LOOKUP_LISTBOX, LOOKUP_CHOICE. Add support for more types.
• The mail address is specified in map_1.json. Add support in backend to retrieve the current user's mail address.
• When you order ("BESTÄLL" button) the request goes directly to FME Server. Add support in backend to communicate with FME Server to eliminate CORS problem.
• The FME token must be updated manually in map_1.json. Add support in backend to retrieve a new FME token.
• Add Admin support for this plugin.
• Use hfetch instead of fetch.

[Hallbergs]

The progress can be tracked in this branch

[Hallbergs]

The plugin is now merged to develop, and will be available in release 3.8!

[jacobwod]

Fantastic @Hallbergs! 🚀 💯

[maan002]

Hi Henrik,

I found a bug in the multiple select. The way the plugin sends the selected values are wrong.

The way the selected values should be sent are:

INFORMATION: LAS,HOJDKURVA

[Hallbergs]

@maan002 fix coming in a couple of minutes!

[Hallbergs]

Closing this issue now when 3.8.0-rc1 is out. If more bugs are found, they can be described in the discussion thread connected to the 3.8.0 release candidate! :)