You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Collect needs to be able to support the new approvalEntityList media file type. If a media file has this type, it should behave like other entity lists, except that offline entities should not be created by registration forms. Offline updates should work as they do for any other entity list.
Acceptance
Given I have created a project on Central with entity registration and update forms
And the project uses the Accept/Reject workflow
When I use the project to fill out a registration form
And I finalize the form
Then the new entity is not available to update forms
Given I have created a project on Central with entity registration and update forms
And the project uses the Accept/Reject workflow
When I use the project to fill out an update form
And I finalize the form
Then the updated entity is available in the update form
Given I have created a project on Central with entity registration and update forms
And the project uses the Accept/Reject workflow
And Collect only has access to the registration form
When I use the project to fill out a registration form
And I finalize the form
And I grant Collect access to the update form
Then the new entity is not available in the update form
Questions
What do we do about the case where an app user only has access to registration forms and then has an update/follow-up form added later?
In this scenario, the entity should not be available to the follow-up form when it's added later.
How important is it that we have offline Entities created when there was no follow-up form show up in future follow-up forms?
The text was updated successfully, but these errors were encountered:
Blocked on Open Rosa spec
Collect needs to be able to support the new
approvalEntityList
media file type. If a media file has this type, it should behave like other entity lists, except that offline entities should not be created by registration forms. Offline updates should work as they do for any other entity list.Acceptance
Given I have created a project on Central with entity registration and update forms
And the project uses the Accept/Reject workflow
When I use the project to fill out a registration form
And I finalize the form
Then the new entity is not available to update forms
Given I have created a project on Central with entity registration and update forms
And the project uses the Accept/Reject workflow
When I use the project to fill out an update form
And I finalize the form
Then the updated entity is available in the update form
Given I have created a project on Central with entity registration and update forms
And the project uses the Accept/Reject workflow
And Collect only has access to the registration form
When I use the project to fill out a registration form
And I finalize the form
And I grant Collect access to the update form
Then the new entity is not available in the update form
Questions
What do we do about the case where an app user only has access to registration forms and then has an update/follow-up form added later?The text was updated successfully, but these errors were encountered: