Question

FSM-Input XML Business Rule in Web Client

  • 29 September 2021
  • 2 replies
  • 193 views

Userlevel 2
Badge +3

Hi,

I have a requirement to select a request contact from the place contact look up, on saving of request. I am trying to achieve this by using following input xml in BR.

This is working fine in Smart Client, but not on Web client.

Issues  on Webclient -

  • Contact_sequence is not  required field.(though I am passing required = y in xml).
  • Not able to see Magnifier Glass to open Place Contact Lookup.

 

Can anybody help me on this, what am I missing here? or is there any other way to achieve same functionality on Web client?

Requirement is - user should not able to save request without selecting request_contact on Web client. 

​​​​​​​

<update_request_contact>
  <request_contact>
    <insert is_initialized="false" />
    <request_id>@user_input[id=request_id, table_name=request_contact, column_name=request_id, control_type=TextBox, read_only=Y,required=Y, default_value=@request_id]</request_id>
    <contact_sequence>
     @user_input[id=contact_sequence,
     table_name=request_contact,
     column_name=contact_sequence,
     control_type=TextBox,
     required=Y, 
     navigation_def=
    <navigation_item>
                 <function_name>PLACECONTACTLOOKUP</function_name>
       <type>popup</type>
      <trigger>button</trigger>
       <template>ButtonControlTemplate</template>
       <search_criteria>
           <criteria_def>
            <item_name>request_contact.place_id</item_name>
            <function_item_name>place_contact.place_id</function_item_name>
            <value>@place_id</value>
            <locked>N</locked>
         </criteria_def>
      </search_criteria>
      <return_values>
        <return_def>
            <item_name>request_contact.contact_sequence</item_name>
            <function_item_name>contact.contact_sequence</function_item_name>
        </return_def>
       </return_values>
</navigation_item>]
</contact_sequence>
  </request_contact>
</update_request_contact>

 

Thanks


2 replies

Userlevel 7
Badge +22

Hi @arti.sagar ,

Which FSM update are you on? There was a common issue in input XML BRs not being popped up/ getting errors while saving on webclient but this has been resolved from U11 onwards.

Is your requirement simply a validation? If that’s the case, isn’t it possible to add a validation business rule according to your requirement before saving the request? One option would be, you might need to check the count of request_contacts before saving the request. If that’s less than one you can throw the error. The count of request_contacts can be created as a view and then you can join that view in custom metadata for request so that you can have that view on the input parameters itself.

Another way would be, you can write custom webclient script to validate the request contacts before saving the request or to popup (with openPopup() function) the request contact by checking the number of request_contact entries.

Userlevel 2
Badge +3

Hi @Saranga Amaraweera ,

Thanks for your help, I have found the solution though.

Reply