(forum messed up other post - re-posting)
Hi
This week I need to make a component to view/edit my customer info... the grand daddy Customer Info screen (CustInfo). Using UX. A complex, comprehensive, Customer at-a-glance status screen showing all sorts of stuff about a specific customer.
Once I have the CustInfo screen done, I would like to make that a stand-alone component that can be called from other places in Alpha (ie. a list of open invoices, each of which is for a customer, should allow me to get to the CustInfo screen, albeit not in Edit mode for each user, or a to-do list for today. Basically, any place a piece of data references a customer MIGHT be a place where I'd want to jump to the CustInfo screen.)
One simple starting place would be a UX List of customers (that does searching, filtering, etc) and then be able to select a customer to then view using CustInfo.
1) Is this the correct strategy to approach this, with a seperate, compartmentalized routine for CustInfo? Sure, it could be in 1 UX comp with the list and edit together, but in the example above, I want to come to the CustInfo screen from many places in the system, not just from a List.
2) Is there a written example of this somewhere in the docs, on how I go about passing parms, etc. Is this what a filter is for? Do I stuff the selected CustID into a session variable? etc etc
3) is this so ridiculously simple, that someone could just describe how to do it?
thx
jim
web only, no desktop needed
bld 5864.5310 (23 may)
MS SQL
Hi
This week I need to make a component to view/edit my customer info... the grand daddy Customer Info screen (CustInfo). Using UX. A complex, comprehensive, Customer at-a-glance status screen showing all sorts of stuff about a specific customer.
Once I have the CustInfo screen done, I would like to make that a stand-alone component that can be called from other places in Alpha (ie. a list of open invoices, each of which is for a customer, should allow me to get to the CustInfo screen, albeit not in Edit mode for each user, or a to-do list for today. Basically, any place a piece of data references a customer MIGHT be a place where I'd want to jump to the CustInfo screen.)
One simple starting place would be a UX List of customers (that does searching, filtering, etc) and then be able to select a customer to then view using CustInfo.
1) Is this the correct strategy to approach this, with a seperate, compartmentalized routine for CustInfo? Sure, it could be in 1 UX comp with the list and edit together, but in the example above, I want to come to the CustInfo screen from many places in the system, not just from a List.
2) Is there a written example of this somewhere in the docs, on how I go about passing parms, etc. Is this what a filter is for? Do I stuff the selected CustID into a session variable? etc etc
3) is this so ridiculously simple, that someone could just describe how to do it?
thx
jim
web only, no desktop needed
bld 5864.5310 (23 may)
MS SQL
Comment