...
It will allow to leverage Salesforce Service Cloud + Community Cloud (+ Marketing Cloud + Sales Cloud to some extend in this first release), yet allowing you to fully customize Salesforce processes/workflows to exactly fit your needs…
Main features
Bidirectional synchronisation of contacts
Individuals created (=contacts which represent real people) in SecuTix are created/updated mapped in Salesforce as entity PersonAccount or Contact (support for PersonAccount is under development)Structures created in SecuTix as created/updated as Accountsit is a setup decision depending of the availability of PersonAccount in your Salesforce organization)
Relays in SecuTix (individuals linked to a Structure) are mapped to Salesforce Contact entities.
Structures in SecuTix (contacts which represent companies, associations...) are mapped to Salesforce Account entities.
- It a Contact is modified in SecuTix, the changes are propagated to the relevant object in Salesforce.
- If an Account, PersonAccount or Contact is modified in Salesforce, changes are propagated to SecuTix.
Synchronization from SecuTix to Salesforce relies on SecuTix' firehose contact mechanism.
With this mechanism, all contact modification events are stored in a queue. A scheduled job running every X minutes (configurable) processes the elements in the queue and pushes the changes to Salesforce.
Synchronization from Salesforce to SecuTix relies on Apex jobs triggered by changes on the entity.
Flexible synchronisation
SecuTix offers many custom fields for contacts : criteria, authorization, indicators...
Thanks to a specific mapping screen in SecuTix App in Salesforce, the mapping of fields between SecuTix and Salesforce can be customized fitting your needs.
Configuration detailed example
The SecuTix attribute name is a path allowing to read a contact's value by browsing it representation in SecuTix' API model.
In the example above, it means that a contact's first name will be mapped to the PersonAccount FirstName attribute in SalesForce.
Those "obvious" mappings are delivered as the default setup of SecuTix app.
But the mechanism allows more subtle mappings like
Here, the system will read the authorizations, filter them by code "EMAIL" and take the inverse value of the one that has been found.
Or here, the system will concatenate the 3 fields describing an address in SecuTix, concatenate them with EOL (End of line) characters and map them to Salesforce unique address field.
Interested ? Simply contact your account manager or open a service ticket in the Service Desk