FLS - document classification issue

I have two similar kinds of documents in an FLS project. But the first page of the doc-type B is the same as the second page of the doc-type A. I can't make a proper classification. Whatever I've tried - if B-docs are classified correctly, then A-docs lose their first pages. Is there a way to classify them both correctly?

Was this article helpful?

0 out of 0 found this helpful

Comments

4 comments

  • Avatar
    Adrian Enders

    You need to find something unique on the page that determines if it is a first page or second page. How is FLS supposed to differentiate if the page is exactly the same? You are giving FC conflicting rules.

    The only thing you have going is the scenario where this is the second page. In this scenario is the first page always the same? You might be able to script this, but it would be tricky. Basically you are having FLS identify the pages, then write a script that separates them based on conditions of the "previous" page.

    I see why you are stuck. Other options are to separate these in scanning/import. Make two different document definitions, two different FLS projects and two different batch types. Even better, have 2 different projects. 

    0
  • Avatar
    t.t.

    I see I need to give more details. Of course, I've added unique elements for both pages. I've even tried to lower the quality of the second-page element - it hasn't helped, just like I've thought.

    When you say about the "previous" page, I suppose it means outside of FLS. In FLS, the Header element (which is part of the doc classification mechanics) can see only one page at a time. Does it mean it's impossible to resolve this issue inside FLS? If so, it makes things too tricky. I'm an FLS-only developer. I send AFL's - and other people do the rest of the job.

    Having two different projects is also too complicated. We're already about to have around 30 alternatives in the end. Adding a second project for only one of them is too much.

    I think I'll drop the first page. The client usually doesn't like it, but in this case, I can locate all fields from there on other pages - so we can reassure them.

    0
  • Avatar
    t.t.

    I've found second "second pages" in the middle of some docs. And docs don't have a footer (the last page is the same format as a few previous). If there's any way to work it around, it's too complicated for the project's current stage.

    Strictly speaking, that B-docs look like A-docs with the first page dropped. So, for now, we'll tell the client first pages were probably lost on the scanning - and they need to recheck it.

    0
  • Avatar
    Adrian Enders

    Yeh, this is harder to communicate just thru messages. You can have FLS identify the pages, and then put a classification script in Project Setup to perform the separation - like you said, outside of FLS.

    And to be clear, there is nothing unique on the page that would differentiate between it being page 1 of A-doc instead of page 2 of B-doc, correct? They are identical as far as being able to have something "unique' to distinguish between A-doc and B-doc. This is what I understand when you say "look alike". You have to have a header element that is unique between the two. Something you can use.

    Sounds like you are putting together a process that will work. I hope you can solve this, it's a good topic for discussion! 

    0

Please sign in to leave a comment.