@reqquest/ui 1.1.10 → 1.1.11

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.
@@ -285,7 +285,6 @@ type AppRequest {
285
285
  Date that this request was considered closed and no longer editable. If active or re-opened, will be null. If closed again, will be the second closure date.
286
286
  """
287
287
  closedAt: DateTime
288
- complete: Boolean!
289
288
  createdAt: DateTime!
290
289
 
291
290
  """
@@ -327,6 +326,11 @@ type AppRequest {
327
326
  """The period this appRequest is associated with."""
328
327
  period: Period!
329
328
 
329
+ """
330
+ The current phase of the app request. The phase generally only changes when control of the app request shifts between the applicant and reviewer.
331
+ """
332
+ phase: AppRequestPhase!
333
+
330
334
  """
331
335
  Retrieve a specific prompt by its ID. This is useful for the UI to get the full prompt data and configuration when trying to edit an individual prompt. We don't want to be downloading all the config data for everything up front.
332
336
  """
@@ -337,6 +341,11 @@ type AppRequest {
337
341
  The most pertinent status reason for this app request. The logic is complicated and depends on the AppRequest's status.
338
342
  """
339
343
  statusReason: String
344
+
345
+ """
346
+ The date that the applicant submitted their request. If the applicant has not yet submitted, this will be null.
347
+ """
348
+ submittedAt: DateTime
340
349
  updatedAt: DateTime!
341
350
  }
342
351
 
@@ -484,6 +493,11 @@ input AppRequestFilter {
484
493
  """
485
494
  closedBefore: DateTime
486
495
 
496
+ """
497
+ true -> only return appRequests that are complete (i.e. no more work to do, everything including nonblocking workflow is done). false -> only return appRequests that are not complete. null -> return all appRequests. Complete does not necessarily mean closed.
498
+ """
499
+ complete: Boolean
500
+
487
501
  """Only return appRequests that were created after this date."""
488
502
  createdAfter: DateTime
489
503
 
@@ -501,6 +515,11 @@ input AppRequestFilter {
501
515
  own: Boolean
502
516
  periodIds: [ID!]
503
517
 
518
+ """
519
+ Only return appRequests that have had their review started. true -> return review started, false -> return not started. Note that this is NOT mutually exclusive with complete or closed, it very simply means that a non-applicant has taken an action on it.
520
+ """
521
+ reviewStarted: Boolean
522
+
504
523
  """
505
524
  Search for appRequests that match this search term. This will do a prefix search across all fields that are indexed.
506
525
  """
@@ -602,6 +621,34 @@ input AppRequestNoteFilters {
602
621
  ids: [ID!]
603
622
  }
604
623
 
624
+ """
625
+ The current phase of the app request. The phase generally only changes when control of the app request shifts between the applicant and reviewer.
626
+ """
627
+ enum AppRequestPhase {
628
+ """
629
+ Reviewer has approved an offer and we are waiting for the applicant to accept. This phase is unreachable if the period has no ACCEPTANCE requirements.
630
+ """
631
+ ACCEPTANCE
632
+
633
+ """
634
+ All applications are complete and any non-blocking workflow is complete. The request is not necessarily closed, as that is an additional status, but nothing else needs be done to it.
635
+ """
636
+ COMPLETE
637
+
638
+ """Applicant has begun the process and has not yet submitted."""
639
+ STARTED
640
+
641
+ """
642
+ Applicant has submitted and we are waiting for reviewers to do their part.
643
+ """
644
+ SUBMITTED
645
+
646
+ """
647
+ The request has moved past ACCEPTANCE and is ready for each application to begin its non-blocking workflow. This phase is unreachable if the period has no non-blocking workflow stages.
648
+ """
649
+ WORKFLOW_NONBLOCKING
650
+ }
651
+
605
652
  "\n The status of an appRequest. This status is computed based on the \"dbStatus\" recorded in\n the database and the status of each application.\n "
606
653
  enum AppRequestStatus {
607
654
  """
@@ -1479,6 +1526,7 @@ type Query {
1479
1526
  This is where you get information about the authorization system. Each grant will be associated with one of these controlGroups, one or more controls in the group, and an optional set of tags. The tags are used to limit the scope of the grant.
1480
1527
  """
1481
1528
  controlGroups: [AccessControlGroup!]!
1529
+ countAppRequests(filter: AppRequestFilter): Int!
1482
1530
  pageInfo: PaginationResponse!
1483
1531
  periods(filter: PeriodFilters): [Period!]!
1484
1532
  programs(filter: ProgramFilters): [Program!]!
@@ -302,6 +302,13 @@ export const enumAppRequestIndexDestination = {
302
302
  LIST_FILTERS: 'LIST_FILTERS',
303
303
  REVIEWER_DASHBOARD: 'REVIEWER_DASHBOARD'
304
304
  };
305
+ export const enumAppRequestPhase = {
306
+ ACCEPTANCE: 'ACCEPTANCE',
307
+ COMPLETE: 'COMPLETE',
308
+ STARTED: 'STARTED',
309
+ SUBMITTED: 'SUBMITTED',
310
+ WORKFLOW_NONBLOCKING: 'WORKFLOW_NONBLOCKING'
311
+ };
305
312
  export const enumAppRequestStatus = {
306
313
  ACCEPTANCE: 'ACCEPTANCE',
307
314
  ACCEPTED: 'ACCEPTED',