FSM Schedule Board Searches and Editing Constraints

This topic includes the following sections:

• Search Filters and Panel Filters

• Editing and Assignment Constraints

The following table lists standard event definitions and their feature requirements.

Definition	Records and Purpose	Availability
event.task	CRM tasks and their scheduling data.	Standard definition.
event.projecttask	Project tasks and their scheduling data.	Depends on the Project Management feature.
event.nonworkingday	Field Service Employee Non-Working Day records.	Standard definition.
event.resourceallocation	Resource Allocation time blocks.	Depends on Project Management and Resource Allocations.

The board uses mapped event IDs, resource associations, dates, time zones, labels, and eligibility values. Preserve the standard date and resource criteria and access restrictions when changing searches. The selected date range and resources form part of those criteria.

The following fragment changes only the CRM task display label. It retains the rest of the inherited map and reads the NetSuite task title for label:

          {
  "routes/scheduler": {
    "event": {
      "task": {
        "map": {
          "label": "title"
        }
      }
    }
  }
} 

        

This changes that label's source. It doesn't change the task title, event identity, scheduling fields, or other labels.

Search Filters and Panel Filters

Search filters select the records retrieved from NetSuite. Panel filters select from mapped records available to the board. A panel filter cannot display a record excluded by the underlying search. For information about the default selection logic, subsidiary scope, and the meaning of user.view, user.edit, and the request tags, see Board Searches and Request Tags.

Schedule Board search definitions use the board's server template context. This differs from the current-job context in FSM Mobile. Don't assume that an FSM Mobile event reference is available in a Schedule Board search. For template syntax, see FSM Expressions and Template Tags.

Warning:

Assess record visibility and scheduling effects before changing resource, date, or subsidiary criteria, Boolean grouping, or the nested project task search. Removing CRM case expansion is an exception. For more information, see Turning Off FSM Schedule Board CRM Task Linking and Case Expansion. These searches are part of the board's data boundary. Panel filters cannot correct a broadened search or restore excluded data.

The following table lists configuration changes and their risks.

Change	Risk and Consequence
Remove or broaden the user.view condition	Can return records outside the intended subsidiary view scope through the board. Don't rely on panel filters or editing eligibility to keep retrieved data out of view.
Remove or broaden the user.edit mapping	Can make records or assignment targets selectable outside the intended editing scope. Board editing controls and NetSuite save permissions remain separate. A save may fail or, where permitted, change unintended records.
Remove resource criteria or the nonempty team condition	Can include unrelated assignments or incorrectly match tasks with empty teams, including during unassigned-work requests. Removing team matching can instead hide work assigned to team members.
Remove date criteria, or use the same date rule for every record type	Can load unnecessary history or exclude valid work. CRM tasks use start-date inclusion. Project tasks and contextual blocks use date overlap.
Change the nesting of and and or conditions	Can make a scope or date condition apply to only one branch. Adding a restriction outside the case-expansion branch and its nested search is not necessarily equivalent to adding it inside both.
Remove the project task nested ID search or filter assignment joins directly in the outer search	Can return an incomplete resources list. Project task saves rebuild assignments, so a partial list can lead to lost assignments or incorrect work recalculation. This is not the CRM case-link search.
Replace a standard filters array or add a new resource definition without its own restrictions	Arrays replace inherited arrays. New definitions don't inherit the employee definition's safeguards. A short custom filter can silently remove resource, date, or subsidiary conditions.

Keep subsidiary formulas conditional on the account's enabled features. References to subsidiary fields are not a portable substitute for the non-OneWorld defaults. Preserve mapped IDs, assignment lists, calendars, dates, time zones, and editing rules when changing presentation.

Editing and Assignment Constraints

The following table describes the conditions that govern editing and assignment.

Condition	Role
Board editing eligibility	administrators identifies roles for which board editing controls are enabled. The standard configuration includes the Administrator role and roles marked for FSM scheduling.
Event eligibility	The event's mapped editable value determines whether the event is eligible for editing.
Resource eligibility	Resource data determines whether the target employee is eligible for the relevant assignment, including applicable subsidiary and Project-resource conditions.
NetSuite processing	Permissions, record requirements, and the applicable save behavior still govern the resulting record operation.

The standard CRM task eligibility requires the task to be not started, with applicable subsidiary editing restrictions. Project tasks have additional requirements, including fixed-start scheduling and the relevant project resource condition.

Important:

Don't replace standard eligibility or access conditions with unrestricted values merely to enable dragging. Displaying a record, enabling an editing control, and successfully saving an assignment are different results.

An administrators override replaces the inherited array. Preserve the required authorized roles if that setting is changed. It doesn't grant NetSuite record permissions.

A new event definition or copied map doesn't establish that the record supports Schedule Board scheduling. Some standard definitions have specialized save processing. Confirm the supported record type, identity, mapped fields, and save behavior before treating a custom definition as equivalent to a standard event.

Additional Information

• FSM Searches and Field Mapping
• FSM Expressions and Template Tags
• FSM Schedule Board Visibility and Editing Eligibility
• FSM CRM Task Record

Related Topics

• FSM Schedule Board Configuration
• Configuring FSM Schedule Board Resources
• Turning Off FSM Schedule Board CRM Task Linking and Case Expansion
• Configuring FSM Schedule Board Groups and Panel Options
• Adding an FSM Schedule Board Case Type Filter

General Notices