I realize there is a question like this, but the solution was not really answered. That user was able to still use the same table.
Business Requirement: I have two tables, one is the "Finance Request Template" (sn_sm_finance_request_template) and the other one is the "Finance Request" (sn_sm_finance_request). The sn_sm_finance_request_template is the table that houses values for the setup of the Finance Request. The other table holds the actual data of the request. On these requests, there is a drop down called "Closure Codes". The business wants this field mandatory for certain Finance Templates. And to clarify, we create Finance Requests...but we have different versions of it that has different variables ("Medicaid Refund", "Cash Payment", etc)
We currently created a UI policy that linked to the Finance Request table (sn_sm_finance_request) in which we hard coded the template names that we want to assign it to. The new requirement is not to hard code it. They wanted a database field somewhere that says "Require Closure Codes". So I added a new field on this template table as a way to determine whether this type of template would have this required
The problem is when I try and modify the UI policy, I am linking to just a single table and the new field is on a different table.
Question: How can I specify fields from two separate tables in a UI policy? Or what is another way around it?
Is there relation between the two tables?
If relation is there, you can get the other table name field from related fields of that table.
Ex:
OOB Incident form contains problem field, if you want to get problem field record, you will select the show related records of problem and you can select the problem fields.
Is there relation between the two tables?
If relation is there, you can get the other table name field from related fields of that table.
Ex:
OOB Incident form contains problem field, if you want to get problem field record, you will select the show related records of problem and you can select the problem fields.
