Rule for looping over a collection of Ojects in Agentry

[former_member455472]

Hi All,

The solution that we have currently has a Object - WorkOrder which has a collection - Notfication. This Notification has a property - Notes.

The requirement is to display the Notes of the Notification which is associated with the WorkOrder. The mapping field here would be the Notification Number which is a part of both WorkOrder and Notification objects. We need to have a rule that picks the Notification for which the Number matches with that of the WokOrder object. How do we achieve this

Thanks,

Pooja

[Former Member]

Pooja,

If your workorder and notification has relationship 1:1 than you can achieve this very easily.

Like

  IF

     EQSTR

     Notification    

     Application.Blank

  Application.Blank

  Notification property-> 1st object->Notes property

If relationship is not 1:1 than you have to write a rule like

current property-> Notification property where Notification equal to NotificationNum->Notes property

Most of the case we use 1:1 relationship. Let me know if you have any other issue.

Thanks

Ajitesh

[former_member455472]

Hi Ajitesh,

Thanks for the quick reply. We have tried the Notification property-> 1st object->Notes property method, but apparently the required Notification Object is not always the 1st object, it is not sorted to be the 1st object always. Hence we need to match the NotifNum and get the correct Notification object. How exactly can we have a update rule in place for achieving this?

Thanks,

Pooja

[Former Member]

does that means you have 1:N relationship. Means one workorder may have more than 1 notification?

and which screen you want to display? is it in Workorder screen or somewhere else?

[former_member455472]

Yes Ajitesh, its 1:N reln. A single workOrder can have multiple Notifications. And the Notes has to be displayed in the WorkOrder screen

[Former Member]

Please follow below screen shot

[former_member455472]

Thanks a ton Ajitesh

[Former Member]

Roopa,

If your issue has been resolved please close the thread.