Update/Insert child entity record in siebel when a session is saved in WD

Question

Hi,
We have a requirement where we need to create/update a child entity's record in siebel when user clicks on save session link in WD window after the rule execution. We are using IO mapping. Account is the parent entity and let's say B is the child entity.We are storing row_id of the new created B record in a field of Account BC(before the WD call we are creating a new B record).
So, in the rule we need to update one field of B entity such that we can update the new created B record using EAI Siebel Adapter BS in the Policy Automation Save Session IO Post WF. We wrote like below.
reason(B's field) = RejectionReason (Account's attribute) if
ButtonOption = "Reject"
and
B's id = Account's field where B's row_id is stored for the new record
but we found that we had to use rule table for this.
We used the rule table like below(could not paste the table):
rule_loop
Reason
RejectionReason     ButtonOption = “Reject”
And
B’s row_id = B’s row_id in Account
Reason     otherwise
It is setting B's Reason field for the particular record of B, but for rest of the B's records it is setting Reason to null although we do not want to change the Reason for rest of the B records.
Could you please help us on this? Also how to navigate to the question screen directly if any attribute value is null? We added the screen flow but now it is directly showing the summary screen even if the attribute value is null.
Thanks in advance!
Regards,
Subhradeep

Answer 1

Hi Frank,
Yes, the parent entity is "Account" and the child entity is a new entity(B).One Account can have multiple B records(1:M relationship).Before calling WD one B record is created for the Account and we are storing the row id of that record in Account BC.
In WD screen we have dropdown where user can select "Reject" option for the product offered to him.
user selects "Reject": in the next screen he will select the Rejection Reason and when he saves the session the Reason field of the new B record will be updated.
We have created an IO to send data to OPA where Account is the primary BC.So if we can update the Reason of B in the rule(for the new B record) then we can directly use the IntegrationObject returned from OPA and use EAI Siebel Adapter BS to update that B record in Policy Automation Save Session IO Post WF.
So we need:
Update Reason for the new B record, do not update the Reason for rest of the B records.We had written in a rule table like below:
rule_loop
Reason
RejectionReason     ButtonOption = “Reject” and B’s row_id = B’s row_id in Account
Reason     otherwise
(B’s row_id in Account, RejectionReason are global attributes for Account, Reason is the B's attribute)
when we used the IntegrationObject in Siebel(after the save session) it is updating Reason of the correct B record(new one)...but for rest of the B records Reason becomes null(the otherwise condition). We do not need to update the Reason for the remaining B records.
Please could you suggest us how to stop updating the Reason of the remaing B records in the rule itself?
Thanks & Regards,
Subhradeep