ucdavis / ucdavis/Purchasing

Same number characters in OPP and KFS Item Description Fields

Open
#325 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feedback
Dominant language
C#
Stars
7
Forks
5
PR merge metrics
No merged PRs in 30d

Description

I think the line item description fields for the Kuali requisition and OPP should have the same number of characters. Because they don't, some of our text from OPP ticket HOUS-EIJK9BK was dropped when converting to purchase order UCD159798. The SSC and Contracting Services apparently didn't see that the text was missing and the purchase order went to the vendor that way. See attached.

20151209104557.pdf 377 KB - 0 downloads
Janet Horrigan on December 9, 2015 10:53 AM (0 comments) Public permalink

Votes: 1
Author: jsylvest
Voters: jsylvest

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing where OPP and KFS item description fields are defined and where OPP text is converted into a purchase order. Compare their character limits and inspect how overlong text is handled. Done means the fields use the same limit and the conversion no longer silently drops description text.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.