XStep conditional formatting. Can it be determined at run time ?

Question

Does anyone know of a way to put conditional formatting into an XStep generated table output. For example, this is what we are trying to do:
- At some point after an order is generated and released, materials are issued to it.
- We have created a function module that reports back the list of all materials issued.
- The FM also checks to see if the material was planned in a reservation.
- If a material issued was not a planned material we want to list it in RED.
In the XStep repository, I can simulate a table output using parameter PPPI_FRAGMENT_HTML, and can change font color by giving it a value like
<div style="color: red">TEST123</div>
And I get TEST123 displayed in RED.
I also get TEST123 displayed in red on the generated PI sheet, if I put the put the HTML string above into the XStep as a fixed value.
But if I program the FM to return this string, then I get the entire string output in the table field and the font color is not changed to RED.
Edited by: Mike Rupp on Oct 14, 2011 6:31 PM
Edited by: Mike Rupp on Oct 14, 2011 6:36 PM

Answer 1

I got a response at the XStep Cafe and thought it might help others if I share it here.
Arne Manthey:
I assume that you are also using PPPI_FRAGMENT_HTML for the parameter to which the FM returns your string. If you valuate this parameter manually it is internally handled as a long text. However the function module will most likely return just a string value and these are probably not recognized as a long text. I do not have any idea how to valuate a long text with a FM when the PI Sheet has already been generated. The only thing I did successfully was to generate HTML text during generation (although not with XSteps). But in your case this would not help, yes?
The general problem with long text elements is that they are really meant for initial valuation only and not for changing back and forth.
Another way of doing conditional formatting would be to use some Stylesheet magic which evaluates a status parameter you would set by a function module. This would most likely also include some Javascript to make the change happen. Please follow that path only if it is really necessary because Stylesheet stuff is not easy to handle.
mrupp:
Thanks Arne.
We decided to just add an additional table column with an alert message when needed to flag Unplanned Materials and/or Expired Shelf Life. I have played around with Stylesheets & Javascript a bit and agree that it is not worth it in this case.