Action

Action URIsAction URIA dynamic link, populated with fields from a task, job or appointment, that opens an external system in one click. can launch another application while passing parameters as the selected resourceResourceAn entity that can carry out work - a person, vehicle, tool, or room - that you schedule on the planning board. and date or time. For instructions how to construct an URI, see configuring actions.

Upsert

Inserts or updates an action uri.

Only URI's with matching SourceApp and SourceType fields are shown. UrlDesc is the description shown to the user.

Name	Data Type	Default	Required	Description
SourceApp	nvarchar(30)			See API reference
SourceType	nvarchar(10)			See API reference
UrlType	int		✔️	See API reference
Url	nvarchar(1000)		✔️
UrlDesc	nvarchar(255)
DefaultUrl	bit	0
RequestType	int		✔️	See API reference

Import

• This endpoint is available in the import API endpoint /import via the procedure mboc_upsertActionUrl.
• Example body:

  [
      {
          "StoredProcedureName": "mboc_upsertActionUrl",
          "ParameterNames": ["UrlType", "Url", "UrlDesc"],
          "ParameterValues": ["2", "https://actionableURI.domain", "Lock appointment"]
      }
  ]

API

See POST /actionUri, PUT /actionUri in the REST API reference.

API reference

Source

Dime.Scheduler is a centralized planning application. One of its key tenets is the ability to accommodate data from different origins. For instance, it is perfectly acceptable to plan work orders from Business Central, CRM, imported Excel sheets, etc., and Dime.Scheduler won't break a sweat because of the existence of the Source App and Source Type fields in the data model.

Source App

When the planner creates an appointment for a resource or task, Dime.Scheduler knows which system to notify. Through the connector setup, Dime.Scheduler will find a matching SourceApp and subsequently send the appointment to the corresponding URI.

The source appSource appAn identifier Dime.Scheduler attaches to data so it can route a change back to the correct back-office system. field is a unique identifier that identifies a back-officeBack officeThe ERP or business system Dime.Scheduler plans for - most often Microsoft Dynamics 365 Business Central. It owns the master data and remains authoritative over what it receives. instance such as a tenant of Business Central, a test environment, an instance of CRM cloud, or any other application you wish to use to feed data into Dime.Scheduler.

Back officeERP · CRM · LoB

served bySource App

ConnectorBound to one Source App

creates

JobProject container

contains

TaskWork to do

scheduled as

AppointmentPlanning decision

Step 1 of 4Back office Connector

The back office is bound to a connector

Each back-office instance - a Business Central tenant, a CRM environment, an Excel sheet - is identified by a Source App. The connector is configured for that one Source App and nothing else, so Dime.Scheduler always knows which system any record came from.

Source Type

The SourceType is used inside the back-office system itself. A source typeSource typeAn identifier that, together with the source app, tells Dime.Scheduler which back-office table a record belongs to. represents a distinct entity such as a service orderService orderA Business Central service management document. The service order solution plans it as one task or as one task per service item line, and writes the assignment back as a resource allocation., production orderProduction orderA Business Central manufacturing order with routing lines. The production routing solution puts those lines on the planning board against work and machine centers while BC’s own rules still hold., assembly orderAssembly orderA Business Central document that says what to build. The assembly order solution schedules the resources that build it and keeps the order’s dates in sync., etc.

The standard connectorsConnectorAn integration that links Dime.Scheduler to a back-office system, routing data in and scheduling decisions back out. that Dime Software provides make it possible to plan different types of resources and tasks. When Dime.Scheduler posts an appointment to a standard connector, it ends up in a staging tableStaging tableThe Dime.Scheduler Appointments table in Business Central where incoming appointments land first. Business Central processes rows from there, so a row can be received and still fail processing., which is then processed by the connector to ensure the appointment produced in Dime.Scheduler is traced back to the original record using the externally identifiable fields (JobNo, TaskNo, ResourceNo) that identify the record.

URL Type

Values for UrlType are:

• 0: Url is shown when user right-clicks an empty slot in the planning boardPlanning boardThe main graphical scheduling surface where dispatchers drag tasks onto resources across a timeline.
• 1: Url is shown when user right-clicks an appointmentAppointmentA task scheduled to a resource for a specific period - the scheduled instance you see on the planning board.;
• 2: Task
• 3: Map

Request Type

Values for RequestType are:

• 1: Regular, HTTP GET request using placeholders that are resolved in runtime.
• 2: HTTP POST that publishes the entire appointment graph to the endpoint.