Launching Signature Agent Configuration

This is the user interface that is used to configure the CDC and Event triggers.

1. Launch Signature Agent Configuration.
2. Log into the SQL Server Instance. The Signature Agent Configuration is divided into two tabbed sections:
   • Home: The Home tab is where Signature Agent is configured.
   • CDC Configuration: The CDC tab is used to set up the CDC for the database for capturing state changes to the database tables.

Setting up Change Data Capture (CDC) configuration

Creating the CDC change options is the first step in setting up Signature Agent.

1. In Signature Agent Configuration, choose the CDC Configuration tab.
2. In the Name column, choose the Dynamics GP database and then choose the database.
3. Select Create Objects to create the CDC change options that are listed on the right side of the window.
4. Four entities default as enabled (for service appointments):
   • Appointment
   • Service Call
   • Service Option
   • Technician
5. To enable additional triggers, right-click on the entity name and choose Enable Trigger(s). For example, enable Job to track changes to the job tables for job appointments.
   • Enabled entities are indicated with a green  icon.
   • Disabled entities are indicated with a red  icon.

Configuring Signature Agent

Each company that will be used with Signature Agent Configuration will need to be set up.

1. On the Home tab, create a new company by choosing New Company or choose an existing company and then choose Properties.
2. In the Edit Company Connection window, you will be associating the company to a Signature Agent Service that will be monitoring for changes.

Database tab

1. Enter the Company Name. This is only used for the display name in the Tenant tree to the left.
2. Enter the Database Server IP/Port. To enter the Database Name, you can either enter the name or choose Browse and then select the company database.
3. Enter the Username and Password for the database.
4. Select Test Connection to verify that the database settings are correct and can connect to the database. You will be prompted to save the settings prior to the test running. The Access Key is generated at this time. See General tab.

Access tab

1. The Incoming Access Key is generated by the database once the company is saved prior to testing the configuration. This key is used as a unique identifier.
2. The Email Alias is the email address that your customers will use when sending an email to create a service call. For example, if you create an alias of Fabrikam, your customers would send an email for a service to fabrikam@servicerequests.io.

3. Select the cloud-based server Environment (Note that additional environments may exist based on licensing): 

   • Production
   • Staging
4. Select the Agent Service.

Company Info tab

Enter the company information that is included in some of the communications.

Dispatcher Emails

Mark the Dispatcher email address checkbox(es) to indicate where notifications of service aggregate changes should be sent. 

These changes include:

• Schedule date
• Priority
• NTE amount: This also involves manually updating the service quote in Signature.
• Service status: A client may cancel the service through the service aggregator.

Maintenance tab

This section is used for setting up a Maintenance Schedule. The Next Scheduled Eventing Pause is used to stop Signature Agent from accessing the database.

1. Choose Edit.
2. In the Eventing Schedule Editor window, create an optional schedule to pause the Eventing Engine.
   • Choose Weekly or Monthly.
   • Choose the day(s) or month(s), this display is related to the previous choice.
   • Choose the Time of Day and Frequency.
   • Enter the Duration (Hours).
3. Choose OK. The Tenant tree now displays the company and automatically creates Event Triggers.

Viewing log file

Choose View Event Log to view the log.txt file that displays information about trigger events. For example, an email for service was received and a response is sent out.