One-to-Many Data Collectors

[av_one_full first min_height=\’\’ vertical_alignment=\’av-align-top\’ space=\’\’ row_boxshadow_color=\’\’ row_boxshadow_width=\’10\’ custom_margin=\’aviaTBcustom_margin\’ margin=\’0px\’ margin_sync=\’true\’ mobile_breaking=\’\’ border=\’\’ border_color=\’\’ radius=\’0px\’ radius_sync=\’true\’ padding=\’0px\’ padding_sync=\’true\’ column_boxshadow_color=\’\’ column_boxshadow_width=\’10\’ background=\’bg_color\’ background_color=\’\’ background_gradient_color1=\’\’ background_gradient_color2=\’\’ background_gradient_direction=\’vertical\’ src=\’\’ attachment=\’\’ attachment_size=\’\’ background_position=\’top left\’ background_repeat=\’no-repeat\’ highlight_size=\’1.1\’ animation=\’\’ link=\’\’ linktarget=\’\’ link_hover=\’\’ title_attr=\’\’ alt_attr=\’\’ mobile_display=\’\’ id=\’\’ custom_class=\’\’ aria_label=\’\’ av_uid=\’av-1vrra\’]

[av_heading heading=\’One-to-Many (O2M) Data Collectors\’ tag=\’h1\’ link=\’\’ link_target=\’\’ style=\’blockquote modern-quote\’ size=\’\’ subheading_active=\’\’ subheading_size=\’\’ margin=\’5px\’ padding=\’10\’ icon_padding=\’10\’ color=\’custom-color-heading\’ custom_font=\’\’ icon_color=\’\’ show_icon=\’\’ icon=\’ue800\’ font=\’\’ icon_size=\’\’ custom_class=\’\’ id=\’\’ admin_preview_bg=\’\’ av-desktop-hide=\’\’ av-medium-hide=\’\’ av-small-hide=\’\’ av-mini-hide=\’\’ av-medium-font-size-title=\’\’ av-small-font-size-title=\’\’ av-mini-font-size-title=\’\’ av-medium-font-size=\’\’ av-small-font-size=\’\’ av-mini-font-size=\’\’ av-medium-font-size-1=\’\’ av-small-font-size-1=\’\’ av-mini-font-size-1=\’\’][/av_heading]

[av_hr class=\’custom\’ icon_select=\’no\’ icon=\’ue808\’ font=\’entypo-fontello\’ position=\’center\’ shadow=\’no-shadow\’ height=\’50\’ custom_border=\’av-border-thin\’ custom_width=\’100%\’ custom_margin_top=\’10px\’ custom_margin_bottom=\’10px\’ custom_border_color=\’\’ custom_icon_color=\’\’ id=\’\’ custom_class=\’\’ av_uid=\’av-3fbm\’ admin_preview_bg=\’\’]

[av_textblock size=\’\’ av-medium-font-size=\’\’ av-small-font-size=\’\’ av-mini-font-size=\’\’ font_color=\’\’ color=\’\’ id=\’\’ custom_class=\’\’ av_uid=\’av-k7n2xpvo\’ admin_preview_bg=\’\’]
A \’One-to-Many Data Collector\’ (O2M) differs from a standard Data Collector in that any \’Repeating Sections\’ become a separate record in \’View Data\’. This allows these separate records to be assigned to users for completion. Typically, One-to-Many Data Collectors where tasks are then assigned to different users.

When creating a \’One-to-Many Data Collector\’, select this option when creating your app.

$\"\"$
[/av_textblock]

[av_textblock size=\’\’ av-medium-font-size=\’\’ av-small-font-size=\’\’ av-mini-font-size=\’\’ font_color=\’\’ color=\’\’ id=\’\’ custom_class=\’\’ av_uid=\’av-ka00b6ed\’ admin_preview_bg=\’\’]
An overview of the features available to build a \’One-to-Many Data Collector app\’ are show below:
[/av_textblock]

