Invisible of dependent field custom input in service catalogue

Provisioning & Self Service
, ,
3

Hello @aungkyawthu,

To add to what @cbunge mentioned, in the event there is a field you do not want to show but add logic to.

  1. In the Catalog Item, for the config.resourcePoolId field, you could have logic that is based on the items in the form. For example:
    <%= if(input.cluster == "abc"){8}else{5} %>
    The above can be nice when your logic is simple based on other items in the Catalog Item, but making complex decisions or accessing data from the API might be less convenient.

  2. Attach a Workflow and use the Configuration phase to make more complex decisions. See the following post for more info:
    Edit Instance Configuration Before Deployment

  3. Finally, I have put in an Idea for having some of the APIs as data sources, instead of inputs. The idea is that you can use the data source and reference it, without needing to actually show the input. Feel free to vote on this, if it is related:
    Input Data Sources

Hope that helps!