Subsections of Templates
Integration Templates
Navigate to Administration → Templates → Integrations to manage integration templates.
Integration templates helps you to define and manage integration definitions. An integration in Serviceboard is represented by a system (e.g. Jira Cloud, Sharepoint, MS Teams or any other system that provides REST API).
As the name describes, we are defining a system in general (e.g. Jira Cloud), not a specific instance of Jira Cloud yet.
This way, you can have just one integration definition and reuse it for as many systems or environments of the same type as you need, without reinventing the wheel again.
Same as enterprise projects, you can define terms of use for integration templates. In larger organizations the systems are owned and managed by different internal groups and each group has their own terms of use they require to agree with by their users before they allow them to access and use it.
Icons of integration templates are displayed in the catalog of associated services for end users.
Service Templates
Navigate to Administration → Templates→ Services to manage service templates.
Service templates helps you to define and manage service definitions.
Service Types
Workspace
A service that results in creation of a workspace (e.g. Jira Project, Sharepoint Space..) and you can navigate to it by visiting a specific URL.
Automation
A service that just performs an action - automation (e.g. generate a report..).
1 service template = 1 REST API endpoint
Standalone service = service that can be provisioned individually, not necessarily in a bundle only.
Request
You can use the following format to use dynamic inputs (taken from what a user enters into the form):
param=#{fk_fieldkey}
A field must be created in advance to use the dynamic input for it.
Response
Process the data received on the response and store its values (e.g. in form of workspaces).
This is applicable only to the Workspace service type, and after each successful execution of the service, a new workspace is created in the section Home → My Workspaces or Projects → PROJECT NAME → Workspaces.
Additionally to dynamic inputs mentioned in the Request section above, you can use also JSON path or a fixed variable:
#{fk_integration_base_url} -> returns the URL of an integration instance
${$.xxx} -> parse the JSON response to get a value
Fields
Fields is a feature which allows administrators to add additional information when creating a new enterprise project. You can manage the fields from Administration → Templates → Services → SERVICE NAME → Manage Fields.
Fields can be set as optional/required, hidden/visible and can depend on each other.
Unlimited fields hierarchy is supported.
Field Types
The following field types are available:
- String
- Text
- Number
- Single Select
- Multi Select
- Checkbox
- Radiobutton
- Date
- External (fetch data in real-time via REST API)
- Group Picker
- User Picker (fetch users from LDAP)
- Secret (hidden by default)
Default Values
Default values help you to prefill selected field values when a user opens a service form. This is especially useful for hidden fields. Default values can be defined globally or per Project Category.
Default value cannot be created for Date or External fields.
Service Categories
Service Categories help you organize services into meaningful buckets and used later for filtering or configuring default form values.
Navigate to Administration → Templates → Services → Service Categories to view or create a new service category.