[av_hr class=\’invisible\’ icon_select=\’yes\’ icon=\’ue808\’ font=\’entypo-fontello\’ position=\’center\’ shadow=\’no-shadow\’ height=\’20\’ custom_border=\’av-border-thin\’ custom_width=\’50px\’ custom_margin_top=\’30px\’ custom_margin_bottom=\’30px\’ custom_border_color=\’\’ custom_icon_color=\’\’ id=\’\’ custom_class=\’\’ av_uid=\’av-kk2dhujv\’ admin_preview_bg=\’\’]

[/av_one_full][av_one_full first min_height=\’av-equal-height-column\’ vertical_alignment=\’av-align-top\’ space=\’\’ row_boxshadow_color=\’\’ row_boxshadow_width=\’10\’ custom_margin=\’aviaTBcustom_margin\’ margin=\’0px,20px\’ mobile_breaking=\’\’ border=\’\’ border_color=\’\’ radius=\’0px\’ radius_sync=\’true\’ padding=\’0px\’ padding_sync=\’true\’ column_boxshadow_color=\’\’ column_boxshadow_width=\’10\’ background=\’bg_color\’ background_color=\’\’ background_gradient_color1=\’\’ background_gradient_color2=\’\’ background_gradient_direction=\’vertical\’ src=\’\’ attachment=\’\’ attachment_size=\’\’ background_position=\’top left\’ background_repeat=\’no-repeat\’ highlight_size=\’1.1\’ animation=\’\’ link=\’\’ linktarget=\’\’ link_hover=\’\’ title_attr=\’\’ alt_attr=\’\’ mobile_display=\’\’ id=\’\’ custom_class=\’\’ aria_label=\’\’ av_uid=\’av-llg45\’]
[av_heading heading=\’‘One-to-Many’ Data Collector Logic\’ tag=\’h3\’ link=\’\’ link_target=\’\’ style=\’blockquote modern-quote\’ size=\’\’ subheading_active=\’\’ subheading_size=\’\’ margin=\’\’ padding=\’10\’ icon_padding=\’10\’ color=\’\’ custom_font=\’\’ icon_color=\’\’ show_icon=\’\’ icon=\’ue800\’ font=\’\’ icon_size=\’\’ custom_class=\’\’ id=\’\’ admin_preview_bg=\’\’ av-desktop-hide=\’\’ av-medium-hide=\’\’ av-small-hide=\’\’ av-mini-hide=\’\’ av-medium-font-size-title=\’\’ av-small-font-size-title=\’\’ av-mini-font-size-title=\’\’ av-medium-font-size=\’\’ av-small-font-size=\’\’ av-mini-font-size=\’\’ av-medium-font-size-1=\’\’ av-small-font-size-1=\’\’ av-mini-font-size-1=\’\’ av_uid=\’av-28x28i\’][/av_heading]

[av_hr class=\’custom\’ icon_select=\’no\’ icon=\’ue808\’ font=\’entypo-fontello\’ position=\’left\’ shadow=\’no-shadow\’ height=\’50\’ custom_border=\’av-border-thin\’ custom_width=\’100%\’ custom_margin_top=\’0px\’ custom_margin_bottom=\’10px\’ custom_border_color=\’\’ custom_icon_color=\’\’ id=\’\’ custom_class=\’\’ av_uid=\’av-hftjh\’ admin_preview_bg=\’\’]

