Service Settings

Use this guide to learn how to work with the Service Settings window. Service Settings centralizes tenant defaults, scheduling rules, background processes, and guided migration tools for the service suite.

Common Reminders

• Settings changes affect tenant behavior across service workflows, not just the current user.

• Process actions are queued and may take time to complete.

• Signature migration uploads must match the required CSV structure for the selected dataset.

• Telematics webhook actions depend on telematics being enabled for the tenant.

Understand the Service Settings Window

Service Settings is the administration window for service-specific defaults and operational processes.

What Service Settings Supports

• Service call default values and completion behavior.

• Schedule Board working hours and holiday dates.

• Maintenance contract defaults.

• Business Central dimension and posting group settings.

• AI-generated resolution summary settings.

• Business Central and telematics webhook management.

• Background migrations and search embedding refresh.

• Guided Signature data uploads.

Tabs in the Window

• Settings: Maintains tenant defaults that affect service creation, scheduling, and AI assistance.

• Processes: Queues and monitors integration and migration jobs.

• Signature Migration: Guides users through legacy Signature imports.

Use the Settings Tab

Use this tab to define the defaults and rules used across service workflows.

To use the Settings tab:

1. Open Service Settings.

2. Stay on the Settings tab.

3. Review and complete the service defaults.

   • Default Service Call Priority (Optional but recommended): Sets the fallback priority for new service calls.

   • Scheduled Open Substatus (Optional): Sets the open substatus used when the first appointment is created for an open service call.

   • Auto-complete when all appointments are Complete (Optional): Turns on automatic service call completion after the last appointment is completed.

4. Review Business Central service dimension settings.

   • Use BC Global Dimension (Optional): Controls whether the global dimension configuration is used.

   • BC Global Service Dimension (Optional): Select the Business Central dimension used for service tagging.

   • BC Global Service Dimension Value (Optional): Select the value paired with the global service dimension.

   • BC Service Call Dimension (Optional): Select the service call dimension field.

   • BC Service Call Dimension Value (Optional): Select the service call dimension value.

5. Review maintenance contract defaults if Maintenance Contracts is enabled.

   • Maintenance Call Type (Optional unless your process requires a default): Sets the default call type for maintenance-generated work.

   • Maintenance Priority (Optional unless your process requires a default): Sets the default priority for maintenance-generated work.

   • Maintenance Split Strategy (Optional): Select how maintenance work should be split, such as a single technician across multiple days or multiple technicians in a single day.

   • Maintenance Billing Product (Optional): Sets the default billing product when a contract does not provide its own billing product.

6. Review inventory posting group rules.

   • Service T&M (Optional but required for applicable Send to ERP scenarios): Select the general business posting group used for service time and material inventory consumption.

   • Service Maintenance Contract (Optional but required for applicable Send to ERP scenarios): Select the general business posting group used for maintenance contract inventory consumption.

7. In the Schedule Board Hours section, review the Service Hours by Day (Optional but strongly recommended). Set enabled days and the working start and end times used by scheduling and planning.

8. Review Holiday Dates (Optional). Add dates that should be skipped during maintenance contract generation.

9. In the AI Enhancements section,

   • Use AI to draft the resolution summary when completing service calls (Optional): Enables AI-generated resolution summary drafting.

   • Resolution Summary Prompt (Optional): Defines the prompt used when generating the summary.

10. Save the tab when your changes are complete.

Key Rules

• Problem type defaults can override the Default Service Call Priority during service call creation.

• Schedule Board hours affect planner placement, conflict checking, and maintenance visit start times.

• Holiday dates are skipped during maintenance contract generation.

• Inventory Send to ERP can be blocked when posting group rules are missing for the required context.

• AI resolution summaries only populate empty resolution notes and ignore internal notes.

• Maintenance contract settings are available only when Maintenance Contracts is enabled in registration.

Use the Processes Tab

Use this tab to manage webhooks, queue migrations, and run maintenance jobs.

To use the Processes tab:

1. Open Service Settings.

2. Select the Processes tab.

3. Review the available process cards.

4. In the Business Central Webhooks section, you can use webhook management to create or refresh the standard webhook set for customers, vendors, items, cost audit ledgers, ship-to address changes, and tax area codes.

5. In the Azuga Telematics Webhook section, you can manage the Azuga webhook used for GPS updates. This is enabled when Telematics is turned on in WennSoft Registration.

   • Notification Email (Required for Azuga Telematics Webhook creation): Enter the email required to register the webhook.

   • Create/Update/Delete Webhook

6. In the Lookup Data Populate section, Choose which lookups to populate. Seeds supported lookup data with duplicate detection.

   • Shared Lookups: Choose the lookups to populate that are consistent across business unit types.

   • Business Specific Lookups: Select the business unit type when the lookup process requires it.

7. In the Business Central Data Migration section, you can trigger Business Central Sync jobs that populate WennSoft lookups.

   • Posting Groups

   • Customers & Locations

   • Vendors

   • Products

   • Payment Terms

   • Dimensions

   • Tax Area Codes

   • Accounting Periods

   • GL Accounts

8. Use search maintenance when embeddings need to be refreshed.

   • Run Search Embedding Refresh (Optional): Queues regeneration of customer, location, and equipment embeddings after large imports or AI setting changes.

9. Review process history and status.

   • Status (System-filled): Shows the current process status.

   • Trace ID (System-filled): Provides the correlation id for support and troubleshooting.

   • Processed and Updated Counts (System-filled when available): Shows the number of records handled by the run.

   • Completed Date and Time (System-filled when available): Shows when the run finished.

Key Rules

• Each process run queues a background job rather than completing immediately in the window.

• Use Process Logs when you need to review payloads, results, or error details for queued runs.

• Customer and ship-to processes update WennSoft customers and locations.

• Vendor migration uses vendor upsert logic for the current tenant.

• Notification Email is required before an Azuga telematics webhook can be created.

Use the Signature Migration Tab

Use this tab to prepare and upload CSV files for supported Signature migration datasets.

To use the Signature Migration tab:

1. Open Service Settings.

2. Select the Signature Migration tab.

3. Click the Data to Migrate drop-down to choose the dataset you want to upload.

   • Call Types

   • Departments

   • Equipment Types

   • Employees

   • Manufacturers

   • Positions

   • Problem Types

   • Resource Technicians

   • Service Calls

   • Appointments

   • Ship To Xrefs

   • Skill Levels

4. Review the guided instructions for the selected dataset.

   • Copy SQL (Optional when available): Copies the published SQL used to extract the selected dataset from the source system.

   • Required Headers (Required for upload): Review the required CSV column names for the selected dataset.

5. Generate the source CSV file.

6. Upload the CSV File for the selected dataset, ensuring it matches the published template and required headers.

7. Queue the migration job.

8. Review migration history and trace information.