4Industry Mobile Configuration Checks

This page gives an overview of the 4Industry Mobile Configuration Checks Suite that is included in the 4Industry Management application per release as well as a product backlog of possible future checks.

In order to run the checks, go to your instance > Instance Scan > Suites > 4Industry Mobile Configuration Checks > Execute Suite Scan.

Release 10.0

Name

Description

Name

Description

4I - Active Field Exists On Sync Config

Validates if the active field is available on the sync configuration since this is the field that is used to determine whether a record should remain on the device. NB: does not work for x_ap4_scm_km_job

4I - Equipment Field Exists On Sync Config

Validates if the equipment field is available on the sync configuration since all tasks rely on both the equipment and the work area field for filtering and syncing tasks. *

4I - Parent Field Exists On Sync Config

Validates if the parent field is synced to mobile since any task can be a child of another task. *

4I - Source Field Exists On Sync Config

Validates if the source field is synced to mobile sync any task can be related to another task. *

4I - Related Assessment Field Exists On Sync Config

Validates if the related assessement field is synced to mobile since every record can have a related assessment since any task can have an assessment connected to it. *

4I - Work Area Field Exists On Sync Config

Validates if the equipment field is available on the sync configuration since all tasks rely on both the equipment and the work area field for filtering and syncing tasks. *

4I - All Fields On Mobile App View Should Be In Sync Config

The mobileapp form view determines the form that is shown on mobile. In order to save the data, all fields should also be added to the sync configuration of that table.

4I - Check For Valid JSON In Mobile App Configurations

TBD

4I - Checklist Configuration Should Be Set When Checklist True

When the 'Enable checklist' checkbox is checked in the Table Configuration, there should also be a configuration added to x_ap4_scm_core_checklist_configuration to make sure that newly created checklist items can be created, read and updated.

4I - Full Sync Filter Should Contain Active Check

When a full sync is started, all records are removed from the mobile device. We then only want to have the active records on the device to make prevent the sync from taking to long.

NB: The partial sync does not have this filter, since it needs to know which records became inactive after which they are removed from the device. This sync takes less time since a last_updated timestamp is send along with the request.

4I - SCM Task Should Have Active True Active False

This is done to prevent these tasks overwriting the other task configurations

4I - Sync Layout Should Be Present For All Defined Items

When no sync configuration is available for a table configuration, mobile will try to sync the record, but won’t get any data due to the missing sync configuration.

4I - Table Config Location Filter on Top Parent

Some instances are configured with multiple Locations that are hierarchly organized. This settings makes sure that they always use the top level location.

4I - Table Configuration Should Be Present For All Core Tables 

Makes sure that the default flows of 4Industry work out of the box.

4I - Task Definition Table Configuration Has Condition Ad Hoc

Only Task Definition that have the Ad-hoc checkbox checked, should be synced to mobile to prevent too much data being synced.

4I - When Syncing Form Layout A View Should Be Present

Without a form lay-out, the data of a task can exist on the device, but cannot be visualized.

4I - When Syncing Forms/Lists A Sync Config Should Be Present

Without a list lay-out, the data of a task can exist on the device, but the the task cannot be opened.

4I - When Syncing List Layout A View Should Be Present

Without a list lay-out, the data of a task can exist on the device, but the the task cannot be opened.

4I - 'business_duration' must be present on 'x_ap4_scm_tmg_task' mobile form

Without the business duration field not being loaded in the lay-out model, the Grouped Task card cannot set the business duration for Simple Tasks.

* Job Management is excluded from this in R10 or earlier

Release 11

Name

Description

Name

Description

4I - State Field Exists On Sync Config

State field should always be part of the Sync configuration for a Task table (in order to revert changes when switching users)

4I - Opened Field Exists On Sync Config

Opened, Updated, Due Date, Order and Priority field should always be part of the Sync configuration for a Task table (to be able to configure these for sorting)

4I - Updated Field Exists On Sync Config

Opened, Updated, Due Date, Order and Priority field should always be part of the Sync configuration for a Task table (to be able to configure these for sorting)

4I - Due Date Field Exists On Sync Config

Opened, Updated, Due Date, Order and Priority field should always be part of the Sync configuration for a Task table (to be able to configure these for sorting)

