Let's Talk

Salesforce Integration

Papyrus offers a standard integration of Papyrus Business Correspondence with Salesforce using a REST API:

  • Papyrus WebRepository domain, on-premis or Cloud
  • REST Adapter as client of Webservices exposed by Salesforce
  • Papyrus Server/HTTPS to expose Webservices consumed by Salesforce
  • Exposed Webservices implemented within the Atlas API, Lightning API, Apex (depending on the Salesforce version)
  • Consume the Web Services exposed by Papyrus as a client

    The following screenshots show a typical browser-based application integration where Salesforce is the leading application calling Papyrus Client/HTML when document writing is requested.

    Salesforce calling Papyrus for document writing

    Document Template Selection

    Document writing invoked via Salesforce in a dedicated browser tab

    The resulting document is saved back to Salesforce or stored in Papyrus and accessed via a link

    Guidewire Integration

    The Papyrus Business Correspondence application will run as Papyrus WebClient application. The Papyrus platform will communicate at the back end with Guidewire's bi-directional WebServices. A business clerk triggers a business event in Guidewire which communicates over the HTTP(S)-Webservices with the Papyrus REST Adapter. Papyrus document templates are send to Guidewire for selection in the Guidewire UI. When a template is selected Papyrus opens in the Papyrus WebClient.

    SAP Integration

    Typically, Papyrus is integrated into SAP systems according to the following scenarios to facilitate the formatting and processing of documents based on one of SAP's spool data formats.

    1. Papyrus receives document processing requests from SAP
      SAP's XOM interface is a generic interface to the SAP spool system for external output management systems (OMS). The Papyrus XOM Adapter communicates with the XOM interface of SAP to receive output from on-line, ad-hoc or batch SAP applications for processing and control of SAP jobs and returns job state information to SAP.
      Benefits of the Papyrus XOM Adapter are:
      • Transparent status exchange between Papyrus and SAP: Document generation is "Completed", in "Error", "Waiting", "Running" or "Held".
      • Consistent interfaces using the SAP standard interface XOM for data exchange in the generic format XMI (XML meta data interchange)
      • Centralized management and control - in case of problems the administrator only has to work at a central point in the Papyrus UI
      • It is the perfect tool for planning distributed output strategy l The XOM Adapter can easily be incorporated into the Papyrus workflow
    2. RDI: raw data interface
      Papyrus can be connected via the SAPscript Raw Data Interface (RDI) for independent formatting and postprocessing including special purposes such as postage optimization. This interface contains all R/3 forms data, but no layout information such as font or page size. Document data is formatted and managed by Papyrus outside R/3. The raw data interface is a certified interface which provides a high -quality external system connection.
      A typical Papyrus architecture integration used an Adapter to receive the SAP data and then invokes automatically DocEXEC for document formatting and subsequent Papyrus Server modules to output the desired document format.
    3. Archive integration
      ArchiveLink is a service integrated in the SAP Web Application Server for linking archived documents and the application documents entered in the SAP system. Linking documents according to content guarantees long term easy access to the documents. The SAP UI enables a direct display of the stored documents. Search for documents by attributes is also supported. This replaces time consuming processes such as making copies of originals, searching for procedure-related information, etc. With the Papyrus HTTP/REST interface, Papyrus offers an interface matching SAP's archive purposes.
    4. Integration of the Papyrus UI with the SAP UI
      Typically, the Papyrus Business Correspondence solution will run in an iframe within the SAP NetWeaver application. The Papyrus platform will communicate at the back end with bi-directional WebServices to exchange data. E.g. a user triggers a business event in SAP which communicates over SOAP Webservices with the Papyrus SOAP Adapter. This can be used to send the applicable letter templates from Papyrus to SAP for presentation in the SAP UI. When a Template is being selected (can be automated) it will be communicated back to Papyrus via a SOAP message. This event triggers an update of the Papyrus UI (e.g. new template instantiated and document loaded) which will be shown in the Papyrus iframe of the SAP UI.

      Users will be automatically logged-in to Papyrus using the single sign-on techniques offered by Papyrus LDAP Adapter. The business user gets the full word processor 'Papyrus Client’ presented in the iframe and can modify certain paragraphs depending on the user's authorization. When the user completes the task in SAP an event will be sent to Papyrus (e.g. 'complete' or 'sent') and Papyrus will not only process the Letter, doing the full multi-channel output management using the Document Pool, but will also notify SAP via Webservices about the status.

Enterprise Application Integration

Papyrus solutions interface with any business system, as well as back-office users, by leveraging Service-oriented Architecture (SOA) to flexibly integrate via loose coupling and configuration without without hard-coded interfaces.

Click to read case study

File & Messaging

A broad variety of Papyrus Adapters connect the document system with business application data from any legacy or mainstream system or application.

Read More

Click to read case study

Type Manager

Simple user and application access to query data from non-Papyrus databases, with native connection to SQL Server, Oracle and DB/2 and ODBC for other databases

Read More

Click to read case study

Device and
Service Integration

The REST Adapter is an interface that allows communication with web services. Applications use web services via the REST Adapter using JSON for data transfer

Read More

Click to read case study

Guidewire, SAP

Papyrus Software always delivered an open platform approach to facilitate the integration with other core business systems like Salesforce, Guidewire and SAP.

Read More