Turning Off FSM Schedule Board CRM Task Linking and Case Expansion

event.task.map.link supplies the grouping value used for linked focus and automatic selection. The standard mapping uses the case number. It is not a record hyperlink. Links in title, details, add, and other display and action mappings are separate.

Make the following two independent changes:

Set event.task.map.link to the Boolean value false. This setting stops automatic focus or selection of other tasks through the mapped link value. Deleting the property from a custom override would allow the standard mapping to remain inherited.
Replace event.task.filters with its original first branch. Remove the outer or branch that uses the nested cases search. This change stops loading additional CRM tasks based solely on a shared case within the requested resource and date scope.

The following OneWorld example makes both changes. It retains the standard subsidiary formula, primary-assignee matching, nonempty task-team matching, and start-date criteria. The array completely replaces event.task.filters. The rest of the standard task definition and map remains inherited.

          {
  "routes/scheduler": {
    "event": {
      "task": {
        "filters": [
          [
            [
              ["assigned", "anyof", "${ request.parameters.resource }"],
              "or",
              [
                ["formulatext:{custevent_nx_task_team.id}", "isnot", ""],
                "and",
                ["custevent_nx_task_team", "anyof", "${ request.parameters.resource }"]
              ]
            ],
            "and",
            ["startdate", "onorafter", "${ request.parameters.start }"],
            "and",
            ["startdate", "onorbefore", "${ request.parameters.end }"],
            "and",
            ["formulatext:case when '${ user.view }' = '0' or coalesce({case.subsidiary.id}, {job.subsidiary.id}, {company.subsidiary.id}, 0) in (0,${ user.view }) then 'T' else 'F' end", "is", "T"]
          ]
        ],
        "map": {
          "link": false
        }
      }
    }
  }
}

For a non-OneWorld account, omit the final "and" and subsidiary-formula condition, and retain the rest of the filter unchanged. Also retain any intentional task criteria already configured in the account. This example replaces standard case expansion and doesn't automatically preserve an existing custom filter array.

Setting link: false alone leaves the case-expansion search and its extra returned records in place. Removing the search alone leaves automatic linking among any matching visible tasks still returned. Applying both changes removes automatic linking and case-expansion loading. Individual selection, manual selection of multiple tasks, the underlying case relationship, and each task's editing conditions remain available.

Important:

Leave event.projecttask.filters unchanged. Its nested projecttasks search identifies eligible project task IDs and then loads the complete resource assignments. The standard project task map has no case link property. The event.nonworkingday and event.resourceallocation definitions also have no standard case-link mapping. Removing CRM case expansion doesn't require changing those definitions.

Turning Off FSM Schedule Board CRM Task Linking and Case Expansion

Additional Information

Related Topics