1 / 81

MarkeTrak Phase 2a

MarkeTrak Phase 2a. Technical Walk Through. Req 7 – No User Changes to Issue Title Field. GUI Issue Title not available on Submit Read only on all other Screens Default Issue Title supplied by MarkeTrak. Req 7 – No User Changes to Issue Title Field.

bailey
Download Presentation

MarkeTrak Phase 2a

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MarkeTrak Phase 2a Technical Walk Through

  2. Req 7 – No User Changes to Issue Title Field • GUI • Issue Title not available on Submit • Read only on all other Screens • Default Issue Title supplied by MarkeTrak

  3. Req 7 – No User Changes to Issue Title Field

  4. Req 7 – No User Changes to Issue Title Field • API • Title element removed from Submit and Update Complex Types • Title element will be returned on Query Detail Responses

  5. Req 7 – No User Changes to Issue Title Field • Bulk Insert • Title column removed from all Bulk Insert table definitions

  6. Req 8 – Only Capture Owner if Owner field empty • GUI • Appropriate Owner field populated with transitioning userid on “Begin Working” transition only if Owner field is empty

  7. Req 8 – Only Capture Owner if Owner field empty (before)

  8. Req 8 – Only Capture Owner if Owner field empty (after)

  9. Req 8 – Only Capture Owner if Owner field empty • API • No noticeable changes • MPs should review “Assign Owner” API backend logic to reduce needless API traffic

  10. Req 8 – Only Capture Owner if Owner field empty • Bulk Insert • No changes

  11. Req 13 – Updates to D2D Missing Transactions Workflow • GUI • Added “Original Tran ID” field help • Limited Tran Type choices on “Submit” and “ReAssign” transitions • New field, “Tran ID” required on “Complete” transition • Tran Type updatable on “ReAssign” transition

  12. Req 13 – Updates to D2D Missing Transactions (Original tran ID help)

  13. Req 13 – Updates to D2D Missing Transactions (limit Tran Types)

  14. Req 13 – Updates to D2D Missing Transactions (ReAssign)

  15. Req 13 – Updates to D2D Missing Transactions Workflow • API • Replaced “MissTrxn” element in “SubTypeD2DResponseType” complex type with new “MissTrxnResp” element • Replaced “TrxnType” element in “MissTrxnType” complex type with “TrxnMissingType” element • Add “TrxnID” element to “MissTrxnType” complex type

  16. Req 13 – Updates to D2D Missing Transactions Workflow • API (cont) • Added “MissTrxnRespType” complex type • Defined “MissTrxnResp” as type “MissTrxnRespType” • Defined “TrxnID” as type “origTrxnDef” • Defined “TrxnMissingType" as type “trxnMissingTypeDef” • Defined “trxnMissingTypeDef” with valid transaction types

  17. Req 13 – Updates to D2D Missing Transactions Workflow • Bulk Insert • Transaction type validation added

  18. Req 15 – Validate TDSP Involved • GUI • Upon Submit transition • Not IAS/IAG/D2D 997 Issue • Warning Message (user can “OK” thru) • Valid ESIID • Either Submitter or Assignee must “own” ESIID in question

  19. Req 15 – Validate TDSP Involved

  20. Req 15 – Validate TDSP Involved • API • Added “ValidateTDSP” flag element to “IssueSubmitRequest” complex type • Removed validation flags from “UpdateRequestIssueType” complex type • Defined “ValidateTDSP” as boolean, default of ‘false”

  21. Req 15 – Validate TDSP Involved • Bulk Insert • New “Validate TDSP” column added • If value “0”/”false” then validation not performed • Optional on all except “997 Issues”, “Inadvertent Gaining” and “Inadvertent Losing”

  22. Req 16 – Updates to Usage/Billing • GUI • Limit selections for “Tran Type” • “Tran Type” field required on Submit/Create • New “IDR/Non-IDR” field • “Original Tran ID” required if “Tran Type” = “867_03F” • New “Dispute/Missing” field • “Transaction Date” is required on Submit/Create

  23. Req 16 – Updates to Usage/Billing • GUI (cont) • New “Tran ID” required on “Complete” transition if “Missing” type • New “Tran ID” required on “Submit/Create” if “Dispute” type

  24. Req 16 – Updates to Usage/Billing (Tran Type require and limited)

  25. Req 16 – Updates to Usage/Billing(required fields)

  26. Req 16 – Updates to Usage/Billing(Tran ID required on Complete)

  27. Req 16 – Updates to Usage/Billing • API • Replaced “UsageBilling” element with “UsageBillingResp” element in “SubTypeD2DResponseType” complex type • Made “OrigTrxnID” optional in “UsageBillingType” complex type • Replaced “TrxnType” element with “TrxnUsageBillType” element in “UsageBillingType” complex type

  28. Req 16 – Updates to Usage/Billing • API (cont) • Made “TrxnDate” required on Submit/Create • Add “TrxnID” element • Add “DisputeMissing” element • Add “IDRNonIDR” element • Define “UsageBillingRespType” complex type • Define “UsageBillingResp” as type “UsageBillingRespType”

  29. Req 16 – Updates to Usage/Billing • API (cont) • Define “TrxnUsageBillingType” as type “trxnUsageBillTypeDef” • Define “DisputeMissing” as type “DisputeMissingDef” • Define “IDRNonIDR” as type “IDRNonIDRDef” • Add “810_02”, 867_03 Monthly 00“, "867_03 Monthly 01“, "867_03 Monthly 05“, "810_02 Monthly 00“, "810_02 Monthly 01“, and "810_02 Monthly 05“ to “TrxnTypeDef” enumerations

  30. Req 16 – Updates to Usage/Billing • API (cont) • Define “trxnUsageBillingTypeDef” enumerations • Define “DisputeMissingDef” enumerations • Define “IDRNonIDRDef” enumerations

  31. Req 16 – Updates to Usage/Billing • Bulk Insert • Make “Orig Tran ID” optional, required if “Tran Type” = “867_03F” • Make “Tran Type” required • Make “Transaction Date” required • Make “Missing/Dispute” required • Make “Transaction ID” optional, required if “Missing/Dispute” = “Dispute” • Make “IDR/Non-IDR” required

  32. Req 18 – Standardize DEV LSE sub-type names • GUI • Change “LSE in MP not ERCOT: inactiv” to “LSE in MP not ERCOT: De-engz” on Submit tree

  33. Req 18 – Standardize DEV LSE sub-type names

  34. Req 18 – Standardize DEV LSE sub-type names • API • Add “LSE in MP sys not ERCOT: de-engz – CR” and “LSE in MP sys not ERCOT: de-engz – TDSP” as valid enumerations for “issueSubTypeDef”

  35. Req 18 – Standardize DEV LSE sub-type names • Bulk Insert • Change “LSE in MP not ERCOT: inactiv – CR” to “LSE in MP not ERCOT: De-engz – CR” on Bulk Insert sub-type drop down list • Change “LSE in MP not ERCOT: inactiv – TDSP” to “LSE in MP not ERCOT: De-engz – TDSP” on Bulk Insert sub-type drop down list

  36. Req 18 – Standardize DEV LSE sub-type names

  37. Req 19 – Changes to ERCOT Initiated • API • Add “SiebelStatus”, “SiebelSubStatus”, and “SiebelCheckDateTime” fields to “ERCOTInitiatedTypeResponse” complex type

  38. Req 22 – Validate CR on Siebel Chg/Info • GUI • Valid Global ID • Submit/Create transition • Error message if neither Submitter or Assignee isn’t the CR involved with Global ID

  39. Req 22 – Validate CR on Siebel Chg/Info

  40. Req 22 – Validate CR on Siebel Chg/Info • API • Error message returned if neither Submitter or Assignee isn’t the CR involved with Global ID

  41. Req 22 – Validate CR on Siebel Chg/Info • Bulk Insert • Error message if neither Submitter or Assignee isn’t the CR involved with Global ID

  42. Req 24 – DEV LSE field Layout • GUI • “Usage Matches Date Requested”, “Usage Loaded for Date Requested” and “Another CR Involved” fields will appear separately • On “LSE in ERCOT system not MP” workflow, replace “Row Exists at ERCOT” with “Usage Matches Date Requested” • On “LSE in ERCOT system not MP” workflow, replace “Usage Exists for Time Period” with “Usage Loaded for Date Date Requested”

  43. Req 24 – DEV LSE field Layout

  44. Req 24 – DEV LSE field Layout • API • Remove “RowExistsERCOT” and “UsageExistsForTimePeriod” elements from “UpdateDevLSEType” • Remove “RowExistsERCOT” and “UsageExistsForTimePeriod” elements from “DevLSEResponseType” • Remove “RowExistsERCOT” element definition

  45. Req 24 – DEV LSE field Layout • API (cont) • Remove “UsageExistsForTimePeriod” element definition • Remove “usageExistsForTimePeriodDef” simple type

  46. Req 24 – DEV LSE field Layout • Bulk Insert • No changes

  47. Req 25 – New IAG Workflows • GUI • Users no longer able to submit IAS issues • Users will still be able to update current IAS issues • 2 new workflows added to Submit Tree: • Inadvertent Gaining • Inadvertent Losing • Users will be able to run Reports against IAS and IAGs issues by selecting “IAG” from project list

  48. Req 25 – New IAG Workflows • GUI (cont) • Error thrown if “Proposed Regain Date” is greater than 15 days from Issue submit date • Comments are required if “Invalid IAG Reason” is “Other” or “Invalid Order Type” on “Select IAS parties” transition

  49. Req 25 – New IAG Workflows

  50. Req 25 – New IAG Workflows • API • Add “IaGg” and “IaGl” to “SubTypeD2DType” complex type • Add “IaGgResponse” and “IaGlResponse” to “SubTypeD2DResponseType” complex type • Add “ProposedRegainDate”, “RegainingBGN02”, “TransactionDate”, “RegainingGlobalID”, “UnexecutableReason”, and “RegainingTrxnSubmitDate” to “SubTypeUpdateD2DType” complex type

More Related