@forwardslashns/taskit-validation-messages 1.9.9 → 1.10.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/validation/features/client-records-filing-statuses-histories.validation-messages.d.ts +91 -0
- package/dist/validation/features/client-records-filing-statuses-histories.validation-messages.d.ts.map +1 -0
- package/dist/validation/features/client-records-filing-statuses-histories.validation-messages.js +93 -0
- package/dist/validation/validation-messages.d.ts +55 -55
- package/dist/validation/validation-messages.js +2 -2
- package/package.json +1 -1
- package/src/validation/features/client-records-filing-statuses-histories.validation-messages.ts +90 -0
- package/src/validation/validation-messages.ts +2 -2
- package/dist/validation/features/client-records-filing-types-histories.validation-messages.d.ts +0 -91
- package/dist/validation/features/client-records-filing-types-histories.validation-messages.d.ts.map +0 -1
- package/dist/validation/features/client-records-filing-types-histories.validation-messages.js +0 -93
- package/src/validation/features/client-records-filing-types-histories.validation-messages.ts +0 -90
package/dist/validation/features/client-records-filing-statuses-histories.validation-messages.d.ts
ADDED
|
@@ -0,0 +1,91 @@
|
|
|
1
|
+
export declare const CLIENT_RECORDS_FILING_STATUSES: {
|
|
2
|
+
readonly FILING_STATUS_ID_DOES_NOT_EXIST: {
|
|
3
|
+
readonly message: "Sub/Parent status does not exist";
|
|
4
|
+
readonly params: readonly ["id"];
|
|
5
|
+
readonly affectedFields: readonly ["filingStatus"];
|
|
6
|
+
};
|
|
7
|
+
readonly FILING_STATUS_PARENT_REQUIRED: {
|
|
8
|
+
readonly message: "Parent needs to be specified for filing status 'Files under parent'";
|
|
9
|
+
readonly affectedFields: readonly ["currentParent"];
|
|
10
|
+
};
|
|
11
|
+
readonly CURRENT_FILING_STATUS_PARENT_REQUIRED: {
|
|
12
|
+
readonly message: "Parent needs to be specified for current filing status 'Files under parent'";
|
|
13
|
+
readonly affectedFields: readonly ["currentParent"];
|
|
14
|
+
};
|
|
15
|
+
readonly NOT_ALIGNED_DATE_ESTABLISHED_FILING_STATUS_STARTING_DATE: {
|
|
16
|
+
readonly message: "The Sub/Parent status {filingStatus} starts on {filingStatusStartingDate} which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the Sub/Parent status or the client's date established.";
|
|
17
|
+
readonly params: readonly ["clientDateEstablished", "filingStatus", "filingStatusStartingDate"];
|
|
18
|
+
readonly affectedFields: readonly ["dateEstablished", "filingStatus"];
|
|
19
|
+
};
|
|
20
|
+
readonly NOT_ALIGNED_CLOSE_DATE_FILING_STATUS_STARTING_DATE: {
|
|
21
|
+
readonly message: "One or more Sub/Parent status have a start date which is after the client's close date of {clientCloseDate}. {filingStatus}, starting {filingStatusStartingDate}. Please update the start date to be earlier than the client's close date, or update the client's close date.";
|
|
22
|
+
readonly params: readonly ["clientCloseDate", "filingStatus", "filingStatusStartingDate"];
|
|
23
|
+
readonly affectedFields: readonly ["closeDate", "filingStatus"];
|
|
24
|
+
};
|
|
25
|
+
readonly FILING_STATUS_STARTING_DATE_NOT_POPULATED: {
|
|
26
|
+
readonly message: "Current Sub/Parent status Starting Date cannot be Empty";
|
|
27
|
+
readonly affectedFields: readonly ["filingStatusStartingDate"];
|
|
28
|
+
};
|
|
29
|
+
readonly NOT_ALIGNED_FILING_STATUS_STARTING_ENDING_DATE: {
|
|
30
|
+
readonly message: "Sub/Parent status starting date needs to be before the ending date";
|
|
31
|
+
readonly affectedFields: readonly ["filingStatusStartingDate", "filingStatusEndingDate"];
|
|
32
|
+
};
|
|
33
|
+
readonly FILING_STATUSES_IDS_DOES_NOT_EXIST: {
|
|
34
|
+
readonly message: "Sub/Parent status do not exist";
|
|
35
|
+
readonly params: readonly ["ids"];
|
|
36
|
+
readonly affectedFields: readonly ["filingStatus"];
|
|
37
|
+
};
|
|
38
|
+
readonly AT_LEAST_ONE_FILING_STATUS_SHOULD_EXIST: {
|
|
39
|
+
readonly message: "At least one Sub/Parent status should exist";
|
|
40
|
+
readonly affectedFields: readonly ["filingStatus"];
|
|
41
|
+
};
|
|
42
|
+
readonly FILING_STATUSES_STARTING_DATE_NOT_POPULATED: {
|
|
43
|
+
readonly message: "Starting date for {filingStatus} cannot be empty";
|
|
44
|
+
readonly params: readonly ["filingStatus"];
|
|
45
|
+
readonly affectedFields: readonly ["filingStatusStartingDate"];
|
|
46
|
+
};
|
|
47
|
+
readonly NOT_ALIGNED_FILING_STATUSES_STARTING_ENDING_DATE: {
|
|
48
|
+
readonly message: "The ending date for {filingStatus} must be after its starting date";
|
|
49
|
+
readonly params: readonly ["filingStatus"];
|
|
50
|
+
readonly affectedFields: readonly ["filingStatusStartingDate", "filingStatusEndingDate"];
|
|
51
|
+
};
|
|
52
|
+
readonly NOT_ALIGNED_DATE_ESTABLISHED_FILING_STATUSES_STARTING_DATE: {
|
|
53
|
+
readonly message: "Adjust the start date to be on or after the client's date established, {clientStartDate}.";
|
|
54
|
+
readonly params: readonly ["clientStartDate"];
|
|
55
|
+
readonly affectedFields: readonly ["filingStatusStartingDate", "dateEstablished"];
|
|
56
|
+
};
|
|
57
|
+
readonly NOT_ALIGNED_CLOSE_DATE_FILING_STATUSES_STARTING_DATE: {
|
|
58
|
+
readonly message: "Adjust the start date to be before the client's close date, {clientCloseDate}.";
|
|
59
|
+
readonly params: readonly ["clientCloseDate"];
|
|
60
|
+
readonly affectedFields: readonly ["filingStatusStartingDate", "closeDate"];
|
|
61
|
+
};
|
|
62
|
+
readonly FILING_STATUSES_DATE_GAP_DETECTED: {
|
|
63
|
+
readonly message: "There is a gap in the timeframes between {currentFilingStatus}, ending {currentFilingStatusEndDate}, and {nextFilingStatus}, starting {nextFilingStatusStartDate}. Please adjust the dates to fill this gap.";
|
|
64
|
+
readonly params: readonly ["currentFilingStatus", "currentFilingStatusEndDate", "nextFilingStatus", "nextFilingStatusStartDate"];
|
|
65
|
+
readonly affectedFields: readonly ["filingStatus"];
|
|
66
|
+
};
|
|
67
|
+
readonly FILING_STATUSES_CONSECUTIVE_DUPLICATES_DETECTED: {
|
|
68
|
+
readonly message: "There are two entries for {filingStatus} with timeframes that immediately follow each other. {filingStatus} ending {firstPeriodEnd}, and {filingStatus} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {filingStatus}. ";
|
|
69
|
+
readonly params: readonly ["filingStatus", "firstPeriodStart", "firstPeriodEnd", "secondPeriodStart"];
|
|
70
|
+
readonly affectedFields: readonly ["filingStatus"];
|
|
71
|
+
};
|
|
72
|
+
readonly FILING_STATUS_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
|
|
73
|
+
readonly message: "There is a gap between the client's date established ({dateEstablished}) and the start date of {earliestFilingStatus} ({earliestFilingStatusStartDate}). Please ensure that the status of one Sub/Parent status matches the client's date established.";
|
|
74
|
+
readonly params: readonly ["dateEstablished", "earliestFilingStatus", "earliestFilingStatusStartDate"];
|
|
75
|
+
readonly affectedFields: readonly ["filingStatus", "dateEstablished"];
|
|
76
|
+
};
|
|
77
|
+
readonly FILING_STATUSES_DATES_OVERLAP: {
|
|
78
|
+
readonly message: "The client already has {filingStatus} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.";
|
|
79
|
+
readonly params: readonly ["filingStatus", "startDate1", "endDate1", "startDate2", "endDate2"];
|
|
80
|
+
readonly affectedFields: readonly ["filingStatus"];
|
|
81
|
+
};
|
|
82
|
+
readonly ALL_NON_LAST_FILING_STATUSES_REQUIRE_ENDING_DATE: {
|
|
83
|
+
readonly message: "Only the last Sub/Parent status can be open without an end date. Add an ending date to the existing Sub/Parent status before adding a start date for a new Sub/Parent status.";
|
|
84
|
+
readonly affectedFields: readonly ["filingStatusEndingDate"];
|
|
85
|
+
};
|
|
86
|
+
readonly CURRENT_FILING_STATUS_CANNOT_HAVE_ENDING_DATE: {
|
|
87
|
+
readonly message: "The current Sub/Parent status cannot have an end date. Please remove the end date for this state.";
|
|
88
|
+
readonly affectedFields: readonly ["filingStatusEndingDate"];
|
|
89
|
+
};
|
|
90
|
+
};
|
|
91
|
+
//# sourceMappingURL=client-records-filing-statuses-histories.validation-messages.d.ts.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"client-records-filing-statuses-histories.validation-messages.d.ts","sourceRoot":"","sources":["../../../src/validation/features/client-records-filing-statuses-histories.validation-messages.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,8BAA8B;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyFjC,CAAC"}
|
package/dist/validation/features/client-records-filing-statuses-histories.validation-messages.js
ADDED
|
@@ -0,0 +1,93 @@
|
|
|
1
|
+
"use strict";
|
|
2
|
+
Object.defineProperty(exports, "__esModule", { value: true });
|
|
3
|
+
exports.CLIENT_RECORDS_FILING_STATUSES = void 0;
|
|
4
|
+
exports.CLIENT_RECORDS_FILING_STATUSES = {
|
|
5
|
+
FILING_STATUS_ID_DOES_NOT_EXIST: {
|
|
6
|
+
message: `Sub/Parent status does not exist`,
|
|
7
|
+
params: ['id'],
|
|
8
|
+
affectedFields: ['filingStatus'],
|
|
9
|
+
},
|
|
10
|
+
FILING_STATUS_PARENT_REQUIRED: {
|
|
11
|
+
message: `Parent needs to be specified for filing status 'Files under parent'`,
|
|
12
|
+
affectedFields: ['currentParent'],
|
|
13
|
+
},
|
|
14
|
+
CURRENT_FILING_STATUS_PARENT_REQUIRED: {
|
|
15
|
+
message: `Parent needs to be specified for current filing status 'Files under parent'`,
|
|
16
|
+
affectedFields: ['currentParent'],
|
|
17
|
+
},
|
|
18
|
+
NOT_ALIGNED_DATE_ESTABLISHED_FILING_STATUS_STARTING_DATE: {
|
|
19
|
+
message: `The Sub/Parent status {filingStatus} starts on {filingStatusStartingDate} which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the Sub/Parent status or the client's date established.`,
|
|
20
|
+
params: ['clientDateEstablished', 'filingStatus', 'filingStatusStartingDate'],
|
|
21
|
+
affectedFields: ['dateEstablished', 'filingStatus'],
|
|
22
|
+
},
|
|
23
|
+
NOT_ALIGNED_CLOSE_DATE_FILING_STATUS_STARTING_DATE: {
|
|
24
|
+
message: `One or more Sub/Parent status have a start date which is after the client's close date of {clientCloseDate}. {filingStatus}, starting {filingStatusStartingDate}. Please update the start date to be earlier than the client's close date, or update the client's close date.`,
|
|
25
|
+
params: ['clientCloseDate', 'filingStatus', 'filingStatusStartingDate'],
|
|
26
|
+
affectedFields: ['closeDate', 'filingStatus'],
|
|
27
|
+
},
|
|
28
|
+
FILING_STATUS_STARTING_DATE_NOT_POPULATED: {
|
|
29
|
+
message: `Current Sub/Parent status Starting Date cannot be Empty`,
|
|
30
|
+
affectedFields: ['filingStatusStartingDate'],
|
|
31
|
+
},
|
|
32
|
+
NOT_ALIGNED_FILING_STATUS_STARTING_ENDING_DATE: {
|
|
33
|
+
message: `Sub/Parent status starting date needs to be before the ending date`,
|
|
34
|
+
affectedFields: ['filingStatusStartingDate', 'filingStatusEndingDate'],
|
|
35
|
+
},
|
|
36
|
+
FILING_STATUSES_IDS_DOES_NOT_EXIST: {
|
|
37
|
+
message: `Sub/Parent status do not exist`,
|
|
38
|
+
params: ['ids'],
|
|
39
|
+
affectedFields: ['filingStatus'],
|
|
40
|
+
},
|
|
41
|
+
AT_LEAST_ONE_FILING_STATUS_SHOULD_EXIST: {
|
|
42
|
+
message: `At least one Sub/Parent status should exist`,
|
|
43
|
+
affectedFields: ['filingStatus'],
|
|
44
|
+
},
|
|
45
|
+
FILING_STATUSES_STARTING_DATE_NOT_POPULATED: {
|
|
46
|
+
message: `Starting date for {filingStatus} cannot be empty`,
|
|
47
|
+
params: ['filingStatus'],
|
|
48
|
+
affectedFields: ['filingStatusStartingDate'],
|
|
49
|
+
},
|
|
50
|
+
NOT_ALIGNED_FILING_STATUSES_STARTING_ENDING_DATE: {
|
|
51
|
+
message: `The ending date for {filingStatus} must be after its starting date`,
|
|
52
|
+
params: ['filingStatus'],
|
|
53
|
+
affectedFields: ['filingStatusStartingDate', 'filingStatusEndingDate'],
|
|
54
|
+
},
|
|
55
|
+
NOT_ALIGNED_DATE_ESTABLISHED_FILING_STATUSES_STARTING_DATE: {
|
|
56
|
+
message: `Adjust the start date to be on or after the client's date established, {clientStartDate}.`,
|
|
57
|
+
params: ['clientStartDate'],
|
|
58
|
+
affectedFields: ['filingStatusStartingDate', 'dateEstablished'],
|
|
59
|
+
},
|
|
60
|
+
NOT_ALIGNED_CLOSE_DATE_FILING_STATUSES_STARTING_DATE: {
|
|
61
|
+
message: `Adjust the start date to be before the client's close date, {clientCloseDate}.`,
|
|
62
|
+
params: ['clientCloseDate'],
|
|
63
|
+
affectedFields: ['filingStatusStartingDate', 'closeDate'],
|
|
64
|
+
},
|
|
65
|
+
FILING_STATUSES_DATE_GAP_DETECTED: {
|
|
66
|
+
message: `There is a gap in the timeframes between {currentFilingStatus}, ending {currentFilingStatusEndDate}, and {nextFilingStatus}, starting {nextFilingStatusStartDate}. Please adjust the dates to fill this gap.`,
|
|
67
|
+
params: ['currentFilingStatus', 'currentFilingStatusEndDate', 'nextFilingStatus', 'nextFilingStatusStartDate'],
|
|
68
|
+
affectedFields: ['filingStatus'],
|
|
69
|
+
},
|
|
70
|
+
FILING_STATUSES_CONSECUTIVE_DUPLICATES_DETECTED: {
|
|
71
|
+
message: `There are two entries for {filingStatus} with timeframes that immediately follow each other. {filingStatus} ending {firstPeriodEnd}, and {filingStatus} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {filingStatus}. `,
|
|
72
|
+
params: ['filingStatus', 'firstPeriodStart', 'firstPeriodEnd', 'secondPeriodStart'],
|
|
73
|
+
affectedFields: ['filingStatus'],
|
|
74
|
+
},
|
|
75
|
+
FILING_STATUS_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
|
|
76
|
+
message: `There is a gap between the client's date established ({dateEstablished}) and the start date of {earliestFilingStatus} ({earliestFilingStatusStartDate}). Please ensure that the status of one Sub/Parent status matches the client's date established.`,
|
|
77
|
+
params: ['dateEstablished', 'earliestFilingStatus', 'earliestFilingStatusStartDate'],
|
|
78
|
+
affectedFields: ['filingStatus', 'dateEstablished'],
|
|
79
|
+
},
|
|
80
|
+
FILING_STATUSES_DATES_OVERLAP: {
|
|
81
|
+
message: `The client already has {filingStatus} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.`,
|
|
82
|
+
params: ['filingStatus', 'startDate1', 'endDate1', 'startDate2', 'endDate2'],
|
|
83
|
+
affectedFields: ['filingStatus'],
|
|
84
|
+
},
|
|
85
|
+
ALL_NON_LAST_FILING_STATUSES_REQUIRE_ENDING_DATE: {
|
|
86
|
+
message: `Only the last Sub/Parent status can be open without an end date. Add an ending date to the existing Sub/Parent status before adding a start date for a new Sub/Parent status.`,
|
|
87
|
+
affectedFields: ['filingStatusEndingDate'],
|
|
88
|
+
},
|
|
89
|
+
CURRENT_FILING_STATUS_CANNOT_HAVE_ENDING_DATE: {
|
|
90
|
+
message: `The current Sub/Parent status cannot have an end date. Please remove the end date for this state.`,
|
|
91
|
+
affectedFields: ['filingStatusEndingDate'],
|
|
92
|
+
},
|
|
93
|
+
};
|
|
@@ -475,94 +475,94 @@ export declare const VALIDATION_MESSAGES: {
|
|
|
475
475
|
readonly affectedFields: readonly ["entityTypeEndingDate"];
|
|
476
476
|
};
|
|
477
477
|
};
|
|
478
|
-
readonly
|
|
479
|
-
readonly
|
|
478
|
+
readonly CLIENT_RECORDS_FILING_STATUSES: {
|
|
479
|
+
readonly FILING_STATUS_ID_DOES_NOT_EXIST: {
|
|
480
480
|
readonly message: "Sub/Parent status does not exist";
|
|
481
481
|
readonly params: readonly ["id"];
|
|
482
|
-
readonly affectedFields: readonly ["
|
|
482
|
+
readonly affectedFields: readonly ["filingStatus"];
|
|
483
483
|
};
|
|
484
|
-
readonly
|
|
485
|
-
readonly message: "Parent needs to be specified for filing
|
|
484
|
+
readonly FILING_STATUS_PARENT_REQUIRED: {
|
|
485
|
+
readonly message: "Parent needs to be specified for filing status 'Files under parent'";
|
|
486
486
|
readonly affectedFields: readonly ["currentParent"];
|
|
487
487
|
};
|
|
488
|
-
readonly
|
|
489
|
-
readonly message: "Parent needs to be specified for current filing
|
|
488
|
+
readonly CURRENT_FILING_STATUS_PARENT_REQUIRED: {
|
|
489
|
+
readonly message: "Parent needs to be specified for current filing status 'Files under parent'";
|
|
490
490
|
readonly affectedFields: readonly ["currentParent"];
|
|
491
491
|
};
|
|
492
|
-
readonly
|
|
493
|
-
readonly message: "The Sub/Parent status {
|
|
494
|
-
readonly params: readonly ["clientDateEstablished", "
|
|
495
|
-
readonly affectedFields: readonly ["dateEstablished", "
|
|
492
|
+
readonly NOT_ALIGNED_DATE_ESTABLISHED_FILING_STATUS_STARTING_DATE: {
|
|
493
|
+
readonly message: "The Sub/Parent status {filingStatus} starts on {filingStatusStartingDate} which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the Sub/Parent status or the client's date established.";
|
|
494
|
+
readonly params: readonly ["clientDateEstablished", "filingStatus", "filingStatusStartingDate"];
|
|
495
|
+
readonly affectedFields: readonly ["dateEstablished", "filingStatus"];
|
|
496
496
|
};
|
|
497
|
-
readonly
|
|
498
|
-
readonly message: "One or more Sub/Parent status have a start date which is after the client's close date of {clientCloseDate}. {
|
|
499
|
-
readonly params: readonly ["clientCloseDate", "
|
|
500
|
-
readonly affectedFields: readonly ["closeDate", "
|
|
497
|
+
readonly NOT_ALIGNED_CLOSE_DATE_FILING_STATUS_STARTING_DATE: {
|
|
498
|
+
readonly message: "One or more Sub/Parent status have a start date which is after the client's close date of {clientCloseDate}. {filingStatus}, starting {filingStatusStartingDate}. Please update the start date to be earlier than the client's close date, or update the client's close date.";
|
|
499
|
+
readonly params: readonly ["clientCloseDate", "filingStatus", "filingStatusStartingDate"];
|
|
500
|
+
readonly affectedFields: readonly ["closeDate", "filingStatus"];
|
|
501
501
|
};
|
|
502
|
-
readonly
|
|
502
|
+
readonly FILING_STATUS_STARTING_DATE_NOT_POPULATED: {
|
|
503
503
|
readonly message: "Current Sub/Parent status Starting Date cannot be Empty";
|
|
504
|
-
readonly affectedFields: readonly ["
|
|
504
|
+
readonly affectedFields: readonly ["filingStatusStartingDate"];
|
|
505
505
|
};
|
|
506
|
-
readonly
|
|
506
|
+
readonly NOT_ALIGNED_FILING_STATUS_STARTING_ENDING_DATE: {
|
|
507
507
|
readonly message: "Sub/Parent status starting date needs to be before the ending date";
|
|
508
|
-
readonly affectedFields: readonly ["
|
|
508
|
+
readonly affectedFields: readonly ["filingStatusStartingDate", "filingStatusEndingDate"];
|
|
509
509
|
};
|
|
510
|
-
readonly
|
|
510
|
+
readonly FILING_STATUSES_IDS_DOES_NOT_EXIST: {
|
|
511
511
|
readonly message: "Sub/Parent status do not exist";
|
|
512
512
|
readonly params: readonly ["ids"];
|
|
513
|
-
readonly affectedFields: readonly ["
|
|
513
|
+
readonly affectedFields: readonly ["filingStatus"];
|
|
514
514
|
};
|
|
515
|
-
readonly
|
|
515
|
+
readonly AT_LEAST_ONE_FILING_STATUS_SHOULD_EXIST: {
|
|
516
516
|
readonly message: "At least one Sub/Parent status should exist";
|
|
517
|
-
readonly affectedFields: readonly ["
|
|
517
|
+
readonly affectedFields: readonly ["filingStatus"];
|
|
518
518
|
};
|
|
519
|
-
readonly
|
|
520
|
-
readonly message: "Starting date for {
|
|
521
|
-
readonly params: readonly ["
|
|
522
|
-
readonly affectedFields: readonly ["
|
|
519
|
+
readonly FILING_STATUSES_STARTING_DATE_NOT_POPULATED: {
|
|
520
|
+
readonly message: "Starting date for {filingStatus} cannot be empty";
|
|
521
|
+
readonly params: readonly ["filingStatus"];
|
|
522
|
+
readonly affectedFields: readonly ["filingStatusStartingDate"];
|
|
523
523
|
};
|
|
524
|
-
readonly
|
|
525
|
-
readonly message: "The ending date for {
|
|
526
|
-
readonly params: readonly ["
|
|
527
|
-
readonly affectedFields: readonly ["
|
|
524
|
+
readonly NOT_ALIGNED_FILING_STATUSES_STARTING_ENDING_DATE: {
|
|
525
|
+
readonly message: "The ending date for {filingStatus} must be after its starting date";
|
|
526
|
+
readonly params: readonly ["filingStatus"];
|
|
527
|
+
readonly affectedFields: readonly ["filingStatusStartingDate", "filingStatusEndingDate"];
|
|
528
528
|
};
|
|
529
|
-
readonly
|
|
529
|
+
readonly NOT_ALIGNED_DATE_ESTABLISHED_FILING_STATUSES_STARTING_DATE: {
|
|
530
530
|
readonly message: "Adjust the start date to be on or after the client's date established, {clientStartDate}.";
|
|
531
531
|
readonly params: readonly ["clientStartDate"];
|
|
532
|
-
readonly affectedFields: readonly ["
|
|
532
|
+
readonly affectedFields: readonly ["filingStatusStartingDate", "dateEstablished"];
|
|
533
533
|
};
|
|
534
|
-
readonly
|
|
534
|
+
readonly NOT_ALIGNED_CLOSE_DATE_FILING_STATUSES_STARTING_DATE: {
|
|
535
535
|
readonly message: "Adjust the start date to be before the client's close date, {clientCloseDate}.";
|
|
536
536
|
readonly params: readonly ["clientCloseDate"];
|
|
537
|
-
readonly affectedFields: readonly ["
|
|
537
|
+
readonly affectedFields: readonly ["filingStatusStartingDate", "closeDate"];
|
|
538
538
|
};
|
|
539
|
-
readonly
|
|
540
|
-
readonly message: "There is a gap in the timeframes between {
|
|
541
|
-
readonly params: readonly ["
|
|
542
|
-
readonly affectedFields: readonly ["
|
|
539
|
+
readonly FILING_STATUSES_DATE_GAP_DETECTED: {
|
|
540
|
+
readonly message: "There is a gap in the timeframes between {currentFilingStatus}, ending {currentFilingStatusEndDate}, and {nextFilingStatus}, starting {nextFilingStatusStartDate}. Please adjust the dates to fill this gap.";
|
|
541
|
+
readonly params: readonly ["currentFilingStatus", "currentFilingStatusEndDate", "nextFilingStatus", "nextFilingStatusStartDate"];
|
|
542
|
+
readonly affectedFields: readonly ["filingStatus"];
|
|
543
543
|
};
|
|
544
|
-
readonly
|
|
545
|
-
readonly message: "There are two entries for {
|
|
546
|
-
readonly params: readonly ["
|
|
547
|
-
readonly affectedFields: readonly ["
|
|
544
|
+
readonly FILING_STATUSES_CONSECUTIVE_DUPLICATES_DETECTED: {
|
|
545
|
+
readonly message: "There are two entries for {filingStatus} with timeframes that immediately follow each other. {filingStatus} ending {firstPeriodEnd}, and {filingStatus} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {filingStatus}. ";
|
|
546
|
+
readonly params: readonly ["filingStatus", "firstPeriodStart", "firstPeriodEnd", "secondPeriodStart"];
|
|
547
|
+
readonly affectedFields: readonly ["filingStatus"];
|
|
548
548
|
};
|
|
549
|
-
readonly
|
|
550
|
-
readonly message: "There is a gap between the client's date established ({dateEstablished}) and the start of
|
|
551
|
-
readonly params: readonly ["dateEstablished", "
|
|
552
|
-
readonly affectedFields: readonly ["
|
|
549
|
+
readonly FILING_STATUS_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
|
|
550
|
+
readonly message: "There is a gap between the client's date established ({dateEstablished}) and the start date of {earliestFilingStatus} ({earliestFilingStatusStartDate}). Please ensure that the status of one Sub/Parent status matches the client's date established.";
|
|
551
|
+
readonly params: readonly ["dateEstablished", "earliestFilingStatus", "earliestFilingStatusStartDate"];
|
|
552
|
+
readonly affectedFields: readonly ["filingStatus", "dateEstablished"];
|
|
553
553
|
};
|
|
554
|
-
readonly
|
|
555
|
-
readonly message: "The client already has {
|
|
556
|
-
readonly params: readonly ["
|
|
557
|
-
readonly affectedFields: readonly ["
|
|
554
|
+
readonly FILING_STATUSES_DATES_OVERLAP: {
|
|
555
|
+
readonly message: "The client already has {filingStatus} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.";
|
|
556
|
+
readonly params: readonly ["filingStatus", "startDate1", "endDate1", "startDate2", "endDate2"];
|
|
557
|
+
readonly affectedFields: readonly ["filingStatus"];
|
|
558
558
|
};
|
|
559
|
-
readonly
|
|
559
|
+
readonly ALL_NON_LAST_FILING_STATUSES_REQUIRE_ENDING_DATE: {
|
|
560
560
|
readonly message: "Only the last Sub/Parent status can be open without an end date. Add an ending date to the existing Sub/Parent status before adding a start date for a new Sub/Parent status.";
|
|
561
|
-
readonly affectedFields: readonly ["
|
|
561
|
+
readonly affectedFields: readonly ["filingStatusEndingDate"];
|
|
562
562
|
};
|
|
563
|
-
readonly
|
|
563
|
+
readonly CURRENT_FILING_STATUS_CANNOT_HAVE_ENDING_DATE: {
|
|
564
564
|
readonly message: "The current Sub/Parent status cannot have an end date. Please remove the end date for this state.";
|
|
565
|
-
readonly affectedFields: readonly ["
|
|
565
|
+
readonly affectedFields: readonly ["filingStatusEndingDate"];
|
|
566
566
|
};
|
|
567
567
|
};
|
|
568
568
|
readonly CLIENT_RECORDS_ENTITY_STATES: {
|
|
@@ -11,7 +11,7 @@ const client_records_contacts_validation_messages_1 = require("./features/client
|
|
|
11
11
|
const client_records_commission_details_validation_messages_1 = require("./features/client-records-commission-details.validation-messages");
|
|
12
12
|
const client_current_entity_statuses_validation_messages_1 = require("./features/client-current-entity-statuses.validation-messages");
|
|
13
13
|
const client_records_entity_types_histories_validation_messages_1 = require("./features/client-records-entity-types-histories.validation-messages");
|
|
14
|
-
const
|
|
14
|
+
const client_records_filing_statuses_histories_validation_messages_1 = require("./features/client-records-filing-statuses-histories.validation-messages");
|
|
15
15
|
const client_records_entity_states_histories_validation_messages_1 = require("./features/client-records-entity-states-histories.validation-messages");
|
|
16
16
|
const client_relationships_common_validation_messages_1 = require("./features/client-relationships-common.validation-messages");
|
|
17
17
|
const client_relationships_owners_validation_messages_1 = require("./features/client-relationships-owners.validation-messages");
|
|
@@ -37,7 +37,7 @@ exports.VALIDATION_MESSAGES = {
|
|
|
37
37
|
CLIENT_RECORDS_COMMISSION_DETAILS: client_records_commission_details_validation_messages_1.CLIENT_RECORDS_COMMISSION_DETAILS,
|
|
38
38
|
CLIENT_CURRENT_ENTITY_STATUS: client_current_entity_statuses_validation_messages_1.CLIENT_CURRENT_ENTITY_STATUS,
|
|
39
39
|
CLIENT_RECORDS_ENTITY_TYPES: client_records_entity_types_histories_validation_messages_1.CLIENT_RECORDS_ENTITY_TYPES,
|
|
40
|
-
|
|
40
|
+
CLIENT_RECORDS_FILING_STATUSES: client_records_filing_statuses_histories_validation_messages_1.CLIENT_RECORDS_FILING_STATUSES,
|
|
41
41
|
CLIENT_RECORDS_ENTITY_STATES: client_records_entity_states_histories_validation_messages_1.CLIENT_RECORDS_ENTITY_STATES,
|
|
42
42
|
CLIENT_RELATIONSHIPS_COMMON: client_relationships_common_validation_messages_1.CLIENT_RELATIONSHIPS_COMMON,
|
|
43
43
|
CLIENT_RELATIONSHIPS_OWNERS: client_relationships_owners_validation_messages_1.CLIENT_RELATIONSHIPS_OWNERS,
|
package/package.json
CHANGED
package/src/validation/features/client-records-filing-statuses-histories.validation-messages.ts
ADDED
|
@@ -0,0 +1,90 @@
|
|
|
1
|
+
export const CLIENT_RECORDS_FILING_STATUSES = {
|
|
2
|
+
FILING_STATUS_ID_DOES_NOT_EXIST: {
|
|
3
|
+
message: `Sub/Parent status does not exist`,
|
|
4
|
+
params: ['id'],
|
|
5
|
+
affectedFields: ['filingStatus'],
|
|
6
|
+
},
|
|
7
|
+
FILING_STATUS_PARENT_REQUIRED: {
|
|
8
|
+
message: `Parent needs to be specified for filing status 'Files under parent'`,
|
|
9
|
+
affectedFields: ['currentParent'],
|
|
10
|
+
},
|
|
11
|
+
CURRENT_FILING_STATUS_PARENT_REQUIRED: {
|
|
12
|
+
message: `Parent needs to be specified for current filing status 'Files under parent'`,
|
|
13
|
+
affectedFields: ['currentParent'],
|
|
14
|
+
},
|
|
15
|
+
NOT_ALIGNED_DATE_ESTABLISHED_FILING_STATUS_STARTING_DATE: {
|
|
16
|
+
message: `The Sub/Parent status {filingStatus} starts on {filingStatusStartingDate} which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the Sub/Parent status or the client's date established.`,
|
|
17
|
+
params: ['clientDateEstablished', 'filingStatus', 'filingStatusStartingDate'],
|
|
18
|
+
affectedFields: ['dateEstablished', 'filingStatus'],
|
|
19
|
+
},
|
|
20
|
+
NOT_ALIGNED_CLOSE_DATE_FILING_STATUS_STARTING_DATE: {
|
|
21
|
+
message: `One or more Sub/Parent status have a start date which is after the client's close date of {clientCloseDate}. {filingStatus}, starting {filingStatusStartingDate}. Please update the start date to be earlier than the client's close date, or update the client's close date.`,
|
|
22
|
+
params: ['clientCloseDate', 'filingStatus', 'filingStatusStartingDate'],
|
|
23
|
+
affectedFields: ['closeDate', 'filingStatus'],
|
|
24
|
+
},
|
|
25
|
+
FILING_STATUS_STARTING_DATE_NOT_POPULATED: {
|
|
26
|
+
message: `Current Sub/Parent status Starting Date cannot be Empty`,
|
|
27
|
+
affectedFields: ['filingStatusStartingDate'],
|
|
28
|
+
},
|
|
29
|
+
NOT_ALIGNED_FILING_STATUS_STARTING_ENDING_DATE: {
|
|
30
|
+
message: `Sub/Parent status starting date needs to be before the ending date`,
|
|
31
|
+
affectedFields: ['filingStatusStartingDate', 'filingStatusEndingDate'],
|
|
32
|
+
},
|
|
33
|
+
FILING_STATUSES_IDS_DOES_NOT_EXIST: {
|
|
34
|
+
message: `Sub/Parent status do not exist`,
|
|
35
|
+
params: ['ids'],
|
|
36
|
+
affectedFields: ['filingStatus'],
|
|
37
|
+
},
|
|
38
|
+
AT_LEAST_ONE_FILING_STATUS_SHOULD_EXIST: {
|
|
39
|
+
message: `At least one Sub/Parent status should exist`,
|
|
40
|
+
affectedFields: ['filingStatus'],
|
|
41
|
+
},
|
|
42
|
+
FILING_STATUSES_STARTING_DATE_NOT_POPULATED: {
|
|
43
|
+
message: `Starting date for {filingStatus} cannot be empty`,
|
|
44
|
+
params: ['filingStatus'],
|
|
45
|
+
affectedFields: ['filingStatusStartingDate'],
|
|
46
|
+
},
|
|
47
|
+
NOT_ALIGNED_FILING_STATUSES_STARTING_ENDING_DATE: {
|
|
48
|
+
message: `The ending date for {filingStatus} must be after its starting date`,
|
|
49
|
+
params: ['filingStatus'],
|
|
50
|
+
affectedFields: ['filingStatusStartingDate', 'filingStatusEndingDate'],
|
|
51
|
+
},
|
|
52
|
+
NOT_ALIGNED_DATE_ESTABLISHED_FILING_STATUSES_STARTING_DATE: {
|
|
53
|
+
message: `Adjust the start date to be on or after the client's date established, {clientStartDate}.`,
|
|
54
|
+
params: ['clientStartDate'],
|
|
55
|
+
affectedFields: ['filingStatusStartingDate', 'dateEstablished'],
|
|
56
|
+
},
|
|
57
|
+
NOT_ALIGNED_CLOSE_DATE_FILING_STATUSES_STARTING_DATE: {
|
|
58
|
+
message: `Adjust the start date to be before the client's close date, {clientCloseDate}.`,
|
|
59
|
+
params: ['clientCloseDate'],
|
|
60
|
+
affectedFields: ['filingStatusStartingDate', 'closeDate'],
|
|
61
|
+
},
|
|
62
|
+
FILING_STATUSES_DATE_GAP_DETECTED: {
|
|
63
|
+
message: `There is a gap in the timeframes between {currentFilingStatus}, ending {currentFilingStatusEndDate}, and {nextFilingStatus}, starting {nextFilingStatusStartDate}. Please adjust the dates to fill this gap.`,
|
|
64
|
+
params: ['currentFilingStatus', 'currentFilingStatusEndDate', 'nextFilingStatus', 'nextFilingStatusStartDate'],
|
|
65
|
+
affectedFields: ['filingStatus'],
|
|
66
|
+
},
|
|
67
|
+
FILING_STATUSES_CONSECUTIVE_DUPLICATES_DETECTED: {
|
|
68
|
+
message: `There are two entries for {filingStatus} with timeframes that immediately follow each other. {filingStatus} ending {firstPeriodEnd}, and {filingStatus} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {filingStatus}. `,
|
|
69
|
+
params: ['filingStatus', 'firstPeriodStart', 'firstPeriodEnd', 'secondPeriodStart'],
|
|
70
|
+
affectedFields: ['filingStatus'],
|
|
71
|
+
},
|
|
72
|
+
FILING_STATUS_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
|
|
73
|
+
message: `There is a gap between the client's date established ({dateEstablished}) and the start date of {earliestFilingStatus} ({earliestFilingStatusStartDate}). Please ensure that the status of one Sub/Parent status matches the client's date established.`,
|
|
74
|
+
params: ['dateEstablished', 'earliestFilingStatus', 'earliestFilingStatusStartDate'],
|
|
75
|
+
affectedFields: ['filingStatus', 'dateEstablished'],
|
|
76
|
+
},
|
|
77
|
+
FILING_STATUSES_DATES_OVERLAP: {
|
|
78
|
+
message: `The client already has {filingStatus} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.`,
|
|
79
|
+
params: ['filingStatus', 'startDate1', 'endDate1', 'startDate2', 'endDate2'],
|
|
80
|
+
affectedFields: ['filingStatus'],
|
|
81
|
+
},
|
|
82
|
+
ALL_NON_LAST_FILING_STATUSES_REQUIRE_ENDING_DATE: {
|
|
83
|
+
message: `Only the last Sub/Parent status can be open without an end date. Add an ending date to the existing Sub/Parent status before adding a start date for a new Sub/Parent status.`,
|
|
84
|
+
affectedFields: ['filingStatusEndingDate'],
|
|
85
|
+
},
|
|
86
|
+
CURRENT_FILING_STATUS_CANNOT_HAVE_ENDING_DATE: {
|
|
87
|
+
message: `The current Sub/Parent status cannot have an end date. Please remove the end date for this state.`,
|
|
88
|
+
affectedFields: ['filingStatusEndingDate'],
|
|
89
|
+
},
|
|
90
|
+
} as const;
|
|
@@ -8,7 +8,7 @@ import { CLIENT_RECORDS_CONTACTS } from './features/client-records-contacts.vali
|
|
|
8
8
|
import { CLIENT_RECORDS_COMMISSION_DETAILS } from './features/client-records-commission-details.validation-messages';
|
|
9
9
|
import { CLIENT_CURRENT_ENTITY_STATUS } from './features/client-current-entity-statuses.validation-messages';
|
|
10
10
|
import { CLIENT_RECORDS_ENTITY_TYPES } from './features/client-records-entity-types-histories.validation-messages';
|
|
11
|
-
import {
|
|
11
|
+
import { CLIENT_RECORDS_FILING_STATUSES } from './features/client-records-filing-statuses-histories.validation-messages';
|
|
12
12
|
import { CLIENT_RECORDS_ENTITY_STATES } from './features/client-records-entity-states-histories.validation-messages';
|
|
13
13
|
import { CLIENT_RELATIONSHIPS_COMMON } from './features/client-relationships-common.validation-messages';
|
|
14
14
|
import { CLIENT_RELATIONSHIPS_OWNERS } from './features/client-relationships-owners.validation-messages';
|
|
@@ -35,7 +35,7 @@ export const VALIDATION_MESSAGES = {
|
|
|
35
35
|
CLIENT_RECORDS_COMMISSION_DETAILS,
|
|
36
36
|
CLIENT_CURRENT_ENTITY_STATUS,
|
|
37
37
|
CLIENT_RECORDS_ENTITY_TYPES,
|
|
38
|
-
|
|
38
|
+
CLIENT_RECORDS_FILING_STATUSES,
|
|
39
39
|
CLIENT_RECORDS_ENTITY_STATES,
|
|
40
40
|
CLIENT_RELATIONSHIPS_COMMON,
|
|
41
41
|
CLIENT_RELATIONSHIPS_OWNERS,
|
package/dist/validation/features/client-records-filing-types-histories.validation-messages.d.ts
DELETED
|
@@ -1,91 +0,0 @@
|
|
|
1
|
-
export declare const CLIENT_RECORDS_FILING_TYPES: {
|
|
2
|
-
readonly FILING_TYPE_ID_DOES_NOT_EXIST: {
|
|
3
|
-
readonly message: "Sub/Parent status does not exist";
|
|
4
|
-
readonly params: readonly ["id"];
|
|
5
|
-
readonly affectedFields: readonly ["filingType"];
|
|
6
|
-
};
|
|
7
|
-
readonly FILING_TYPE_PARENT_REQUIRED: {
|
|
8
|
-
readonly message: "Parent needs to be specified for filing type 'Files under parent'";
|
|
9
|
-
readonly affectedFields: readonly ["currentParent"];
|
|
10
|
-
};
|
|
11
|
-
readonly CURRENT_FILING_TYPE_PARENT_REQUIRED: {
|
|
12
|
-
readonly message: "Parent needs to be specified for current filing type 'Files under parent'";
|
|
13
|
-
readonly affectedFields: readonly ["currentParent"];
|
|
14
|
-
};
|
|
15
|
-
readonly NOT_ALIGNED_DATE_ESTABLISHED_FILING_TYPE_STARTING_DATE: {
|
|
16
|
-
readonly message: "The Sub/Parent status {filingType} starts on {filingTypeStartingDate} which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the Sub/Parent status or the client's date established.";
|
|
17
|
-
readonly params: readonly ["clientDateEstablished", "filingType", "filingTypeStartingDate"];
|
|
18
|
-
readonly affectedFields: readonly ["dateEstablished", "filingType"];
|
|
19
|
-
};
|
|
20
|
-
readonly NOT_ALIGNED_CLOSE_DATE_FILING_TYPE_STARTING_DATE: {
|
|
21
|
-
readonly message: "One or more Sub/Parent status have a start date which is after the client's close date of {clientCloseDate}. {filingType}, starting {filingTypeStartingDate}. Please update the start date to be earlier than the client's close date, or update the client's close date.";
|
|
22
|
-
readonly params: readonly ["clientCloseDate", "filingType", "filingTypeStartingDate"];
|
|
23
|
-
readonly affectedFields: readonly ["closeDate", "filingType"];
|
|
24
|
-
};
|
|
25
|
-
readonly FILING_TYPE_STARTING_DATE_NOT_POPULATED: {
|
|
26
|
-
readonly message: "Current Sub/Parent status Starting Date cannot be Empty";
|
|
27
|
-
readonly affectedFields: readonly ["filingTypeStartingDate"];
|
|
28
|
-
};
|
|
29
|
-
readonly NOT_ALIGNED_FILING_TYPE_STARTING_ENDING_DATE: {
|
|
30
|
-
readonly message: "Sub/Parent status starting date needs to be before the ending date";
|
|
31
|
-
readonly affectedFields: readonly ["filingTypeStartingDate", "filingTypeEndingDate"];
|
|
32
|
-
};
|
|
33
|
-
readonly FILING_TYPES_IDS_DOES_NOT_EXIST: {
|
|
34
|
-
readonly message: "Sub/Parent status do not exist";
|
|
35
|
-
readonly params: readonly ["ids"];
|
|
36
|
-
readonly affectedFields: readonly ["filingType"];
|
|
37
|
-
};
|
|
38
|
-
readonly AT_LEAST_ONE_FILING_TYPE_SHOULD_EXIST: {
|
|
39
|
-
readonly message: "At least one Sub/Parent status should exist";
|
|
40
|
-
readonly affectedFields: readonly ["filingType"];
|
|
41
|
-
};
|
|
42
|
-
readonly FILING_TYPES_STARTING_DATE_NOT_POPULATED: {
|
|
43
|
-
readonly message: "Starting date for {filingType} cannot be empty";
|
|
44
|
-
readonly params: readonly ["filingType"];
|
|
45
|
-
readonly affectedFields: readonly ["filingTypeStartingDate"];
|
|
46
|
-
};
|
|
47
|
-
readonly NOT_ALIGNED_FILING_TYPES_STARTING_ENDING_DATE: {
|
|
48
|
-
readonly message: "The ending date for {filingType} must be after its starting date";
|
|
49
|
-
readonly params: readonly ["filingType"];
|
|
50
|
-
readonly affectedFields: readonly ["filingTypeStartingDate", "filingTypeEndingDate"];
|
|
51
|
-
};
|
|
52
|
-
readonly NOT_ALIGNED_DATE_ESTABLISHED_FILING_TYPES_STARTING_DATE: {
|
|
53
|
-
readonly message: "Adjust the start date to be on or after the client's date established, {clientStartDate}.";
|
|
54
|
-
readonly params: readonly ["clientStartDate"];
|
|
55
|
-
readonly affectedFields: readonly ["filingTypeStartingDate", "dateEstablished"];
|
|
56
|
-
};
|
|
57
|
-
readonly NOT_ALIGNED_CLOSE_DATE_FILING_TYPES_STARTING_DATE: {
|
|
58
|
-
readonly message: "Adjust the start date to be before the client's close date, {clientCloseDate}.";
|
|
59
|
-
readonly params: readonly ["clientCloseDate"];
|
|
60
|
-
readonly affectedFields: readonly ["filingTypeStartingDate", "closeDate"];
|
|
61
|
-
};
|
|
62
|
-
readonly FILING_TYPES_DATE_GAP_DETECTED: {
|
|
63
|
-
readonly message: "There is a gap in the timeframes between {currentFilingType}, ending {currentFilingTypeEndDate}, and {nextFilingType}, starting {nextFilingTypeStartDate}. Please adjust the dates to fill this gap.";
|
|
64
|
-
readonly params: readonly ["currentFilingType", "currentFilingTypeEndDate", "nextFilingType", "nextFilingTypeStartDate"];
|
|
65
|
-
readonly affectedFields: readonly ["filingType"];
|
|
66
|
-
};
|
|
67
|
-
readonly FILING_TYPES_CONSECUTIVE_DUPLICATES_DETECTED: {
|
|
68
|
-
readonly message: "There are two entries for {filingType} with timeframes that immediately follow each other. {filingType} ending {firstPeriodEnd}, and {filingType} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {filingType}. ";
|
|
69
|
-
readonly params: readonly ["filingType", "firstPeriodStart", "firstPeriodEnd", "secondPeriodStart"];
|
|
70
|
-
readonly affectedFields: readonly ["filingType"];
|
|
71
|
-
};
|
|
72
|
-
readonly FILING_TYPE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
|
|
73
|
-
readonly message: "There is a gap between the client's date established ({dateEstablished}) and the start of its first Sub/Parent status ({earliestFilingType} starting {earliestFilingTypeStartDate}). Please ensure that the status of one sub/parent status matches the client's date established.";
|
|
74
|
-
readonly params: readonly ["dateEstablished", "earliestFilingType", "earliestFilingTypeStartDate"];
|
|
75
|
-
readonly affectedFields: readonly ["filingType", "dateEstablished"];
|
|
76
|
-
};
|
|
77
|
-
readonly FILING_TYPES_DATES_OVERLAP: {
|
|
78
|
-
readonly message: "The client already has {filingType} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.";
|
|
79
|
-
readonly params: readonly ["filingType", "startDate1", "endDate1", "startDate2", "endDate2"];
|
|
80
|
-
readonly affectedFields: readonly ["filingType"];
|
|
81
|
-
};
|
|
82
|
-
readonly ALL_NON_LAST_FILING_TYPES_REQUIRE_ENDING_DATE: {
|
|
83
|
-
readonly message: "Only the last Sub/Parent status can be open without an end date. Add an ending date to the existing Sub/Parent status before adding a start date for a new Sub/Parent status.";
|
|
84
|
-
readonly affectedFields: readonly ["filingTypeEndingDate"];
|
|
85
|
-
};
|
|
86
|
-
readonly CURRENT_FILING_TYPE_CANNOT_HAVE_ENDING_DATE: {
|
|
87
|
-
readonly message: "The current Sub/Parent status cannot have an end date. Please remove the end date for this state.";
|
|
88
|
-
readonly affectedFields: readonly ["filingTypeEndingDate"];
|
|
89
|
-
};
|
|
90
|
-
};
|
|
91
|
-
//# sourceMappingURL=client-records-filing-types-histories.validation-messages.d.ts.map
|
package/dist/validation/features/client-records-filing-types-histories.validation-messages.d.ts.map
DELETED
|
@@ -1 +0,0 @@
|
|
|
1
|
-
{"version":3,"file":"client-records-filing-types-histories.validation-messages.d.ts","sourceRoot":"","sources":["../../../src/validation/features/client-records-filing-types-histories.validation-messages.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,2BAA2B;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyF9B,CAAC"}
|
package/dist/validation/features/client-records-filing-types-histories.validation-messages.js
DELETED
|
@@ -1,93 +0,0 @@
|
|
|
1
|
-
"use strict";
|
|
2
|
-
Object.defineProperty(exports, "__esModule", { value: true });
|
|
3
|
-
exports.CLIENT_RECORDS_FILING_TYPES = void 0;
|
|
4
|
-
exports.CLIENT_RECORDS_FILING_TYPES = {
|
|
5
|
-
FILING_TYPE_ID_DOES_NOT_EXIST: {
|
|
6
|
-
message: `Sub/Parent status does not exist`,
|
|
7
|
-
params: ['id'],
|
|
8
|
-
affectedFields: ['filingType'],
|
|
9
|
-
},
|
|
10
|
-
FILING_TYPE_PARENT_REQUIRED: {
|
|
11
|
-
message: `Parent needs to be specified for filing type 'Files under parent'`,
|
|
12
|
-
affectedFields: ['currentParent'],
|
|
13
|
-
},
|
|
14
|
-
CURRENT_FILING_TYPE_PARENT_REQUIRED: {
|
|
15
|
-
message: `Parent needs to be specified for current filing type 'Files under parent'`,
|
|
16
|
-
affectedFields: ['currentParent'],
|
|
17
|
-
},
|
|
18
|
-
NOT_ALIGNED_DATE_ESTABLISHED_FILING_TYPE_STARTING_DATE: {
|
|
19
|
-
message: `The Sub/Parent status {filingType} starts on {filingTypeStartingDate} which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the Sub/Parent status or the client's date established.`,
|
|
20
|
-
params: ['clientDateEstablished', 'filingType', 'filingTypeStartingDate'],
|
|
21
|
-
affectedFields: ['dateEstablished', 'filingType'],
|
|
22
|
-
},
|
|
23
|
-
NOT_ALIGNED_CLOSE_DATE_FILING_TYPE_STARTING_DATE: {
|
|
24
|
-
message: `One or more Sub/Parent status have a start date which is after the client's close date of {clientCloseDate}. {filingType}, starting {filingTypeStartingDate}. Please update the start date to be earlier than the client's close date, or update the client's close date.`,
|
|
25
|
-
params: ['clientCloseDate', 'filingType', 'filingTypeStartingDate'],
|
|
26
|
-
affectedFields: ['closeDate', 'filingType'],
|
|
27
|
-
},
|
|
28
|
-
FILING_TYPE_STARTING_DATE_NOT_POPULATED: {
|
|
29
|
-
message: `Current Sub/Parent status Starting Date cannot be Empty`,
|
|
30
|
-
affectedFields: ['filingTypeStartingDate'],
|
|
31
|
-
},
|
|
32
|
-
NOT_ALIGNED_FILING_TYPE_STARTING_ENDING_DATE: {
|
|
33
|
-
message: `Sub/Parent status starting date needs to be before the ending date`,
|
|
34
|
-
affectedFields: ['filingTypeStartingDate', 'filingTypeEndingDate'],
|
|
35
|
-
},
|
|
36
|
-
FILING_TYPES_IDS_DOES_NOT_EXIST: {
|
|
37
|
-
message: `Sub/Parent status do not exist`,
|
|
38
|
-
params: ['ids'],
|
|
39
|
-
affectedFields: ['filingType'],
|
|
40
|
-
},
|
|
41
|
-
AT_LEAST_ONE_FILING_TYPE_SHOULD_EXIST: {
|
|
42
|
-
message: `At least one Sub/Parent status should exist`,
|
|
43
|
-
affectedFields: ['filingType'],
|
|
44
|
-
},
|
|
45
|
-
FILING_TYPES_STARTING_DATE_NOT_POPULATED: {
|
|
46
|
-
message: `Starting date for {filingType} cannot be empty`,
|
|
47
|
-
params: ['filingType'],
|
|
48
|
-
affectedFields: ['filingTypeStartingDate'],
|
|
49
|
-
},
|
|
50
|
-
NOT_ALIGNED_FILING_TYPES_STARTING_ENDING_DATE: {
|
|
51
|
-
message: `The ending date for {filingType} must be after its starting date`,
|
|
52
|
-
params: ['filingType'],
|
|
53
|
-
affectedFields: ['filingTypeStartingDate', 'filingTypeEndingDate'],
|
|
54
|
-
},
|
|
55
|
-
NOT_ALIGNED_DATE_ESTABLISHED_FILING_TYPES_STARTING_DATE: {
|
|
56
|
-
message: `Adjust the start date to be on or after the client's date established, {clientStartDate}.`,
|
|
57
|
-
params: ['clientStartDate'],
|
|
58
|
-
affectedFields: ['filingTypeStartingDate', 'dateEstablished'],
|
|
59
|
-
},
|
|
60
|
-
NOT_ALIGNED_CLOSE_DATE_FILING_TYPES_STARTING_DATE: {
|
|
61
|
-
message: `Adjust the start date to be before the client's close date, {clientCloseDate}.`,
|
|
62
|
-
params: ['clientCloseDate'],
|
|
63
|
-
affectedFields: ['filingTypeStartingDate', 'closeDate'],
|
|
64
|
-
},
|
|
65
|
-
FILING_TYPES_DATE_GAP_DETECTED: {
|
|
66
|
-
message: `There is a gap in the timeframes between {currentFilingType}, ending {currentFilingTypeEndDate}, and {nextFilingType}, starting {nextFilingTypeStartDate}. Please adjust the dates to fill this gap.`,
|
|
67
|
-
params: ['currentFilingType', 'currentFilingTypeEndDate', 'nextFilingType', 'nextFilingTypeStartDate'],
|
|
68
|
-
affectedFields: ['filingType'],
|
|
69
|
-
},
|
|
70
|
-
FILING_TYPES_CONSECUTIVE_DUPLICATES_DETECTED: {
|
|
71
|
-
message: `There are two entries for {filingType} with timeframes that immediately follow each other. {filingType} ending {firstPeriodEnd}, and {filingType} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {filingType}. `,
|
|
72
|
-
params: ['filingType', 'firstPeriodStart', 'firstPeriodEnd', 'secondPeriodStart'],
|
|
73
|
-
affectedFields: ['filingType'],
|
|
74
|
-
},
|
|
75
|
-
FILING_TYPE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
|
|
76
|
-
message: `There is a gap between the client's date established ({dateEstablished}) and the start of its first Sub/Parent status ({earliestFilingType} starting {earliestFilingTypeStartDate}). Please ensure that the status of one sub/parent status matches the client's date established.`,
|
|
77
|
-
params: ['dateEstablished', 'earliestFilingType', 'earliestFilingTypeStartDate'],
|
|
78
|
-
affectedFields: ['filingType', 'dateEstablished'],
|
|
79
|
-
},
|
|
80
|
-
FILING_TYPES_DATES_OVERLAP: {
|
|
81
|
-
message: `The client already has {filingType} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.`,
|
|
82
|
-
params: ['filingType', 'startDate1', 'endDate1', 'startDate2', 'endDate2'],
|
|
83
|
-
affectedFields: ['filingType'],
|
|
84
|
-
},
|
|
85
|
-
ALL_NON_LAST_FILING_TYPES_REQUIRE_ENDING_DATE: {
|
|
86
|
-
message: `Only the last Sub/Parent status can be open without an end date. Add an ending date to the existing Sub/Parent status before adding a start date for a new Sub/Parent status.`,
|
|
87
|
-
affectedFields: ['filingTypeEndingDate'],
|
|
88
|
-
},
|
|
89
|
-
CURRENT_FILING_TYPE_CANNOT_HAVE_ENDING_DATE: {
|
|
90
|
-
message: `The current Sub/Parent status cannot have an end date. Please remove the end date for this state.`,
|
|
91
|
-
affectedFields: ['filingTypeEndingDate'],
|
|
92
|
-
},
|
|
93
|
-
};
|
package/src/validation/features/client-records-filing-types-histories.validation-messages.ts
DELETED
|
@@ -1,90 +0,0 @@
|
|
|
1
|
-
export const CLIENT_RECORDS_FILING_TYPES = {
|
|
2
|
-
FILING_TYPE_ID_DOES_NOT_EXIST: {
|
|
3
|
-
message: `Sub/Parent status does not exist`,
|
|
4
|
-
params: ['id'],
|
|
5
|
-
affectedFields: ['filingType'],
|
|
6
|
-
},
|
|
7
|
-
FILING_TYPE_PARENT_REQUIRED: {
|
|
8
|
-
message: `Parent needs to be specified for filing type 'Files under parent'`,
|
|
9
|
-
affectedFields: ['currentParent'],
|
|
10
|
-
},
|
|
11
|
-
CURRENT_FILING_TYPE_PARENT_REQUIRED: {
|
|
12
|
-
message: `Parent needs to be specified for current filing type 'Files under parent'`,
|
|
13
|
-
affectedFields: ['currentParent'],
|
|
14
|
-
},
|
|
15
|
-
NOT_ALIGNED_DATE_ESTABLISHED_FILING_TYPE_STARTING_DATE: {
|
|
16
|
-
message: `The Sub/Parent status {filingType} starts on {filingTypeStartingDate} which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the Sub/Parent status or the client's date established.`,
|
|
17
|
-
params: ['clientDateEstablished', 'filingType', 'filingTypeStartingDate'],
|
|
18
|
-
affectedFields: ['dateEstablished', 'filingType'],
|
|
19
|
-
},
|
|
20
|
-
NOT_ALIGNED_CLOSE_DATE_FILING_TYPE_STARTING_DATE: {
|
|
21
|
-
message: `One or more Sub/Parent status have a start date which is after the client's close date of {clientCloseDate}. {filingType}, starting {filingTypeStartingDate}. Please update the start date to be earlier than the client's close date, or update the client's close date.`,
|
|
22
|
-
params: ['clientCloseDate', 'filingType', 'filingTypeStartingDate'],
|
|
23
|
-
affectedFields: ['closeDate', 'filingType'],
|
|
24
|
-
},
|
|
25
|
-
FILING_TYPE_STARTING_DATE_NOT_POPULATED: {
|
|
26
|
-
message: `Current Sub/Parent status Starting Date cannot be Empty`,
|
|
27
|
-
affectedFields: ['filingTypeStartingDate'],
|
|
28
|
-
},
|
|
29
|
-
NOT_ALIGNED_FILING_TYPE_STARTING_ENDING_DATE: {
|
|
30
|
-
message: `Sub/Parent status starting date needs to be before the ending date`,
|
|
31
|
-
affectedFields: ['filingTypeStartingDate', 'filingTypeEndingDate'],
|
|
32
|
-
},
|
|
33
|
-
FILING_TYPES_IDS_DOES_NOT_EXIST: {
|
|
34
|
-
message: `Sub/Parent status do not exist`,
|
|
35
|
-
params: ['ids'],
|
|
36
|
-
affectedFields: ['filingType'],
|
|
37
|
-
},
|
|
38
|
-
AT_LEAST_ONE_FILING_TYPE_SHOULD_EXIST: {
|
|
39
|
-
message: `At least one Sub/Parent status should exist`,
|
|
40
|
-
affectedFields: ['filingType'],
|
|
41
|
-
},
|
|
42
|
-
FILING_TYPES_STARTING_DATE_NOT_POPULATED: {
|
|
43
|
-
message: `Starting date for {filingType} cannot be empty`,
|
|
44
|
-
params: ['filingType'],
|
|
45
|
-
affectedFields: ['filingTypeStartingDate'],
|
|
46
|
-
},
|
|
47
|
-
NOT_ALIGNED_FILING_TYPES_STARTING_ENDING_DATE: {
|
|
48
|
-
message: `The ending date for {filingType} must be after its starting date`,
|
|
49
|
-
params: ['filingType'],
|
|
50
|
-
affectedFields: ['filingTypeStartingDate', 'filingTypeEndingDate'],
|
|
51
|
-
},
|
|
52
|
-
NOT_ALIGNED_DATE_ESTABLISHED_FILING_TYPES_STARTING_DATE: {
|
|
53
|
-
message: `Adjust the start date to be on or after the client's date established, {clientStartDate}.`,
|
|
54
|
-
params: ['clientStartDate'],
|
|
55
|
-
affectedFields: ['filingTypeStartingDate', 'dateEstablished'],
|
|
56
|
-
},
|
|
57
|
-
NOT_ALIGNED_CLOSE_DATE_FILING_TYPES_STARTING_DATE: {
|
|
58
|
-
message: `Adjust the start date to be before the client's close date, {clientCloseDate}.`,
|
|
59
|
-
params: ['clientCloseDate'],
|
|
60
|
-
affectedFields: ['filingTypeStartingDate', 'closeDate'],
|
|
61
|
-
},
|
|
62
|
-
FILING_TYPES_DATE_GAP_DETECTED: {
|
|
63
|
-
message: `There is a gap in the timeframes between {currentFilingType}, ending {currentFilingTypeEndDate}, and {nextFilingType}, starting {nextFilingTypeStartDate}. Please adjust the dates to fill this gap.`,
|
|
64
|
-
params: ['currentFilingType', 'currentFilingTypeEndDate', 'nextFilingType', 'nextFilingTypeStartDate'],
|
|
65
|
-
affectedFields: ['filingType'],
|
|
66
|
-
},
|
|
67
|
-
FILING_TYPES_CONSECUTIVE_DUPLICATES_DETECTED: {
|
|
68
|
-
message: `There are two entries for {filingType} with timeframes that immediately follow each other. {filingType} ending {firstPeriodEnd}, and {filingType} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {filingType}. `,
|
|
69
|
-
params: ['filingType', 'firstPeriodStart', 'firstPeriodEnd', 'secondPeriodStart'],
|
|
70
|
-
affectedFields: ['filingType'],
|
|
71
|
-
},
|
|
72
|
-
FILING_TYPE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
|
|
73
|
-
message: `There is a gap between the client's date established ({dateEstablished}) and the start of its first Sub/Parent status ({earliestFilingType} starting {earliestFilingTypeStartDate}). Please ensure that the status of one sub/parent status matches the client's date established.`,
|
|
74
|
-
params: ['dateEstablished', 'earliestFilingType', 'earliestFilingTypeStartDate'],
|
|
75
|
-
affectedFields: ['filingType', 'dateEstablished'],
|
|
76
|
-
},
|
|
77
|
-
FILING_TYPES_DATES_OVERLAP: {
|
|
78
|
-
message: `The client already has {filingType} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.`,
|
|
79
|
-
params: ['filingType', 'startDate1', 'endDate1', 'startDate2', 'endDate2'],
|
|
80
|
-
affectedFields: ['filingType'],
|
|
81
|
-
},
|
|
82
|
-
ALL_NON_LAST_FILING_TYPES_REQUIRE_ENDING_DATE: {
|
|
83
|
-
message: `Only the last Sub/Parent status can be open without an end date. Add an ending date to the existing Sub/Parent status before adding a start date for a new Sub/Parent status.`,
|
|
84
|
-
affectedFields: ['filingTypeEndingDate'],
|
|
85
|
-
},
|
|
86
|
-
CURRENT_FILING_TYPE_CANNOT_HAVE_ENDING_DATE: {
|
|
87
|
-
message: `The current Sub/Parent status cannot have an end date. Please remove the end date for this state.`,
|
|
88
|
-
affectedFields: ['filingTypeEndingDate'],
|
|
89
|
-
},
|
|
90
|
-
} as const;
|