Show/Hide fields based on workflow logic

[Josh_West]

It would be very helpful if we could use workflow logic to show or hide certain fields. For example, we have 2 types of expenses, one type we only require a GL account for integration and the other type we require a GL account in addition to selecting a project from our accounting system (NetSuite). We would love to be able to hide the “project” field if Type 1 is selected but show if Type 2 is selected.

[Andrew_Russo]

@Josh_West

ould use workflow logic to show or hide certain fields. For example, we have 2 types of expenses, one type we only require a GL account for integration and the other type we require a GL account in addition to selecting a project from our accounting syst

same for us! we could really use this

[charlotte (Charlotte H.)]

Hi all! @Josh_West @Leah_Fitz @Andrew_Russo - thanks for sharing.

Yes, Ramp can support this!

Using conditional coding in submission policies, you can configure logic so that when Type 1 is selected Ramp will hide the Project field, and when Type 2 is selected Ramp will show the Project field (so employees only see and fill out Project when it is relevant). You can still keep the GL Account required for both types, and add the Project requirement only for Type 2.

Let me know if you have any feedback or questions.

[Leah_Fitz]

Thanks @charlotte ! Does this apply to Bill Pay as well? We want the field to show up only for card transactions and reimbursements based on certain conditions, but we want the field hidden in bill pay. It seems that if we have a custom field and enable it conditionally for our card transactions, it still shows up in bill pay no matter what, which we don’t want happening.