IBM Business Automation Community Come for answers. Stay for best practices. All we’re missing is you. Join / Log in Ask a question
Our HR team would like to search for an id in Filenet and found all documents related to one specific hiring process. I am trying to create a compound document to include all documents related to a hiring process to address that request. So far, I have created an Document Class called employee and set that class as an Compound Document. I have created an document using the employee class and follow the instructions below to add a Child document:
"To add a child document to a compound document:
I just guess that in that children adding step, you need to copy an object reference of a "Document" and paste it to the input.
Hi Gerold, Thank you for the answer! It is clear now. One question, is it possible to create a compound document and associate the children using the navigator or only using the admin console?
to create a compound document using the navigator you have to implement your own custom plugin.
There is a quite old entry about this in the Ideas Portal:https://ideas.ibm.com/ideas/CSNAV-I-40
@JIE ZHANG: Are there any plans for this on the RoadMap?
I don't know any plan for this feature...
Thank you for the assistance, guys!
You can use compound documents, linked or another option OVP object value property. A compound will connect two objects of any doc class sub types however if you use an OVP you can define constraints so that only a certain class or classes can be associated with that property and delete behavior - direction. If you have worked with IER records that is a good example of OVP usage. Historically ICN had limited to no OVP support but in latest release notes that is a feature now available. As mentioned in this thread you could use a plugin so the user can associate objects or use workflow for automatic based on metadata or other identifying information to create the compound(s).
Another use of OVP's example you have ten documents for one borrower traditionally we define the metadata on each document so that repeats 10x. Let's say customer changes their last name so we then update the ten documents with that information. Using an OVP "Borrower" that object exists 1x but is associated to ten documents. We change the OVP object address 1x we are done no need to update the ten documents. If we want to remove the borrower we delete the Borrower instance / object which in turn will delete those 10 documents. Downside of OVPs is non ECM developers are traditionally looking for a rowset/reader type function in their custom code to execute searches. If you explain do X search and when you get the results via the object property you will get a document collection that is likely far into the ECM weeds for them. Not because it is too complicated but it's too nuanced for non ECM developers to care.