Content Management and Capture

Content Management and Capture

Come for answers. Stay for best practices. All we’re missing is you.

 View Only

  • 1.  CEBI setting system attributes

    Posted 11 days ago

    Hi,

    I could not find a way, it is not documented and still AI is hallucinating that it is possibe, so I thought I'd ask.

    A customer wants to migrate from a VERY OOOOLD legacy system to CC. The system is so simple that from the database you can get all properties and also can construct the (filesystem) path to the documents. Multiple 'content elements' are possible.

    I thought I'd save some effort by running through the database, creating the transact.dat and the let CEBI finish the job. CEBI can do multiple content elelents.

    But wait: we need to set the values of creator, date created, last modifier, date last modified. Can CEBI do that? E.g. if system attributes are there check for PRIVILEGED_WRITE and then do the right thing?

    If it can't, it is unusuable for migration tasks... and yes, I know I can modify the values later direct in the database but IBM frowns this endeavor and who wants that to happen :-)?

    Kind regards,

    /Gerold



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


  • 2.  RE: CEBI setting system attributes

    Posted 10 days ago

    Gerold

    Typically I don't recommend setting the system properties manually for a migration. Instead, I would recommend you map them to custom properties.

    The main rationale for this is so that the customer can differentiate easily between migrated and native documents. 



    ------------------------------
    RUTH Hildebrand-Lund
    ------------------------------



  • 3.  RE: CEBI setting system attributes

    Posted 7 days ago

    Ruth,

    while I understand what you are saying we found that the user are confused by 2 different creators, 2 different creation dates, 2 different last modifiers and 2 different dates last modified :-(.

    Nevertheless I tried it and - indeed  - the system fields are set as long as the executing user has the correct priviledges.

    Kind regards,

    Gerold



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

    Original Message


  • 4.  RE: CEBI setting system attributes

    Posted yesterday

    Why not just update those "System Properties" as a separate migration step. You can track the imports for later updates using other means. My last customer dug their own special rabbit hole by defining their own "Creation Date" (same display name, different symnbolic name) but later used the system field instead. Every time a workflow step completed they stored it as a custom object and then overwrote the document property so they could then search it... using custom views on DocVersion, of couse.. They solved the access problem "bug" by adding all employees to a group with special privileges during the employee on-boarding process. In 10 years they NEVER went back and fixed their code and had 5000 admins. (ROFL).  The developers just blamed FileNet for everything and in time convinced the business and management to replace FileNet. 



    ------------------------------
    steve weck
    ------------------------------

    Original Message


Related Content