'Associated Release' field on change form

[Ankita9]

Hi All,

I wanted to hide 'Associated Release' field if it is empty or does not contains 'Release number'(RLSE0010001). 

'Associated Release' field is referring to TASK table which is why it is showing Incidents, problems, requests etc. So I created a UI Policy, Please refer below screenshot.

Now what is happening is 'Associated Release' is been displayed only when a Release is associated with it(expected outcome).

But, if I add another record(problem, change, release, task) it removes the previously associated record. I don't want this to happen, the backend association between the change table's associated release field and its associated records should stay as it is. Just the field Associated Release' field should be hidden if it is empty or does not contains 'Release number'

Example - 1st step: RLSE0016725 has been associated with CHG00653009
2nd step: the CHG will show the RLS number (as expected)
3rd step: PRB00013759 has been associated with CHG00653009
4th step: the CHG will NOT show the RLS number because RLSE0016725 is NOT associated with CHG00653009 any longer (NOT expected)

[Stephen Sturde]

Hi Ankita,

Where are you making the addition of the other records (problem, change, release task)? I'm assuming in a different field, correct?

[Ankita9]

Hi Stephen,

To add other records(problem, change, task), I'm going to the particular record(eg. problem ticket) where we have a related tab know as 'Change Request'. Click on Edit and select the change from the slush bucket.

[Vishnu Prasad K]

Hi Ankita,

When you are associating a PRB number to Change request, the parent field on Change request is updated with the PRB number and that is the reason the field is not visible, as you wrote in the UI policy. It's because every record (Problem, Incident, Release etc.) are mapped to one field in Change request form. That in not a many to one relationship, but one to one relationship. I think you need to use other fields for associating other task records to change record, we already have few  and you may need to create the ones we don't have

[shloke04]

Hi,

Associated release looks like a custom field which is created in your instance. 

First thing to mention is creating a UI Policy will not clear out the field automatically unless you write a script in your UI Policy to do so.

Looking at your screenshots, looks like Associated release is a Reference type of field and it can hold only 1 value at a time and not multiple, so when there is already a value linked to it and you add another value it will override the previous value and will show up the new record value added which is how the platform works for a reference type field.

Hope this helps. Please mark the answer as correct/helpful based on impact.

Regards,
Shloke