Save Parameters for use in other workbenches

You can create a template workspace with all those user parameters, but otherwise empty, then use that as a starting point for any new workspace you're going to develop.

You could look into using something like a CSV or an Excel file to store your parameters. Then if you want to use the parameters you can fetch them using a Reader and store them in an attribute.

Thanks both for the responses - i guess what i am after is a database. I could potentially have over 100 workspaces, therefore if the values in the parameter needed to change, i only wanted to change it once and it would then show across all workspaces using that parameter...going to have to think about this one.

Thanks again

@mattmatsafe​ that is perfect, absolutely what I was after, just the smallest request, could the icon stay green and not change back to pink in desktop to save confusion and differentiate the parameter types

Great!

For the most part, the icon should remain green, however, I do see that if a deployment parameter is used as a Rule Configuration value in an Attribute Validator, or in other cases where the control is an inline drop-down list, it does not. I have created an internal ticket for that to be addressed in a future version (ID FMEFORM-29466).

@mattmatsafe​ where are these deployment parameters stored? and is there a way to export them to share them with other authorities? I checked the docs but cant see anything???

@ingalla​ they are stored in FME Flow in the Deployment Parameter Store.

You can export and import them into different FME Flow instances by creating an FME Flow Project using the web UI.

For database and web connection deployment parameters, you'd need to include the connections as well, since the deployment parameter value just points to the name of the connection to use. But for text deployment parameters, this isn't necessary.