Reccomendation: ECM 16.2 - Folder Monitoring (with eventual file actions)

Options

A request for a way to monitor a folder and archive superseded documents based on a specific naming format + version number has come to me.

I already have a category updater in Node.js (SQL Query to ECM DB, then action via Rest API if file changes need to happen) that sits external to ECM.
I also look after a C# application that can query restapi\DB and currently does a similar job but not towards ECM.
I have never ventured to oscript but I have heard about event triggers. IS there a simple example i can learn from and build upon to achieve my goals.

Currently the node app is on a timer to query large lists and compare, which i want to move away from and i believe an event trigger will be more performant as actions only take place when an update happens

Out of these what would be the recommended approach, perhaps theres one im missing. Thanks in advance

Comments

  • @Franky Egan
    I have never ventured to oscript but I have heard about event triggers. Is there a simple example I can learn from and build upon to achieve my goals.

    Oscript has a robust codebase , having said that what you ask here is probably one of the more difficult things to self learn so I would advise you to spend about

    1. At least 8 to 16 hours of setting up your Development VM or server, Install CSIDE making sure everything works and stays stable.
    2. Perhaps run the Oscript hand-holding documentation from OT. It won't make much sense unless you took the class with a good instructor like "Howard Pell"
    3. Try simple things Add a new Webnode command and action perhaps add a new command on a document subtype called "Franky Egan Command" and maybe print out "Hello World"
    4. I have helped many users in past years when the builder was there but CSIDE is really a builder running in Eclipse so the Oscript parts are reusable but not like how we used to do this in the builder. In my KB workspace, I found a word document that shows how I showed that user a CBCreate "CBCreate in 971 we can see the Added Category from GUI there.docx" can be accessed via the following link: https://knowledge.opentext.com/knowledge/cs.dll/properties/62978719 I won't say this is easy but at least you can see the objects and other things
    5. WR Triggers are exactly this only thing is they listen on things and basically have created configurable things so you aren't necessarily putting your own code. Lately, the OT People don't like end customers changing the code and always will push back saying it's customized and hence we won't support you, but in itself, there is just the selling part thrown in because almost anything complicated OT writes in Oscript At least when I was learning this there wasn't much anything other than Oscript proper to do this so we learned with every year doing things as best as we could.
    6. OT is on a quantum shift with SmartUI wherein OScript is really doing all the heavy lifting but its output is given out in favor of new javascript technologies
      . I will put a bunch of awesome contributors in Oscript and they are very helpful in guiding others there are hundreds so I may forget people not intentional
      Chris Webster https://forums.opentext.com/forums/profile/sıɹɥɔ (I don't know is Chris trying to hide:)
      John https://forums.opentext.com/forums/profile/John Simon(My Mentor)
      Ossie https://forums.opentext.com/forums/profile/ossie.moore@knowledgeworks.ca
      Donna https://forums.opentext.com/forums/profile/dnalls
      Greg https://forums.opentext.com/forums/profile/Greg Griffiths
      Hugh https://forums.opentext.com/forums/profile/Hugh Ferguson
      @Kyle_Swidrovich
      @David Templeton
      @Chris Meyer

    The trick is to search on these guy's posts as this new forum is made up of at least 15 years worth of collaborative material it's just very hard to find things as OT does this every few years. What I do when I am confused is click on Chris's profile and try to get to his comments are and usually, I would find something that is of interest to what I am looking for...

  • @""Franky Egan"
    I am posting so that if you end up choosing oScript you have some idea of what to focus on (rather than learn ALL of the modules and what they do). If I am reading your post correctly it sounds like when the user adds a document within a specific location (folder), named a certain way, then you want to do something. If the "something" needs to happen immediately then you would probably want to do a node callback (this lets you do whatever it is as the document/version is added, and gives you a chance to reject it with proper error messages). If the "something" can happen later then you would be looking at an agent (these can be scheduled with a frequently of every 5 minutes all the way up to once a week).

    And if learning oScript is not in the cards for you right now, there are OT Partners available that you can work with for this kind of thing.

    Cheers...