PentaServiceChannelConnector To ServiceChannel - Customer Implementation Guide

Support

For issues related to this solution, please log a ticket via the Service Desk.

Timeline

Implementation, including installation of PentaConnect service and configuration of PentaServiceChannelConnector and Procore is estimated to take 1-2 hours, assuming all necessary information is supplied to Penta.

Requirements

  1. Signed PentaConnect contract (with PentaConnectServiceManagement and PentaServiceChannelConnector)

  2. PENTA v24.1 or up

  3. ServiceChannel

  4. Web server with PentaConnect v23.08 or up

Customer to supply

  1. PENTA User ID to be used for transactions from PentaConnect to PENTA.

  2. ServiceChannel Provider credentials (Provider ID, Client ID & Secret)

  3. Email Address(es) for customer-facing notifications emails.

  4. Mapping specifications from ServiceChannel fields to Penta fields.

    1. This allows data to either flow directly into corresponding fields in Penta, or it allows defining which Penta values correspond to which ServiceChannel values.

    2. For example, if you have ServiceChannel Trade of “AC”, you might specify that that corresponds to the Penta Service Type and the corresponding value in Penta is “HVAC”. Likewise, you might simply specify that all work orders created in Penta from ServiceChannel have a Penta Service Type of of “HVAC”. Or you might specify that the Penta Service Type value should be set to whatever is in the Trade field in ServiceChannel, because you have set up the same exact values in both systems.

    3. Examples mappings:

      1. Mapping Type: Direct Copy
        PentaPropertyName=ServiceTypeCode
        PentaPropertyValue={null}
        ServiceChannelPropertyType=Trade
        ServiceChannelPropertyValue={null}
        Result: The Penta Service Type Code is set to the value in Service Channel’s Trade column

      2. Mapping Type: Constant
        PentaPropertyName=ServiceTypeCode
        PentaPropertyValue=HVAC
        ServiceChannelPropertyType={null}
        ServiceChannelPropertyValue={null}
        Result: Always set Penta’s Service Type Code to “HVAC”

      3. Mapping Type: One-to-one
        PentaPropertyName=ServiceTypeCode
        PentaPropertyValue=HVAC
        ServiceChannelPropertyType=Trade
        ServiceChannelPropertyValue=AC
        Result: When Service Channel’s Trade is set to “AC”, set the Penta Service Type Code to “HVAC”.

      4. Mapping Type: One-to-one
        PentaPropertyName=ServiceTypeCode
        PentaPropertyValue=ELECT
        ServiceChannelPropertyType=Trade
        ServiceChannelPropertyValue=Electrical
        Result: When Service Channel’s Trade is set to “ELECT”, set the Penta Service Type Code to “Electrical”.

    4. These are matched based on a hierarchy, where we would look for an applicable one-to-one entry first. So if the Trade coming from Service Channel was “Furnace”, we would look for a match based on ServiceChannelPropertyName first. Having not found one, we would look for an entry in the xref where the type is DirectCopy, meaning we copy the value from the Service Channel property Trade directly to Penta. If that entry also doesn’t exist, then we look for a Constant entry in the xref table.