comsave / salesforce-outbound-message-bundle
This bundle allows you to easily process outbound messages sent by Salesforce.
Installs: 1 092
Dependents: 0
Suggesters: 0
Security: 0
Stars: 4
Watchers: 3
Forks: 1
Open Issues: 0
Type:symfony-bundle
Requires
- php: >=7.2
- ext-json: >=1.6
- ext-soap: >=7.2
- comsave/salesforce-mapper-bundle: ^3.4.0
- doctrine/mongodb-odm: ^1.1|^2.0
- symfony/config: ^3.4|^4.3
- symfony/dependency-injection: ^3.4|^4.3
- symfony/event-dispatcher: ^3.4|^4.3
- symfony/http-kernel: ^3.4|^4.3
- symfony/polyfill-apcu: ^1.12
- symfony/property-access: ^3.4|^4.3
Requires (Dev)
- phpunit/php-code-coverage: ^6.0
- phpunit/phpunit: ^7.0
Provides
- ext-mongo: *
- dev-master
- 0.12.1
- 0.12.0
- 0.11.7
- 0.11.6
- 0.11.5
- 0.11.4
- 0.11.3
- 0.11.2
- 0.11.1
- 0.11.0
- 0.10.3
- 0.10.2
- 0.10.1
- 0.10.0
- 0.9.2
- 0.9.1
- 0.9.0
- 0.8.0
- 0.7.8
- 0.7.7
- 0.7.6
- 0.7.5
- 0.7.4
- 0.7.3
- 0.7.2
- 0.7.1
- 0.7.0
- 0.6.2
- 0.6.1
- 0.6.0
- 0.5.1
- 0.5.0
- 0.4.5
- 0.4.4
- 0.4.3
- 0.4.2
- 0.4.1
- 0.4
- 0.3.10
- 0.3.9
- 0.3.8
- 0.3.7
- 0.3.6
- 0.3.5
- 0.3.4
- 0.3.3
- 0.3.2
- 0.3.1
- 0.2.37
- 0.2.36
- 0.2.35
- 0.2.34
- 0.2.33
- 0.2.32
- 0.2.31
- 0.2.30
- 0.2.29
- 0.2.28
- 0.2.27
- 0.2.26
- 0.2.25
- 0.2.23
- 0.2.22
- 0.2.21
- 0.2.20
- 0.2.19
- 0.2.18
- 0.2.17
- 0.2.15
- 0.2.14
- 0.2.13
- 0.2.12
- 0.2.11
- 0.2.10
- 0.2.9
- 0.2.8
- 0.2.7
- 0.2.6
- 0.2.5
- 0.2.4
- 0.2.3
- 0.2.2
- 0.2.1
- 0.1.17
- 0.1.15
- 0.1.14
- 0.1.13
- 0.1.12
- 0.1.11
- 0.1.10
- 0.1.9
- 0.1.8
- 0.1.7
- 0.1.6
- 0.1.5
- 0.1.4
- 0.1.3
- 0.1.2
- 0.1.1
- dev-add-license-1
- dev-staging
- dev-add-after-flush-event
- dev-skip-and-delete-options
- dev-symfony3
This package is auto-updated.
Last update: 2024-10-29 05:17:09 UTC
README
Create, update, remove objects in Symfony sent through Salesforce outbound messages.
Requirements
This bundle assumes you're using:
- MongoDB database (and specifically
doctrine/mongodb-odm
). comsave/salesforce-mapper-bundle
for Salesforce object mapping to your MongoDBDocument
classes.
Bundle features
- Object
create
- Object
update
- Object
delete
. To enable this complete additional setup steps. - Object custom handling
beforeFlush
- Object custom handling
afterFlush
Installation
composer require comsave/salesforce-outbound-message-bundle
- Register the bundle in your
AppKernel.php
by addingnew Comsave\SalesforceOutboundMessageBundle\ComsaveSalesforceOutboundMessageBundle()
- To handle the Salesforce's incoming outbound messages create a route (for example
/sync
) and a method to a controller:
<?php use Symfony\Component\HttpFoundation\Request; use Symfony\Bundle\FrameworkBundle\Controller\Controller; use Comsave\SalesforceOutboundMessageBundle\Services\RequestHandler\OutboundMessageRequestHandler; class OutboundMessageController extends Controller { public function syncAction(Request $request, OutboundMessageRequestHandler $requestHandler) { try { $outboundMessageXml = $request->getContent(); return $requestHandler->handle($outboundMessageXml); } catch (\Throwable $e) { throw new \SoapFault("Server", $e->getMessage()); } } }
- add the bundle configuration in your
app/config/config.yml
comsave_salesforce_outbound_message: # WSDL_CACHE_NONE, WSDL_CACHE_DISK, WSDL_CACHE_MEMORY or WSDL_CACHE_BOTH wsdl_cache: 'WSDL_CACHE_DISK' # An absolute path to Salesforce object WSDL files wsdl_directory: '/absolute/path/' document_paths: # Map a document using its Salesforce name and your local class CustomObject__c: path: 'YourNamespace\Documents\CustomObject' force_compare: false # if true, incoming object will be compared to existing ones in the database; will continue sync only if not equal
- Add
DocumentInterface
to the document class you'd like to be tracked by theOutboundMessageBundle
.
<?php use Comsave\SalesforceOutboundMessageBundle\Interfaces\DocumentInterface; use LogicItLab\Salesforce\MapperBundle\Model\Account as BaseAccount; class Account extends BaseAccount implements DocumentInterface { }
- Create an
EventSubscriber
for an object you'd like to sync. It would look something like this for theAccount
object:
<?php namespace YourNamespace\EventSubscriber; use Comsave\SalesforceOutboundMessageBundle\Event\OutboundMessageBeforeFlushEvent; use Comsave\SalesforceOutboundMessageBundle\Event\OutboundMessageAfterFlushEvent; use Symfony\Component\EventDispatcher\EventSubscriberInterface; use Comsave\SalesforceOutboundMessageBundle\Interfaces\DocumentInterface; use Comsave\Webservice\Core\UserBundle\Document\Account; class AccountSoapRequestSubscriber implements EventSubscriberInterface { public static function getSubscribedEvents() { return [ OutboundMessageBeforeFlushEvent::NAME => [ ['onBeforeFlush'], ], OutboundMessageAfterFlushEvent::NAME => [ ['onAfterFlush'], ], ]; } public function supports(DocumentInterface $document): bool { $documentClass = get_class($document); return Account::class == $documentClass || $document instanceof Account; } public function onBeforeFlush(OutboundMessageBeforeFlushEvent $event) { /** * Make sure to do call $this->supports() before you start processing the object * You only want to process the correct object in this EventSubscriber (which is Account in this case) */ /** @var Account $newAccount */ $newAccount = $event->getNewDocument(); if (!$this->supports($newAccount)) return; /** @var Account $existingAccount */ $existingAccount = $event->getExistingDocument(); /** * You can do any modifications you want to the object before it get's saved (flushed) to the database. * - - - * $event->getExistingDocument() provides you access to the existing object (if it exists) * $event->getNewDocument() provides you access to the new object delivered by the outbound message. This is the object that will be merged over the existing one (if any) and saved to the database. In most of the cases you only need to use this one. */ } public function onAfterFlush(OutboundMessageAfterFlushEvent $event) { /** @var Account $account */ $account = $event->getDocument(); if (!$this->supports($account)) return; /** * You can process the object further if necessary after it has been saved (flushed) to the database. */ } }
- Add your newly created route to the Salesforce outbound message for the object you want to sync (
Account
in our example). - That's it! Trigger an outbound message to be sent out and see everything happen automagically. 😎 👍
License
This project is licensed under the MIT License.