26
edits
No edit summary |
No edit summary |
||
Line 62: | Line 62: | ||
[[File:RequiredDocs.png|thumb|Flow Step - 1.5 ("RequiredDocs")]] | |||
Line 74: | Line 72: | ||
=== Second Block === | === Second Block === | ||
In the second block, we use the Get Records component get all the Document Submissions related to the Document Assignment that is associated with the triggering Document Submission record (use Flow Step - 1.6 below as a reference). We also use the Loop, the Decision, and the Assignment components to loop through each Document Submission record and to set Flow variables that determine if there are documents missing and calculate the Document Assignment completion percentage (use Flow Step - 1.7 to 1.11 as a reference). | In the second block, we use the Get Records component get all the Document Submissions related to the Document Assignment that is associated with the triggering Document Submission record (use Flow Step - 1.6 below as a reference). We also use the Loop, the Decision, and the Assignment components to loop through each Document Submission record and to set Flow variables that determine if there are documents missing and calculate the Document Assignment completion percentage (use Flow Step - 1.7 to 1.11 as a reference). | ||
Flow Step - 1.7 - "''loop Actual Submissions''” Loop Component - In this component, we loop through the submissions and count unique, non-rejected items. | Flow Step - 1.7 - "''loop Actual Submissions''” Loop Component - In this component, we loop through the submissions and count unique, non-rejected items. | ||
Line 87: | Line 81: | ||
Flow Step 1.9 ''- “Unique Status”'' Decision Component – In this component, we check if a Submission belonging to the same Document has already been processed. Note that we use a variable called “DocumentIds” in the check. The configuration of the “DocumentIds” variable can be found in Flow Step 1.12. | Flow Step 1.9 ''- “Unique Status”'' Decision Component – In this component, we check if a Submission belonging to the same Document has already been processed. Note that we use a variable called “DocumentIds” in the check. The configuration of the “DocumentIds” variable can be found in Flow Step 1.12. | ||
[[File:Screenshot 6 (“get Submissions” Get Records Component).png|thumb|Flow Step - 1.6 (“get Submissions” Get Records Component)]] | |||
Line 101: | Line 89: | ||
[[File:Screenshot 7 (“loop Actual Submissions” Loop Component).png|alt=|thumb|Flow Step - 1.7 (“loop Actual Submissions” Loop Component)]][[File:Screenshot 8 (“Submission Status” Decision Component ).png|thumb|Flow Step 1.8 (“Submission Status”) Decision Component]] | |||
Line 129: | Line 118: | ||
Flow Step 1.10 - “''Submission + 1”'' Assignment Component – In this component, we set two Flow variables i.e. “SubmissionCount” and “RequiredDocs”. The configuration of | |||
the “SubmissionCount” variable can be found in Flow Step 1.13 below. The configuration of the “RequiredDocs” variable was provided in Flow Step 1.5 above. Note also that we use a Formula variable - i.e. “OutstandingItems” - to set the “RequiredDocs” variable. The configuration of the “OutstandingItems” formula variable can be found in Flow Step 1.14 | |||
Flow Step 1.11 - (“''Unique Storage” Assignment Component'' – In this component, we store variables about the Document Submission to check uniqueness as we loop. The variables we use for storage in this component are “DocumentIds” and “RequiredDocs”. The configuration of the “DocumentIds” variable can be found in Flow Step 1.12 below; the configuration of the “RequiredDocs” variable can be found in Flow Step 1.5 above; and the configuration of the “OutstandingItems” formula variable can be found in Flow Step 1.14. Note also that we use a Formula variable - i.e. “DocumentId” - to set the “DocumentIds” variable. The configuration of the “DocumentId” formula variable can be found in Flow Step 1.15) | |||
[[File:Screenshot 12 (“DocumentIds” Variable).png|thumb|Flow Step 1.12 (“DocumentIds” Variable)]] | |||
Line 152: | Line 144: | ||
[[File:Screenshot 14 (“OutstandingItems” Variable).png|thumb|Flow Step 1.14 (“OutstandingItems” Variable)]] | [[File:Screenshot 14 (“OutstandingItems” Variable).png|thumb|Flow Step 1.14 (“OutstandingItems” Variable)]] | ||
Line 163: | Line 151: | ||
[[File:Screenshot 15 (“DocumentId” Variable).png|thumb|Flow Step 1.15 (“DocumentId” Variable)]] | [[File:Screenshot 15 (“DocumentId” Variable).png|thumb|Flow Step 1.15 (“DocumentId” Variable)]] | ||
Line 177: | Line 159: | ||
The fields that are updated in this component determine how complete is the Document Assignment. | The fields that are updated in this component determine how complete is the Document Assignment. | ||
[[File:Screenshot 16 (“Add Completeness” Update Records Component).png|thumb|Flow Step - 1.16 (“Add Completeness” Update Records Component)]] | [[File:Screenshot 16 (“Add Completeness” Update Records Component).png|thumb|Flow Step - 1.16 (“Add Completeness” Update Records Component)]] | ||
Flow Step 1.16 - (''“Add Completeness”'' Update Records Component) | Flow Step 1.16 - (''“Add Completeness”'' Update Records Component) | ||
Line 201: | Line 181: | ||
[[File:Screenshot 19 (“CompleteCalc” Variable).png|thumb|Flow Step - 1.19 (“CompleteCalc” Variable)]] | [[File:Screenshot 19 (“CompleteCalc” Variable).png|thumb|Flow Step - 1.19 (“CompleteCalc” Variable)]] | ||
edits