[av_toggle_container faq_markup=\’\’ initial=\’0\’ mode=\’accordion\’ sort=\’\’ styling=\’av-minimal-toggle\’ colors=\’\’ font_color=\’\’ background_color=\’\’ border_color=\’\’ colors_current=\’\’ font_color_current=\’\’ background_current=\’\’ background_color_current=\’\’ background_gradient_current_color1=\’\’ background_gradient_current_color2=\’\’ background_gradient_current_direction=\’vertical\’ hover_colors=\’\’ hover_background_color=\’\’ hover_font_color=\’\’ alb_description=\’\’ id=\’\’ custom_class=\’\’ av_uid=\’av-kk2dupc1\’]
[av_toggle title=\’Can contain multiple repeating sections\’ tags=\’\’ custom_id=\’\’ av_uid=\’av-9kpsya\’]
A One-to-Many (O2M) data collector can contain multiple repeating sections
[/av_toggle]
[av_toggle title=\’Assigning of Repeating Section Rows (RSR) to mobile user(s)\’ tags=\’\’ custom_id=\’\’ av_uid=\’av-25vbma\’]
When an RSR is assigned to a Mobile user (becomes P2M) it becomes ‘orphaned’ from the original submitted record (i.e. it becomes its own independent record, as if it had been added to the portal via an ‘Add Record’ routine). At this point any update made to the RSR, either by a portal user via ‘view’ or the mobile user who updates and returns the record, is contained within the RSR; there is no update to the original Mobile record. Any attempted updates / changes to data in the original Mobile submission are not applied to RSRs, which have had a P2M status applied to them.
[/av_toggle]
[av_toggle title=\’Allows updates from AppCan XP\’ tags=\’\’ custom_id=\’\’ av_uid=\’av-3w6c2q\’]
Updates can be made to the original submission on Mobile and submitted: \’Repeating Section Rows\’ (RSR), all update based upon this submission.

If none-repeating section fields are updated in the original submission then all RSRs in ‘View Data’ update too. The version number of each \’Repeating Section Rows\’ increments when an update is made.

