Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

-Uses the same form in the App for University Expense Card Request

-Forms are auto-created from a file we get from Concur.

-Form utilizes flags for DBC/Travel Card to show/hide correct fields when needed.  This includes on ST_Start and through the various DBC and Travel Card stages.

Use Case (happy path)

  1. New form auto-created for each user from Concur .csv file
    1.  (Elements: First Name, Last Name, User Email, Spend Limit, Declining Balance Begin Date, Declining Balance End Date, User Net Id, DBC Flag, Employee Id)
  2. DBC User (student) receives email notification to complete form.
  3. DBC User completes form.
  4. Expense Card Admin group receives notification of submitted form.
  5. Expense Card Admin Approves form.
  6. DBC User receives notification of approval and link to form.
  7. Expense Card Admin transmits form.  Form is created in export report.
  8. Expense Card Admin Exports the data into Excel.


Travel Card Request Application_data specs_20200630.xlsx

Travel Card Request Application_data specs_20200818.xlsx

TCard_and_DBC_Report_Export_DEVSAMPLE.xls

-The fields we still need values for are below under Fields TBD

-I have set up some basic Email Notifications for when certain actions are taken.  Below is the wording used.  Let me know if you want anything changed.

-I have provided a basic Use Case below to give you an idea of the workflow.

-Attached is the updated data spec from our meeting last week.

  • No labels