Uploaded image for project: 'KFS Archive'
  1. KFS Archive
  2. KFSOLD-7515

content routing did not work - doc ID 305855 req # 1003

    Details

    • Type: Bug Fix
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: <= 3.x
    • Labels:
      None
    • Sub-Committee:
      AP / DV / PDP, PUR / VND
    • Impacted Modules:
      Purchasing / Accounts Payable

      Description

      created a requisition for BL-PSY did not add accounts - document should have routed to content approver (demotley) however the req is now in exception routing

        Attachments

          Issue Links

            Activity

            Hide
            delyea David Elyea added a comment -

            I think the problem here was that the validation that was supposed to have run did not run. This document was a BL-PSY document and i don't see a Content level rule for BL-PSY so in theory Marilyn should have seen an error requiring her to enter the full chart and org and percent values for accounts for her items (with object code not needed until Fiscal Review). I don't know if the validation did not run because there is a problem with the PURAP code or if this is a problem with the Workflow code that tells the PURAP code whether to run the validation or not. I may need help in taking a look at this though as i'm not too familiar with the validation and how it works in Kuali.

            This did expose somewhat of a potential Workflow bug but for this particular case i do think the problem is the incorrect validation being run.

            Show
            delyea David Elyea added a comment - I think the problem here was that the validation that was supposed to have run did not run. This document was a BL-PSY document and i don't see a Content level rule for BL-PSY so in theory Marilyn should have seen an error requiring her to enter the full chart and org and percent values for accounts for her items (with object code not needed until Fiscal Review). I don't know if the validation did not run because there is a problem with the PURAP code or if this is a problem with the Workflow code that tells the PURAP code whether to run the validation or not. I may need help in taking a look at this though as i'm not too familiar with the validation and how it works in Kuali. This did expose somewhat of a potential Workflow bug but for this particular case i do think the problem is the incorrect validation being run.
            Hide
            delyea David Elyea added a comment -

            I guess i should have fished in the code before commenting. I found the error i think. It looks like it's a simple 'not' check. Right now the code looks like it's saying "If the document will stop in content level routing.... make sure there are accounts and make sure the percents are correct.

            Show
            delyea David Elyea added a comment - I guess i should have fished in the code before commenting. I found the error i think. It looks like it's a simple 'not' check. Right now the code looks like it's saying "If the document will stop in content level routing.... make sure there are accounts and make sure the percents are correct.
            Hide
            delyea David Elyea added a comment -

            i fixed the 'not' problem i was talking about in my previous comment. It should be testable at the next deploy to the environment of your choice.

            I've also created a JIRA for some potential validation holes i found while looking at all this. It seems the validation for a REQ in terms of what happens when it routes needs a little reworking. Chris and i will probably have to discuss it since he knows the KFS side and i know what we'll need from a routing standpoint.

            Show
            delyea David Elyea added a comment - i fixed the 'not' problem i was talking about in my previous comment. It should be testable at the next deploy to the environment of your choice. I've also created a JIRA for some potential validation holes i found while looking at all this. It seems the validation for a REQ in terms of what happens when it routes needs a little reworking. Chris and i will probably have to discuss it since he knows the KFS side and i know what we'll need from a routing standpoint.
            Hide
            delyea David Elyea added a comment -

            This issue should be fixed to a working state now. I've linked two issues which deal with some of the other potential errors i had mentioned in comments.

            Show
            delyea David Elyea added a comment - This issue should be fixed to a working state now. I've linked two issues which deal with some of the other potential errors i had mentioned in comments.
            Hide
            mkisters Marilyn Kisters (Inactive) added a comment -

            retested on build 522

            Show
            mkisters Marilyn Kisters (Inactive) added a comment - retested on build 522

              People

              • Assignee:
                Unassigned
                Reporter:
                abyrne Ailish Byrne
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: