Huge thanks to the members of this forum that patiently help me get stuff figured out.
We are looking at our next object(s) and I am trying to figure out the best way to handle / organize the them.
Our current object centers around a "client". Now a single client can have multiple invoices and each invoice has multiple "time cards". A time card a period of time that an individual worked, what their pay rate is, the amount paid and the check number that used to pay the individual, etc.
Modeling this nested relationship (Client -> Invoice -> Time Card) is throwing me off.
How would you organize this in VLF-ONE?
Would you create three separate objects each with their own filters or commands? I could potentially see each one having value on its own. I've read about switching objects but I don't see how to "pass data" to another object. For example, I have selected Client ABC. I want to see their Invoices so I need to pass Client ABC's identifiers to the Invoice object.
I was thinking about making an "Invoices" command that would show a list of Invoices. When an Invoice is selected, I need to trigger something else to show the Time Cards. This I thought would be a hidden "By Invoice" Time Card filter, but I still need to get the Invoice Id to the filter. I could create a shared state object that the Invoice command would set the identifier and the hidden filter would read.
Does that make sense? Is that the "LANSA" way of handling a situation like this?
Edit
Reviewing the "Children" example application. Based on that example, I would still create the Invoice and Time Card commands however I would model the relationship through the instance list. In my comment above, I was trying to show model the relationship through commands. I could create filters for Invoices like "By Client Name" or "By Client Number" and filters for Time Cards like "By Invoice Number" etc.