4I - Order Field Exists On Sync Config

Opened, Updated, Due Date, Order and Priority field should always be part of the Sync configuration for a Task table (to be able to configure these for sorting)

4I - Priority Field Exists On Sync Config

Opened, Updated, Due Date, Order and Priority field should always be part of the Sync configuration for a Task table (to be able to configure these for sorting)

4I - Mobile Sync Field Exists On Sync Config

Migrate ‘4I - Active Field Exists On Sync Config' to '4I - Mobile Sync Field Exists On Sync Config’ (R10.0 feature)

4I - Full Sync Filter Should Contain Mobile Sync Check

Migrate ‘4I - Full Sync Filter Should Contain Active Check' to '4I - Full Sync Filter Should Contain Mobile Sync Check’ (R10.0 feature)

4I - Shift Config Field Exists On Sync Config

The Shift Config field should always be part of the Sync configuration so the user can filter on shift if necessary.

4I - Check Child For Task Definition Table Config

When the x_ap4_scm_core_task_definition is part of the Table Configuration, no other Task Definition tables should be part of the table configuration to prevent conflicting configurations.

4I - Home Card Lists Should Exist On Profile

When configuring a landing page card, validate that the list it refers to is also available as a list in the same user profile

4I - Field Configurations Exists On Mobileapp View

All fields that are configured as Mandatory, Read Only, Dependent On, Parent child Filter, Parent Child Selector, QR Code, Reference, Signature Field, Visibility, Equipment work area selector and Show Open Reference in the Field configuration, should also be visible on the Form.

4I - Parent And Child Table Configs Can't Sync Same Records

Validate that if both a parent and a child table are synced, the parent table doesn't sync any records of the child table to overwrite. This is done by checking if both tables filter based on location.top_parent, if so, an error is given.

4I - Choice Labels Cannot Be Empty

Sync breaks if there's an empty label on a choice field in a non-English language and you log in in that language. The field is mandatory but with importing it can be that it stays empty.

Release 12

Name

Description

Name

Description

4I - Ware exists on Sync Configuration for Centerline Audit

Checks to see if the ware field has been added to the sync configuration record belonging to the Centerline Audit table.

To be implemented (sorted on priority)

Critical priority (new R11 features)

State field should always be part of the Sync configuration for a Task table (in order to revert changes when switching users)
Opened, Updated, Due Date, Order and Priority field should always be part of the Sync configuration for a Task table (to be able to configure these for sorting)

High priority

Migrate ‘4I - Active Field Exists On Sync Config' to '4I - Mobile Sync Field Exists On Sync Config’ (R10.0 feature)
Migrate ‘4I - Full Sync Filter Should Contain Active Check' to '4I - Full Sync Filter Should Contain Mobile Sync Check’ (R10.0 feature)
Validate mobile back-end drive List Layout JSON (R10.0 feature)
Make sure the table is set for each List Layout
Validate that the JSON field is filled and that the object is valid. (R11.0 feature)
When the x_ap4_scm_core_task_definition is part of the Table Configuration, no other Task Definition tables should be part of the table configuration to prevent conflicting configurations.
The Shift Config field should always be part of the Sync configuration so the user can filter on shift if necessary.
Check if a mobile and table list layout configuration exists in the x_ap4_scm_mob_api_list_layout table when a Table Configuration has been created for a table.
When configuring a landing page card, validate that the list it refers to is also available as a list in the same user profile

Low priority

Tables added to the x_ap4_scm_core_checklist_configuration table should also be part of the table configuration to make sure that records are synced to the mobile device.
All fields that are configured as Mandatory in the Field configuration, should also be visible on the Form
Check that default Full Sync and Partial Sync configuration is set on location.top_parent instead of location.
Validate that if both a parent and a child table are synced, the parent table doesn’t sync any records of the child table to overwrite

Other checks to be implemented

All Grouped Task Definitions should be set to Ad-Hoc = True
Partial and full sync should have the same conditions set (so not full sync on location.top_parent = …. and partial sync on location = ….).
Found at JDE Horeca: sync breaks if there’s an empty label on a choice field in a non-English language and you log in in that language. The field is mandatory but with importing it can be that it stays empty.