Representing Master Detail or 1:M relationships in a FootPrints ticket

Version 1
    Share:|

    As you know FootPrints is deployed in many non-traditional applications like purchase requests, expense claims , account requests etc. In many such applications, there come a time when they need to represent master detail relationships (aka 1:M) . Eg. submit an expense claim for approval with 20 variable items .

     

    We had a similar request from a customer some time back and we custom made a grid feature to meet it.  Attached are the details.