Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 11 Current »

5.0.0

The Scheduler Provider object is part of the overall ServiceBroker Configuration object, in the following location:

Scheduler Provider object is used within the context of a REST Objects Providers (itself part of an REST Objects Configuration) to represent the details of how ServiceBroker is to be integrated with ServiceScheduling for the relevant tenant.   

 


Scheduler Provider Object Format

JSON Format
{
	"BCS": {
		"EnableRealTimeDispatch": true,
		"RealTimeDispRetryInterval": 10000
	},
	"DbUser": "",
	"Enabled": true,
	"ExtId": "",
	"Host": "",
	"GanttRouter": "",
	"Id": "",
	"Password": "",
	"User": "",
	"Version": "",
	"EmpExtObjectName": "",
	"Job": {
		"UseMoreNotesForJobInfo": true
	}
}

Scheduler Provider Object Properties


PropertyTypeRequired?Description
BCS    objectYesSee below.

EnableRealTimeDispatchbooleanYesWhen true, use the ServiceBroker REST Notification Changed Items to periodically poll for changes to Work Items in ServiceScheduling.

RealTimeDispRetryIntervalintYesWhen enabled via the EnableRealTimeDispatch setting, how often the ServiceBroker REST Notification Changed Items should be called to check for changes to Work Items, in milliseconds.
DbUserstringYes

The username to use when connecting to the ServiceScheduling SOAP API endpoint.

EnabledbooleanYes

Should integration with ServiceScheduling be used?

ExtIdstringYesThe external ID 
HoststringYes

The ServiceScheduling SOAP API endpoint to use for the ServiceScheduling integration, consisting of:

  • The protocol i.e. http:// or https://
  • The hostname or IP address
  • A colon
  • The port number.

For example:

  • https://example.com:46502
GanttRouterstringYes

The ServiceScheduling ServiceGANTT interface to use for the ServiceScheduling integration, consisting of:

  • The hostname or IP address
  • A colon
  • The port number.

For example:

  • example.com:46502
IdstringYesA human-readable identifier to be used in ServiceBroker logs when producing information about this integration, to assist with global debugging of the potentially many different ServiceScheduling system integrations (as every tenant in ServiceBroker could be integrated with a different ServiceScheduling installation).
PasswordstringYesThe password to use when connecting to the ServiceScheduling SOAP API endpoint.
UserstringYesThe designed user of the customer.
VersionstringYes

The full version of ServiceScheduling that is being integrated with.

  • For versions of ServiceScheduling prior to version 10.0.0, this is a number in 4 parts (e.g. 9.4.0.1);
  • For versions of ServiceScheduling including and after version 10.0.0, this is a number in 3 parts.
EmpExtObjectNamestringNoThe name of the object that contains additional information about employees in ServiceMobility, when integration with ServiceMobility is also enabled.
JobobjectYesThe job being scheduled.

UseMoreNotesForJobInfobooleanYes

When true, parse ServiceScheduling's specific "extended" moreNotes XML format when possible, and transform the information into FlexView Objects.


EnableTechPhoto

boolean


ConvertOrderTypes

boolean


MapMoreNotesToFlexViews

boolean

  • No labels