Interesting problem!
Sure, this can be solved in a couple of ways, which for convenience I'll call...
A. Form Field method (easy)
B. Data Copy method (not so easy)
Here's how they'd each work. I'll explain them in the abstract, then depending on which you prefer, I'll can fluff out the details.
A. Form Field method
1. In each of your forms, add a new field called "In Review" or "Sent to Administrator", which is a radio button field with two values: "Yes" and "No".
2. Assign that new field to all Views in your forms so that your managers 1, 2 and 3 can change that value to "Yes" for the relevant submissions.
3. In each form, create a new View that's only visible to Manager 4. This View will contain a Standard Filter that ONLY shows those submissions that have "in review" set to "yes".
And that's it! Now, when the manager logs in they'll only see those submissions that have been "sent" from the other manager accounts.
Benefits: simple to set up.
Drawbacks: Manager 4 has to go to each form in turn to see the submissions that have been passed on by the other managers.
B. Data Copy method
This one's more work and a lot more complicated, but the end result from the viewpoint of Manager 4 may be better. This will aggregate all the submission data in a single form - a NEW form.
1. Create a new form with the fields you want to store that are shared across all the other forms (e.g. name, email etc) and add it to Form Tools for storage. You can then delete the form from your server - it won't be needed!
2. Install the Hooks Manager module.
3. Like the previous example, add a new "In Review" field to each of your forms (but NOT the new one you just created).
4. In the Hooks Manager, write a new rule for each form that's called whenever the form is updated. What it will do is copy over the relevant information into your new form.
To ensure that the information isn't copied over twice, we'll need to add a field to each of the original forms called "mapping_id" that will store the new submission ID in the "aggregate" form. When updating the original forms, the Hooks Manager rule will detect to see if this field has a value. If it doesn't, it will create a new record, otherwise it just updates the existing one.
5. Finally, assign the new form to Manager 4.
Benefits: shows all data in a single form for Manager 4.
Drawbacks: way more work to set up.
- Ben
Sure, this can be solved in a couple of ways, which for convenience I'll call...
A. Form Field method (easy)
B. Data Copy method (not so easy)
Here's how they'd each work. I'll explain them in the abstract, then depending on which you prefer, I'll can fluff out the details.
A. Form Field method
1. In each of your forms, add a new field called "In Review" or "Sent to Administrator", which is a radio button field with two values: "Yes" and "No".
2. Assign that new field to all Views in your forms so that your managers 1, 2 and 3 can change that value to "Yes" for the relevant submissions.
3. In each form, create a new View that's only visible to Manager 4. This View will contain a Standard Filter that ONLY shows those submissions that have "in review" set to "yes".
And that's it! Now, when the manager logs in they'll only see those submissions that have been "sent" from the other manager accounts.
Benefits: simple to set up.
Drawbacks: Manager 4 has to go to each form in turn to see the submissions that have been passed on by the other managers.
B. Data Copy method
This one's more work and a lot more complicated, but the end result from the viewpoint of Manager 4 may be better. This will aggregate all the submission data in a single form - a NEW form.
1. Create a new form with the fields you want to store that are shared across all the other forms (e.g. name, email etc) and add it to Form Tools for storage. You can then delete the form from your server - it won't be needed!
2. Install the Hooks Manager module.
3. Like the previous example, add a new "In Review" field to each of your forms (but NOT the new one you just created).
4. In the Hooks Manager, write a new rule for each form that's called whenever the form is updated. What it will do is copy over the relevant information into your new form.
To ensure that the information isn't copied over twice, we'll need to add a field to each of the original forms called "mapping_id" that will store the new submission ID in the "aggregate" form. When updating the original forms, the Hooks Manager rule will detect to see if this field has a value. If it doesn't, it will create a new record, otherwise it just updates the existing one.
5. Finally, assign the new form to Manager 4.
Benefits: shows all data in a single form for Manager 4.
Drawbacks: way more work to set up.
- Ben