Skip to main content
Archived

Workspace Reader improvements

Related products:FME Form
  • September 11, 2018
  • 2 replies
  • 28 views
lifalin2016
Influencer
Forum|alt.badge.img+40

Hi.

I'm trying to utilize the Workspace Reader to handle my almost 200+ repository of workspaces.

I stumbled over a few issues with the Workspace Reader, that I want to propose as improvements.

  • "PublishedParameters" include both published and private parameters + parameters to embedded custom transformers. But it doesn't include any way of distinguishing between them. Please add an extra attribute for this.
  • "WriterParameters" does not include e.g. the MSSQL_SPATIAL parameters for executing statements before and after translation. Are they available elsewhere ? If not, please add.

This is what I've found sofar.

Cheers

-- Cheers, Lars I.
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

nic_ran
Contributor
Forum|alt.badge.img+20
  • nic_ranContributor
  • Contributor
  • April 24, 2020

I'd like to add to this request:

- published parameters currently make the parameter name, type and default value available, it would be helpful to also have the "prompt" as that's what the user sees.

nic_ran
Contributor
Forum|alt.badge.img+20
  • nic_ranContributor
  • Contributor
  • April 24, 2020

I've discovered that this information is buried in the published_parameter_type attribute, although this is not clear in the documentation. A documentation update would be great.

It would also be great if this could be returned in separate attributes by the FME Workspace Reader as it's a pain to parse in the workspace.

From my interpretation of the data returned by the reader, the published_parameter_type attribute format looks like:

- GUI [IGNORE] [OPTIONAL] <paramType> <name> [choices] <prompt>

Where:

- [IGNORE] is optional and, if exists, signifies a private param

- [OPTIONAL] is optional and, if exists, signifies an optional param

- [choices] is optional and exists only if the paramType is a "choice" type parameter

I built a custom transformer to help parse out this information until Safe (hopefully) supports this more directly with the Workspace reader:

https://hub.safe.com/publishers/front-point-consulting/transformers/parse-published_parameter_type

Community Stats

32,724
Posts
124,149
Replies
41,216
Members
Terms & ConditionsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.