[KULRICE-4777] Fix workflow for Travel Request (sample travel app) Created: 20/Oct/10  Updated: 16/Jan/15

Status: Open
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: 1.0.3
Fix Version/s: Backlog

Type: Bug Fix Priority: Major
Reporter: Peter Giles (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: Old
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Rice Module:
KNS
KAI Review Status: Not Required
KTI Review Status: Not Required

 Description   

There are some apparent issues (and some suspected ones) with the way the routing rules for the sample travel app are set up, and the way the workflow is playing out:

  • rule 'TravelRequest.Supervisor' is using rule template 'TravelerRequest-TravelerRouting'
  • rule 'TravelRequest.FiscalOfficer' is using rule template 'TravelRequest-SupervisorRouting'
  • the rule for template 'TravelRequest-AccountRouting' is named '659D86718DD514C7E0404F8189D877C3' and doesn't appear to be functioning
    • in my test, the fiscal officer never had to approve
    • looking at the rule template for TravelRequest-AccountRouting, it has the AccountAttribute rule attribute, but using the 'Routing Report' feature, the attribute isn't showing up as it should.

Generated at Sat Sep 26 03:55:46 CDT 2020 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.