Changes between Version 35 and Version 36 of TicketToSalesforcePlugin


Ignore:
Timestamp:
Nov 17, 2015, 12:55:58 PM (8 years ago)
Author:
figaro
Comment:

Cosmetic changes

Legend:

Unmodified
Added
Removed
Modified
  • TicketToSalesforcePlugin

    v35 v36  
    55== Description
    66
    7 Maintain synchronization of Trac tickets in [http://www.salesforce.com Salesforce]. Trac tickets are reflected by the Salesforce custom objects, Ticket and Comment. 
    8 Ticket objects are linked to Cases via many-to-many relationship provided by the !CaseTicketLink custom object. Even though this is a many-to-many relation,
    9 Trac uses a custom text field for the Case number, so it's essentially many-to-one. 
     7This plugin synchronizes Trac tickets in [http://www.salesforce.com Salesforce]: Trac tickets are reflected by the Salesforce custom objects, Ticket and Comment. Ticket objects are linked to Cases via many-to-many relationship provided by the !CaseTicketLink custom object. Even though this is a many-to-many relation, Trac uses a custom text field for the Case number, so it's essentially many-to-one. 
    108
    119Comment objects are related to Ticket objects via the link custom object, !TicketCommentLink. The related lists layouts are modified to display the related object fields rather then the object id.
    1210
    13 See the [#ModuleDependencies Module Dependencies] required.
     11This plugin comes with some Salesforce artefacts that are installed to your Salesforce org via an Ant script, using custom Ant tasks from Salesforce. There are four custom objects - `Ticket`, `Comment`, `CaseTicketLink`, `TicketCommentLink`; and four custom layouts - `Case Layout`, `Ticket Layout`, `Comment Layout` and `TicketCommentLink Layout`. The `Case Layout` is the default, out-of-the-box `Case Layout` with an additional related list - "Tickets" appended; so if you already have a customized `Case Layout`, you may want to modify the included `package.xml` to omit the `Case Layout` and manually add the `Tickets` related list to your `Case Layout`. The three other layouts are new and can be safely added, regardless of existing customizations.
    1412
    15 This plugin comes with some Salesforce artifacts that are installed to your Salesforce org via an Ant script, using custom Ant tasks from Salesforce. There are four custom objects - `Ticket`, `Comment`, `CaseTicketLink`, `TicketCommentLink`; and four custom layouts - `Case Layout`, `Ticket Layout`, `Comment Layout` and `TicketCommentLink Layout`. The `Case Layout` is the default, out-of-the-box `Case Layout` with an additional related list - "Tickets" appended; so if you already have a customized `Case Layout`, you may want to modify the included `package.xml` to omit the `Case Layout` and manually add the `Tickets` related list to your `Case Layout`. The three other layouts are new and can be safely added, regardless of existing customizations.
     13The "migration tool" is just a set of Salesforce-specific Ant tasks which use the metadata API to upload/download artefacts, such as custom objects, etc.
    1614
    17 The "migration tool" is just a set of Salesforce-specific Ant tasks which use the metadata API to upload/download artifacts, such as custom objects, etc.
    18 
    19 I provide an Ant script to perform the deployment. You need to acquire the ''ant-salesforce.jar'' by following these steps:
     15An Ant script is provided to perform the deployment. You need to acquire the ''ant-salesforce.jar'' by following these steps:
    2016
    2117 1. Log into a Salesforce.com org on your deployment machine.
     
    4642== Download
    4743
    48 Download the zipped source from [download:tickettosalesforceplugin here].
     44Download the zipped source from [export:tickettosalesforceplugin here].
    4945
    5046== Source
    5147
    52 You can check out TicketToSalesforcePlugin from [http://trac-hacks.org/svn/tickettosalesforceplugin here] using Subversion, or [source:tickettosalesforceplugin browse the source] with Trac.
     48You can check out TicketToSalesforcePlugin from [/svn/tickettosalesforceplugin here] using Subversion, or [source:tickettosalesforceplugin browse the source] with Trac.
    5349
    54 == Module Dependencies
     50== Installation
    5551
    56  * '''sforce''', [pypi:salesforce-python-toolkit]
    57  * '''suds''', versions 0.3.6 to 0.3.9 '''only''' (ie 0.4.0 '''won't work''') Python SOAP API, https://fedorahosted.org/suds
    58  * [wiki:XmlRpcPlugin XML-RPC Plugin]
     52This plugin is dependent on the following:
     53 * '''sforce''': [pypi:salesforce-python-toolkit]
     54 * '''suds''': versions 0.3.6 to 0.3.9 '''only''' (ie 0.4.0 '''won't work''') Python SOAP API, https://fedorahosted.org/suds
     55 * [wiki:XmlRpcPlugin XML-RPC plugin].
     56
     57General instructions on installing Trac plugins can be found on the [TracPlugins#InstallingaTracplugin TracPlugins] page.
    5958
    6059== Example