Action

Action URIs can launch another application while passing parameters as the selected resource and date or time. For instructions how to construct an URI, continue here.

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 app field is a unique identifier that identifies a back-office 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.

Source Type

The SourceType is used inside the back-office system itself. A source type represents a distinct entity such as a service order, production order, assembly order, etc.

The standard connectors 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 table, 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 board
• 1: Url is shown when user right-clicks an appointment;
• 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.