If an update is made on Mobile within a repeating section then the relevant RSR updates in the portal – the version number for this \’Repeating Section Rows\’ increments.
[/av_toggle]
[av_toggle title=\’Allows adding more Repeating Sections in AppCan XP\’ tags=\’\’ custom_id=\’\’ av_uid=\’av-d2vzgy\’]
At any time Mobile users can add more repeating sections to the original record and re-submit. This action simply adds additional RSRs with the same unique ID to the ‘View Data’ grid.
[/av_toggle]
[av_toggle title=\’Shares the same ‘Unique Record ID’\’ tags=\’\’ custom_id=\’\’ av_uid=\’av-5ak1aa\’]
Each Repeating Section Row shares the same \’Unique Record ID\’ from the single record submitted. Each row repeats the data captured in the fields of non-repeating sections within the record (effectively this is ‘header’ data)
[/av_toggle]
[av_toggle title=\’Will display each repeating section in it‘s own row in ’View Data’\’ tags=\’\’ custom_id=\’\’ av_uid=\’av-850y7m\’]
On submission of an O2M data collector record, each repeating section is displayed in a ‘View Data’ grid on it’s own separate row.
[/av_toggle]
[av_toggle title=\’Allows Portal Updates\’ tags=\’\’ custom_id=\’\’ av_uid=\’av-375hiq\’]
Updates in the portal can be made to none repeating section fields for \’Repeating Section Rows\’ by clicking ‘view’ on any \’Repeating Section Rows\’ and editing, and confirming ‘update’. E.g. if you wanted to edit the ‘Project Ref No.’ In the header data you would click ‘view’ on any \’Repeating Section Rows\’, edit the field, and on ‘Update’ the ‘Project Ref No.’ for all linked (by unique ID) RSRs would have this update applied too. When this type of change is made the record on Mobile is updated with these changes.
[/av_toggle]
[av_toggle title=\’Allows portal updates to repeating section data\’ tags=\’\’ custom_id=\’\’ av_uid=\’av-eaof0i\’]
Updates in the portal can also be made to the repeating section data for any RSR. Click ‘view’ for an RSR, edit the repeating data field and confirm ‘Update’. The version number for this particular RSR updates. When this type of change is made the repeating section within the record on Mobile is updated with these changes too.
[/av_toggle]
[av_toggle title=\’Shows each Repeating Section data in individual rows in ‘View Data’\’ tags=\’\’ custom_id=\’\’ av_uid=\’av-8k0uxu\’]
The View Data grid for O2M data collectors will show rows for each repeated section; there will not be an option to switch to a view of the data where repeated sections are presented as repeated columns in the grid.
[/av_toggle]
[av_toggle title=\’Allows ‘View’ for each Repeating Section\’ tags=\’\’ custom_id=\’\’ av_uid=\’av-82pko2\’]
The view link in the view data grid for O2M data collector records will not show repeated sections; it will only show 1 instance of each section with the relevant field populated based on the selected RSR record.
[/av_toggle]
[av_toggle title=\’Allows deletion of Repeating Section Rows\’ tags=\’\’ custom_id=\’\’ av_uid=\’av-5zptb6\’]
RSR records can be deleted which will cause the record to not be visible in the view data grid. If the deletion happens to a record before it is orphaned via P2M the deleted record then it trigger a sync of the original mobile record which will see the repeated section being removed from the record. If the deletion happens after a P2M then this will lead to a sync of the RSR record which will show up as grey clouds on devices that hold a copy of the record. The original master record will not be updated as a result.
[/av_toggle]
[av_toggle title=\’Allows Mobile-to-Mobile (M2M) for individual records\’ tags=\’\’ custom_id=\’\’ av_uid=\’av-4kse82\’]
M2M for O2M data collectors will only apply to individual RSR records. The original master record on the mobile device cannot be forwarded via M2M.
[/av_toggle]
[av_toggle title=\’Prevents adding additional repeating sections for P2M records \’ tags=\’\’ custom_id=\’\’ av_uid=\’av-2tl8cy\’]
RSR records received on the mobile device after P2M will not have the option to add further repeated sections.
[/av_toggle]
[av_toggle title=\’Allows ‘Filing from Site’ for Repeating Section Rows\’ tags=\’\’ custom_id=\’\’ av_uid=\’av-d6wg36\’]
Filing from site will not be available on the master record. When creating a new record on the mobile device, the Publish In selection will never be presented for an O2M record. Filing from site can be allowed on individual RSR records and this is to work based on the current logic and that each RSR record is a submission in its own right.
[/av_toggle]
[av_toggle title=\’Allows ‘Data Collector Rules’ to be used\’ tags=\’\’ custom_id=\’\’ av_uid=\’av-aq0uwi\’]
In an O2M data collector, \’Data Collector Rules\’ can be setup for fields that are included in repeating section. The rules that are setup based on fields in repeating sections will only apply to RSR records on the mobile device. They will not have an impact on the original master record and for that these rules will be ignored.
[/av_toggle]
[av_toggle title=\’Allows for ‘New Record Notification’ schedules\’ tags=\’\’ custom_id=\’\’ av_uid=\’av-9rlkpe\’]
New record notifications via the scheduler can be setup for O2M data collectors however the setup is more restricted compared to regular data collectors. For O2M data collectors there will be no option to select a report and as a result the notifications will only support new records; there will be no notifications for updates to records. The notification email will not include a link to the records. The configuration for the email body will not include any fields contained in repeated sections.
[/av_toggle]
[av_toggle title=\’Allows single ‘Add Record’ to be used in ‘View Data’\’ tags=\’\’ custom_id=\’\’ av_uid=\’av-61mm5u\’]
New single RSR records can be added to a view data grid via the existing ‘Add Record’ functionality.
[/av_toggle]
[av_toggle title=\’Allows the use of ‘Back Office’ Fields\’ tags=\’\’ custom_id=\’\’ av_uid=\’av-4lboo2\’]
Back Office Fields can be added to a O2M data collector app and are visible in the RSR \’View Data\’ grid.
[/av_toggle]
[av_toggle title=\’Shows mobile user who submitted the original One-to-Many record\’ tags=\’\’ custom_id=\’\’ av_uid=\’av-375wya\’]
Mobile user column for v1 of each RSR record is populated with the name of the mobile user who has submitted the original O2M record.
[/av_toggle]
[av_toggle title=\’Allows ‘Report Builder’ reports to be built\’ tags=\’\’ custom_id=\’\’ av_uid=\’av-7u3042\’]
Report Builder will present fields in the data dictionary for RSR reports: only one set of repeating section data fields will be displayed for each repeating section within the O2M app. The RSRs all use the same single set of data fields presented in the data dictionary.
[/av_toggle]
[/av_toggle_container]
[/av_one_full]

AppCan Support