• High
    • None
    • Make Okapi integration more resilient regarding the usage of not supported features in the bconf
    • None

      problem

      Marc created a more sophisticated bconf file for a special use case (with an internal XSLT pre pipeline step).

      The bconf file could not be uploaded to t5

      solution

      • Add a XSLT step to our Pipeline Manegment
      • Therfore the embedded XSLT needs to be recognised & processed in the Unpacker and Packer
      • The XSLT should be added to the content.json and is a integral part of the bconf after import
      • The packed bconf must match the imported one obviously
      • [Future Enhancement: In the Pipline-Editor a XSLT step is addable in conjunction with uploading a XSLT file]

            Assignee:
            Volodymyr Kyianenko (Inactive)
            Reporter:
            Thomas Lauria
            None
            None
            Thomas Lauria
            None
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None