Content Management and Capture

 View Only
Expand all | Collapse all

Single point of change (How document can Inherit a property value from the parent Folder on Create/Update))

  • 1.  Single point of change (How document can Inherit a property value from the parent Folder on Create/Update))

    Posted Tue November 19, 2024 05:15 AM

    Hi All,
    Is there any way to create a single point of change for a group of documents to share a templet of probertites value and securities?
    As example create a templet of probertites value and defined securities, to use it in the document's updates and make the document point to this templet and change between this templet easily.

    Also we have a business logic where all documents need to inherit a property, e.g., "CIF," from the parent folder. Additionally, if the value of this property is updated on the parent folder, it must be propagated to all child documents.

    what is the best way to do that?



    ------------------------------
    Ahmed ElHussein
    ------------------------------


  • 2.  RE: Single point of change (How document can Inherit a property value from the parent Folder on Create/Update))

    Posted Tue November 19, 2024 05:18 AM

    FileNet



    ------------------------------
    Ahmed ElHussein
    ------------------------------



  • 3.  RE: Single point of change (How document can Inherit a property value from the parent Folder on Create/Update))

    Posted Wed November 20, 2024 03:44 AM

    Hi,

    >Is there any way to create a single point of change for a group of documents to share a templet of probertites value and securities?

    This is exactly what a document class is, a template for document attributes and security. 

    >Also we have a business logic where all documents need to inherit a property, e.g., "CIF," from the parent folder. Additionally, if the value of this property is updated on the parent folder, it must be >propagated to all child documents.

    This is not an uncommon requirement because logically a folder attribute very often is a shortcut for a property that applies to all the documents in the folder. There is nothing out of the box but you can achieve this with a combination of event actions (in very short: server side extensions that are triggered by events , e.g. a property update on a folder). We have done this successfully in the past.

    Hope this helps,

    /Gerold



    ------------------------------
    Gerold Krommer
    Managing Director
    The Document Content Profesionals, G.m.bH
    Wien
    +436602408515
    ------------------------------



  • 4.  RE: Single point of change (How document can Inherit a property value from the parent Folder on Create/Update))

    Posted Wed November 20, 2024 03:44 PM

    Hello Gerold,

    Thank you too much for your response,

    >This is exactly what a document class is, a template for document attributes and security. 
    we want to inherit the property value also not only the property also to be able to change this value at one place (Parent Templet) and to be propagated on all instances.

    > This with a combination of event actions.
    is there another way to do this inheritance without configured an event? 

    Thank you again for your effort.



    ------------------------------
    Ahmed ElHussein
    ------------------------------



  • 5.  RE: Single point of change (How document can Inherit a property value from the parent Folder on Create/Update))

    Posted Thu November 21, 2024 03:33 AM

    I see. So you want to sync property values across documents.

    This can also be achieved with an update event, but this time not attached to the class, but to the instance of the document.

    Event actions are the architecturally correct way to achieve both of your requirements, but if you want to avoid them at all costs you could try a sweep job or even an extra program to go through all candidates and change. This woul dbe with a time lag however.

    Using a synchronous event action maintains transaction consistency (all or nothing).

    Hope this helps,

    /Gerold



    ------------------------------
    Gerold Krommer
    Managing Director
    The Document Content Profesionals, G.m.bH
    Wien
    +436602408515
    ------------------------------



  • 6.  RE: Single point of change (How document can Inherit a property value from the parent Folder on Create/Update))

    Posted Wed November 20, 2024 07:26 AM
    Hi Ahmed,
    I have a book published by Apress , "IBM Software Systems Integration" which provides a step by step description for adding a FileNet java Event handler, including a full Java code example (See Chapter 2, Configuring Java Custom Components).
    Available from the following link:


    This shows, as an example, how to trigger a new custom FileNet Event Handler class ( called addDocToFolder) on a specific folder class with a custom property value from the folder as the content of the document property, which I think would satisfy your requirement.


    Alan S Bluck

    (IBM Champion (2024),
    IBM Champion (2023),
    IBM Champion (2022)
    IBM Silver level PartnerWorld Business Partner,
    RedHat Accredited Business Partner,
    Director, ASB Software Development Limited)






  • 7.  RE: Single point of change (How document can Inherit a property value from the parent Folder on Create/Update))

    Posted Wed November 20, 2024 03:51 PM

    Hello Alan,
    Thanks too much for your response, i really appreciate it. I will proceed with your book.

    thank you



    ------------------------------
    Ahmed ElHussein
    ------------------------------



  • 8.  RE: Single point of change (How document can Inherit a property value from the parent Folder on Create/Update))

    Posted Fri November 22, 2024 03:47 PM

    Hi Ahmed, so far posters have shared events but you can also use a few other mechanisms. Now FileNet does not have inheritance for metadata if you use templates you could glue something together but changing a property on the folder will not cause the casade of metadata you want.  Consider the metadata are literal values assigned to each object a better way would be object value properties that way you have one object with your metadata (1x) that both the documents and folder are set to and point to that custom object. Does that make sense? So 5 docs and a parent folder point to the same CO with whatever custom metadata fields you want, the CO instance is on object id. There is no need to cascade the update because everything already points to "this object".   Take a look at reflective OVP properties IMO a powerful but underused feature in FileNet because there have been UI limitations when searching/viewing custom objects in the past. 

    Another option instead of trying to capture the event, filtering if the key metadata field(s) changed and who changed them is the easy approach. Create a manual launch workflow on the folder with your properties and map the properties to exposed fields at that step then have the WF update the initiating attachment (document) and set the properties, then search within the folder and update those properties.  



    ------------------------------
    Jay Bowen
    www.bowenecmsolutions.com
    Medina, OH
    ------------------------------



  • 9.  RE: Single point of change (How document can Inherit a property value from the parent Folder on Create/Update))

    Posted Sun November 24, 2024 10:20 AM

    Hi,

    I like the first idea, because it follows the 'one fact, one place' principle.

    > because there have been UI limitations when searching/viewing custom objects in the past

    Could you elaborate what the improvements are? Last time I looked you just couldn't follow OVPs in ICN or ACCE.

    I'm not so keen on the workflow idea, it is too complicated for daily operations, but is certainly a valid option.

    Kind regards,

    Gerold



    ------------------------------
    Gerold Krommer
    Managing Director
    The Document Content Profesionals, G.m.bH
    Wien
    +436602408515
    ------------------------------