LEP change markers

[ajordin]

I have a manual for which I am generating a List of Effective Pages.
So far, so routine.
However, I have now been given a requirement to generate in the LEP a change marker for each page that has changed.

By 'changed' they mean the page contains a <revst> element or is between a <revst> and a corresponding <revend> element.
(<revst> and <revend> are empty elements.)

The problem I have is that I can't call a test from the pagedesc to see if the page meets the criteria.
I have considered trying to set and clear a variable from the <revst> <revend> elements but there are cases where these occur on the same page which means that the variable gets turned off before the FOSI produces the LEP entry for that page.

Does anyone have any ideas as to how I might get this to work?

I don't think its possible from the FOSI alone and I will probably need to do some external processing, but I'm willing to bow to the groups collected wisdom if someone can prove me wrong. Any pointers or suggestions would be gratefully received.

Thanks,

Adrian Jordin
Business Solutions Manager
Piper Group plc

Email: ajordin@piper-group.com
Tel. + 44(0) 1454 284900
Fax + 44 (0) 1454 284950

www.piper-group.com<file: c:=" documents%20and%20settings=" ajordin=" application%20data=" microsoft=" signatures=" www.piper-group.com=">


Information contained in this e-mail is intended for the use of the
addressee only, and is confidential and may be the subject of legal
professional privilege. Any dissemination, distribution, copying or use
of this communication without permission of the addressee is strictly
prohibited. The views expressed in this communication may not
necessarily be the views held by Piper Group plc.

[AndyEsslinger]

Adrian,

There may be a way to do it in the fosi.

Here is documentation (from Arbortext) for the undocumented "fosicite" attribute of outspec:


<outspec fosicite="TO_FI_ALL_SAVES">

Hope this helps,
-Andy

     \  /      Andy Esslinger  F-22 Tech Order Data
_____-/\-_____ (817) 777 3047  LM Aero     Box 748
    \_\/_/                     Fort Worth, TX 76101


----------

[ebenton]

That's pretty cool, Andy. I like that. It might be useful to me in the
future. The only thing that I don't like is the fact that it is
undocumented, which means that in the future it may not work, or may be
dropped.
Software companies always say that, but in reality, once something is in
the code, even if its undocumented, it almost never gets dropped unless
it causes some sort of other problem sometime.

[ebenton]

After reading the top of your email, it looks like they *are*
documenting it, so scratch my pervious comments...duh...

[AndyEsslinger]

Ed,

I should have said that is not documented in the help that I have
installed (Epic 5.1F). It may be in later versions.

-Andy

\ / Andy Esslinger F-22 Tech Order Data
_____-/\-_____ (817) 777 3047 LM Aero Box 748
\_\/_/ Fort Worth, TX 76101

[LynnHales]

Well, it's not in the help for 5.3 M020 either. Neither ''fosicite" nor TO_FI_ALL_SAVES can be found doing a search of the on line help. 😞

Lynn

---- "Esslinger wrote:
> Ed,
>
> I should have said that is not documented in the help that I have
> installed (Epic 5.1F). It may be in later versions.
>
> -Andy
>
> \ / Andy Esslinger F-22 Tech Order Data
> _____-/\-_____ (817) 777 3047 LM Aero Box 748
> \_\/_/ Fort Worth, TX 76101
>
>

[ebenton]

All the more reason to save this email...

[LynnHales]

I'll drink to that one, Who's turn is to buy there Ed, yours or mine? I think it is mine. 🙂

What one could do is put a comment in the outspec.dtd in the distributed DOCTYPEs folder with the attribute value. Good until the next time Epic is updated. 😄

Lynn

---- "Benton wrote:
> All the more reason to save this email...
>