Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-13779

Create Travel Authorization transactional document in KRAD

    Details

    • Similar issues:
      KULRICE-11520Create Automated Functional (Smoke) Tests for KRAD Demo - Travel Application: Authorization Document
      KULRICE-11440Create Automated Function Test for KRAD Demo Travel Authorization
      KULRICE-5653Create KRAD Version of Travel Account Document
      KULRICE-5656Create KRAD version of Travel Account Type document
      KULRICE-13024Styling issues with travel authorization document
      KULRICE-13843Create working transactional document POC
      KULRICE-5652Create KRAD Version of Create New Sample Application Travel Request Document
      KULRICE-9984Component Library: Travel Authorization Request missing expand/collapse
      KULRICE-5655Create KRAD Version of Travel Account Use Rate document
      KULRICE-9759Create Smoke Tests for KRAD Demo - Travel Authorization
    • Rice Team:
      QA

      Description

      KRAD doesn't have any example of a transactional document yet. We would like to build one within the travel sample app. rSmart is working on the KFS travel module and has an authorization document that would be a good thing to showcase in KRAD. The document can be found here (login as 'khuntley'):

      http://temnightly.kfs.rsmart.com/kfs-dev/portal.do?channelTitle=Travel%20Reimbursement&channelUrl=temTravelReimbursement.do?methodToCall=docHandler&command=initiate&docTypeName=TR

      Reproduce this in KRAD. This will require adding some business objects (with tables and data). Also, would like four views of this:

      1) As is with KFS travel (vertical tabs)
      2) Left menu (tabs become pages)
      3) Horizontal Tabs
      4) KS Look and Feel with Menu

      Try to add progressive disclosure, component refresh, client side validation, ajax queries and so on where possible (in short use as many of the KRAD features as you can).

      Please make sure to document the code well, follow coding standards and formatting.

      Also, create Selenium scripts verifying the document functionality.

      I will ask to see if we can get a contact from rSmart to help us getting any requirements we need for the document.

        Activity

          People

          • Assignee:
            Unassigned
            Reporter:
            Jerry Neal (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 3 weeks
              3w
              Remaining:
              Remaining Estimate - 3 weeks
              3w
              Logged:
              Time Spent - Not Specified
              Not Specified

                Structure Helper Panel