From 57894c16cad99fe6e0437a18cc96f37faeb2bcec Mon Sep 17 00:00:00 2001 From: mk-dds Date: Thu, 18 Jul 2019 13:50:48 -0400 Subject: [PATCH] Update TO to be 13 digits --- js/lib/input_validations.js | 4 ++-- translations.yaml | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/js/lib/input_validations.js b/js/lib/input_validations.js index 5c618bd4..a873b3c0 100644 --- a/js/lib/input_validations.js +++ b/js/lib/input_validations.js @@ -72,9 +72,9 @@ export default { }, taskOrderNumber: { mask: false, - match: /^.{10}$/, + match: /^.{13}$/, unmask: [], - validationError: 'TO number must be 10 digits', + validationError: 'TO number must be 13 digits', }, usPhone: { mask: [ diff --git a/translations.yaml b/translations.yaml index 61620ecf..fc3dc09e 100644 --- a/translations.yaml +++ b/translations.yaml @@ -172,7 +172,7 @@ forms: 'no': 'No, not planning to develop natively in the cloud' not_sure: 'Not sure, unsure if planning to develop natively in the cloud' not_sure_help: Not sure? Talk to your technical lead about where and how they plan on developing your application. - number_description: Task order number (10 digit number from your system of record) + number_description: Task order number (13 digit number from your system of record) scope_description: 'What do you plan to do on the cloud? Some examples might include migrating an existing application or creating a prototype. You don’t need to include a detailed plan of execution, but should list key requirements. This section will be reviewed by your contracting officer, but won’t be sent to the CCPO.

Not sure how to describe your scope? Read some examples to get some inspiration.

' scope_label: Cloud project scope start_date_label: Start of period of performance (PoP)