log audit logs for filetype settings and segmentation rules

XMLWordPrintable

    • High
    • None
    • Hide
      Added audit logging for the file filters:
      Bconf lifecycle: upload, clone, create, update (name/description/customer), delete
      Bconf defaults: set as instance default; default bconf per client
      Segmentation: SRX upload (including purpose source/target and file name)
      Pipeline: pipeline upload
      Custom filters: create, change (name/extensions), delete
      Filter settings: .fprm saved via the filter editor, .fprm uploaded
      Extension mapping: extensions changed, filter removed from the mapping
      Show
      Added audit logging for the file filters: Bconf lifecycle: upload, clone, create, update (name/description/customer), delete Bconf defaults: set as instance default; default bconf per client Segmentation: SRX upload (including purpose source/target and file name) Pipeline: pipeline upload Custom filters: create, change (name/extensions), delete Filter settings: .fprm saved via the filter editor, .fprm uploaded Extension mapping: extensions changed, filter removed from the mapping
    • None

      Problem

      In support from time to time questions of the following type are popping up:

      Who did setup / change XY and when?

      For warranty reasons we should log such information, since sometimes the clients are assuming bugs or wrong setups / configurations for setting that were changed by their users.

      Solution

      log changes in bconf/segmentation rules with user and time * changes of .fprm (Okapi filetype settings file): change, create, delete; including setting it as default for instance/client, changing the default, changing the actual settings for the filetypes etc., so any change

      • changed segmentation rules (srx upload)
      • changed extension-mapping in filtype settings
      • changes filters
      • changed pipelines

      Implementation Details

      1) Upload BCONF

editor_Plugins_Okapi_BconfController::uploadbconfAction()
-> at the end, if action was successfull, log bconf->getId() & bconf->getName()


2) Upload SRX

editor_Plugins_Okapi_BconfController::uploadsrxAction
-> if no exception occurs, log bconfId, $field && $uploadName of $segmentation->processUpload(...)


3) Upload Pipeline

editor_Plugins_Okapi_BconfController::uploadpipelineAction
-> log bconfId, "Pipeline exchanged"


4) Change ExtensionMapping (for non-custom filters)
    
editor_Plugins_Okapi_BconfDefaultFilterController::setextensionsAction()
-> log bconfId, identifier, extensions


5) Change extensions for customized Filter
    
editor_Plugins_Okapi_BconfFilterController::postAction
AND editor_Plugins_Okapi_BconfFilterController::putAction
-> log bconfId, identifier of FPRM, extensions


6) Edit customized Filter

editor_Plugins_Okapi_BconfFilterController::savefprmAction
-> log bconfId, identifier of FPRM


7) Add customized Filter

editor_Plugins_Okapi_BconfFilterController::uploadfprmAction
-> log bconfId, identifier of FPRM


8) Delete customized Filter

editor_Plugins_Okapi_BconfFilterController::deleteAction
-> log bconfId, identifier of FPRM

            Assignee:
            Sasha
            Reporter:
            Sylvia Schumacher
            Sylvia Schumacher Sylvia Schumacher
            Axel Becher
            Axel Becher, Sanya Mikhliaiev
            Axel Becher
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None