• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (5)

1 Ashish@IBM commented Permalink

Thank you. Rainer Mueller-Maechler <div>&nbsp;</div> I would like to know that what else if your Dossier in Motion that means workflow based. And only a single UI interface to Create a Dossier and route the Dossier (Approval - Rejection Cycle)

2 Rainer_Mueller-Maechler commented Permalink

Yeah, static Dossiers is just a start. As a Dossier is technically represented by the top-level folder, you can do everything with a Dossier as you would do with a folder. This includes workflow capability. <br /> The simple version just has one dialog to create a new dossier where the user can provide some metadata. By closing the dialog the dossier with its subfolder structure is created. In a more sophisticated version closing the dialog could trigger an approval workflow (by FileNet Content Engine Event mechanism). So the Dossier would just be created, if the worfkow approves the new dossier. This could be an arbitrary approval workflow even with custom step processors which shows the flexibility and extensibility of IBM Content Navigator. - Developing custom Step Processors is also covered by the redbook.

3 choracy commented Permalink

Ok, what happens when the client has 10,000 (or much more) customers? Would you create 10,000 top level (or at any level) folders? Don't think so. <div>&nbsp;</div> Also how can you provide 'elegant' browsing for different document classess in each folder? e.g. when browsing 'Mail' folder, you need to view columns, From, Subject (ok name is ok) Date etc but Claims should display ClaimNo, PolicyNo, ,,, <div>&nbsp;</div> And of course as these kind of implementations are usually better when separating Dossiers by year, how would you implement? <br /> Year1 <br /> -Customer 1 <br /> -Customer 2 <br /> -Customer 3 <br /> .... <br /> Year2 ..... <div>&nbsp;</div> OR <br /> Customer1 <br /> -Year1 <br /> -Year2 <br /> -Year3 <br /> .... <br /> Customer2 <br /> ....

4 Rainer_Mueller-Maechler commented Permalink

ad 1)A draft version of the new Redbook can be found now in the reference section and there you will find some considerations about Dossier Management in real world e.g. in chapter 4.7. This also covers your question about ten thousands of dossers and how they should be stored. <br /> ad 2) Yeah, showing different document classes with different properties in one folder is a challenge. You would try to put similar documents and document types into one folder that have most of the properties in common. If there are too many different properties even if there are similar documents you could make sub folders. <br /> ad 3) structure of dossiers depends on the customers main order principle. For example we had customers, that structured their credit dossiers of their customers with the account number at first level and with something like the credit request number on second level. A radio station stuctured their radio shows in a Year-Month-Day-Programme manner. That really depends on the use case and customer. If we use the Year-Month-Day structure, we maybe come close to case management structure. But in some use cases this structure is maybe not adequate and with the dossier management approach you are flexible and can design your own structure. <br /> A last consideration is to use a so-called virtual dossier management solution. This allows you to create several views on your dossier documents, even if they are stored unfiled. Chapter 6 introduces the concept of virtual folder browsing and should give you a first idea how a virtual dossier management could look like.

5 choracy commented Permalink

Thank you for taking the time to reply. Will get the new Redbook and do some studying.

Add a Comment Add a Comment