This content has been marked as final. Show 7 replies
Flexible headers are the correct feature in OSM to use. They are designed to display the order or task specific information that is relevant in the user's worklist or query results. You can also filter and order worklist and query results based on flex header values.
I'm not sure therefore what you mean when you say the flex header shows order specific and not task specific data. Can you clarify please?
Let me clarify our requirement with an example. Suppose that we have two separate executable order components for the same process running in parallel, for which we have sent a request and we are waiting for response. In the task client , two separate tasks , will be displayed one for each order component. Can we display in the intial task client screen, information that we will help us discriminate between the two order components, because now we have two seperate lines that include the same info , for example :
Task = ProvisionOrderSIResponseTask | Process = ProvisionOrderProcess | OrderId= Same for both components | Ref.# =Same for both components
We would like to display as an extra column , info that will help us discriminate between the two order components.
For example can we display the product class for the items belonging to an order component , or line-ids, or any other info that is relevant to the order component?
Thank you in advance
You can make any field in the order a flex header field. So if you have a field that you find useful for your scenario then you can make it a flex header and see it in the Worklist or Query results if you want.
Now as to what field to use - well that depends on what you are trying to do. You mentioned product class - this is not going to be unique across two order components necessarily. You could have the same order item in multiple order components and therefore the same product class. Also, you could of course have multiple order items in each order component and therefore it's not a unique value (in cases like this where there are multiple instances of a flex header field within the scope of the task, OSM will just choose one of them to display in the worklist results). The only thing that is always unique across order components if the componentKey field within the ControlData structure. You may have other fields that are by your solution convention unique but of course those would be specific to your cartridge design.
Thank you Brian for your help so far. I updated my response below:
It seems that even if we use the component key element as flexible header element , it is not displayed correctly in the task web client.
The task web client in the componentKey column shows the same value for all tasks , irrespectevely of the executable order component to which it belongs.
Furthermore if we use any element under the path ControlData/Functions/My_Function_Name/orderItem/orderItemRef/ (flexible_element_chosen) , as a flexible header element no value for this element is displayed in the task web client
Edited by: ntheodoropoulos on 14 Ιουν 2012 7:59 πμ