app.json Reference: Published parameter handling

This page documents settings that influence the visibility and values of Published Parameters.

Property Type Required Default Notes

hiddenParameters

Array<String>

No

[]

Published Parameters hidden in the UI. If all are hidden, parameter dialog is not shown.

customPublishedParameters

Object

No

-

Static value overrides by parameter name.

useNumberFieldInsteadSliders

Boolean

No

false

Render numeric parameters as number fields instead of sliders.

runAsynchronously

Boolean

No

false

Force async processing even without email input.

emailIsMandatory

Boolean

No

false

Makes opt_requesteremail mandatory.

provideMapappsEmail

Boolean

No

false

Sends current user email as opt_requesteremail.

provideMapappsUser

Boolean

No

false

Sends current user name as mapapps_etl_user.

acceptTermsOfUse

Boolean

No

false

Requires explicit acceptance before process start.

searchSelectionHiddenAttributes

Array<String>

No

[]

Attributes hidden in search-selection input dialog.

Practical dependencies

  • If emailIsMandatory=true, ensure the workspace contains opt_requesteremail.

  • If provideMapappsEmail=true, ensure your security setup exposes user email.

  • If you use customPublishedParameters, verify parameter names exactly match FME parameter names.

Related pages