Details

    • Type: New Feature New Feature
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0
    • Component/s: Development
    • Labels:
      None
    • Similar issues:
      KULRICE-2241Add XML Export support to KNS lookups
      KULRICE-2297Add "Export Hierarchy" button to Document Type inquiry when converting it to KNS
      KULRICE-4332 Build xml export support for Groups screen
      KULRICE-5255Implement export functionality in KRAD inquiry
      KULRICE-2507Add support for fromDate and toDate to Rule XML export and import
      KULRICE-2634Implement support for better XML export, XML import and migration features
      KULRICE-5041Migrate xml import/export framework to the Rice core
      KULRICE-9805Lookup - Need export for document type xml to use proper export function
      KULRICE-5388Lookup - Add support for specifying a menubar
      KULRICE-10257Implement support for inquiry in conversion scripts

      Description

      In KEW we put an "Export" button on our inquiries that allow us to export the business object to XML. In the version of Rice that I'm looking at (0.9.4) I don't see any way to add custom buttons to inquiries but I think Ailish mentioned that they just added that feature (might be on the 0.9.4 kfs branch?). We need to check on that and figure out if that feature is available or if we need to work on it ourselves. Once we have the ability to add custom buttons, we can have the export button rendered automatically based on whether or not the BusinessObject has an exporter registered in it's data dictionary file.

        Issue Links

          Activity

          Hide
          Ailish Byrne added a comment -

          i don't get why you need the custom buttons feature for this. i would think you would just build this right into the inquiry framework when a custom exporter exists or some other prop is set on the inquiry dd object to show export option on inquiry. custom button is not for things like this where support is built into the framework - i.e. the work you did to add the prop to the bo dd entry. can you lmk what i'm missing?

          Show
          Ailish Byrne added a comment - i don't get why you need the custom buttons feature for this. i would think you would just build this right into the inquiry framework when a custom exporter exists or some other prop is set on the inquiry dd object to show export option on inquiry. custom button is not for things like this where support is built into the framework - i.e. the work you did to add the prop to the bo dd entry. can you lmk what i'm missing?
          Hide
          Eric Westfall added a comment -

          Yeah, not really sure what I was thinking here. Was still thinking of it from the perspective of export not being built into the KNS.

          Show
          Eric Westfall added a comment - Yeah, not really sure what I was thinking here. Was still thinking of it from the perspective of export not being built into the KNS.
          Hide
          Eric Westfall added a comment -

          Ah, just remembered, for standard export this can be built into the KNS but we wiil probably need to take advantage of the custom buttons feature in order to implement the "Export Hierarchy" feature on Document Type.

          Show
          Eric Westfall added a comment - Ah, just remembered, for standard export this can be built into the KNS but we wiil probably need to take advantage of the custom buttons feature in order to implement the "Export Hierarchy" feature on Document Type.
          Hide
          Eric Westfall added a comment -

          Standard XML export is implemented on Inquiries now. The export button only shows up if the business object has an exporter that supports XML export. I had to re-implement how the close button was implemented a bit in order to get the 2 buttons to look good next to each other. It's still javascript-based with the SCRIPT and NOSCRIPT tags but it uses a input type=image instead of an href surrounding an img tag.

          I will create a separate issue for the export hierarchy function of Document Type.

          Show
          Eric Westfall added a comment - Standard XML export is implemented on Inquiries now. The export button only shows up if the business object has an exporter that supports XML export. I had to re-implement how the close button was implemented a bit in order to get the 2 buttons to look good next to each other. It's still javascript-based with the SCRIPT and NOSCRIPT tags but it uses a input type=image instead of an href surrounding an img tag. I will create a separate issue for the export hierarchy function of Document Type.
          Hide
          Eric Westfall added a comment -

          Bulk change of all Rice 1.0 issues to closed after public release.

          Show
          Eric Westfall added a comment - Bulk change of all Rice 1.0 issues to closed after public release.

            People

            • Assignee:
              Eric Westfall
              Reporter:
              Eric Westfall
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel