Integration services The recommended way to communicate with Tempus Serva is through the webservice interface (REST). Regardless of you are using the scheduled import services or the webservice interface, all restrictions from the solution models apply. Scheduled data imports The services runs in the context of a user (static), that can have restricted access just as any other user. Database connection / SQL Databases fields are mapped to solution fields by their SQL names. The SQL import allows for incremential imports, by adding a datetime filter on the records extracted. Connections for the remote database is set up in:  Designer > Integration > DB Connections CSV file import CSV imports are handled much in the same way as SQL connections using af CSV database driver. The differences are Use the filename as substitute for the table name Files have to be placed in the folder set by the configuration:  folderIntegrationCSV Support for very simple WHERE clauses No support for aggregate functions Parsing XML data files XML fields are mapped to solution fields by xpath expressions. XML integration also handles task splitting and handling. Each file is split into multiple smaller requests, that are logged and handled individually. In that way an error in a single line, will not prevent the complete batch from executing. The task split is done by an xpath expression. Files are split in the following folder structure Tasks that are  awaiting  processing Tasks that have been processed Tasks processed with  succes Tasks processed with  errors This allows for easy resubmission of problem data ("Tasks processed with errors"), by copying the file back to the preocessing folder ("Tasks awaiting processing"). Files have to be placed in the folder set by the configuration:  folderIntegrationXML Converting emails to data The email import converts new emails sent to a certain account. A few special email "values" can be mapped to solution fields Email: Senders address Subject: Email subject title line (text) Content: Text payload in email (rich text) Attatchments: Files attached to the email After processing the emails they are marked as read at the server - regardless of succes/error status. Reprocessing can be invoked by changing the read status of the email in question. Content source (aka CMS data delivery) The content delivery service can serve any view for external systems (for example: your website). The content interface serves in different formats (json,html,xml), and provides a caching mechanism too. Setting up a content source THIS ARTICLE IS UNDER DEVELOPMENT Many parameters are straight forward Related solution Max cache age Is active Unique NAME This is the calling name of the interface, that must be provided accessing the content service. Example for calling the view  myview .../cmsinterface?q=myview& ... Query command Relevant commands include General records list: List of records show: Single record HTML formatted views heat: Heatmaps gant: Gant charts xtab: Pivot tables calm: Calendar Query parameters Parameters are provided without URL encoding QUERY_FIELD_1=TITEL&QUERY_OPERATOR_1=8&QUERY_VALUE_1=Hello&QUERY_SHOWFIELD=TITEL StatusID DEADLINE Procedure for easy parameter setup Build views in frontend. Activate the link and copy the URL ´Remove unneeded parameters command SagID QUERY_NEW Possible parameters QUERY_FIELD_n Part of the search/filter. The field to filter by. QUERY_OPERATOR_n Part of the search/filter. The way to filter. Full list  Dashboard widget configuration QUERY_VALUE_n Part of the search/filter. The value to filter by. QUERY_SHOWFIELD The fields to show in the list, separated by space. QUERY_PageSize Number of records to show pr page. QUERY_PageOffset The page number to show. QUERY_SortOrder The field to sort ascending by. Use either this or SortOrderDesc. QUERY_SortOrderDesc The field to sort descending by. Use either this or SortOrder. QUERY_Grouping The field to group records by. QUERY_GroupingDesc   Dynamic parameter This specifies a parameter that will be set by the value provided in the  v  parameter. Example: Using this interface Unique NAME: mylist Query command: list Dynamic parameter: QUERY_PageOffset Making a call to .../cmsinterface?q=mylist&v=2 Will fetch a list of data and display page 2, because  2  is injected into  QUERY_PageOffset . Parameters and values are injected directly into the http request. Note: Using the "show" command the variable will ALLWAYS get mapped to "DataID" Using a content source Calling the  cmsinterface  servlet will provide you with an overview on how to use it. Example: https://www.acme.com/TempusServa/cmsinterface The interface requires just the name of the source, but additional parameters can be provided. Parameters q : Name of the interface (required) This name must match "Unique NAME" f : Format of the result (optional) Valid values: html json xml v : Parameter for dynamic values (optional) The value will be substituted to the parameter in "Dynamic parameter" Example: https://www.acme.com/TempusServa/cmsinterface?q=mysource&f=json Troubleshooting THIS ARTICLE IS UNDER DEVELOPMENT Configuration caching For performance reasons information about the content sources is kept cached. Adding or changing sources will propegate automatically : You will need to clear the system cache to pick the changes. Parameter encoding Note that URL's copied from a browser address bar are often encoded in HTML format. The content will not decode values and request strings, so all encoded strings will fail. Consuming a Content Source CMS content provider The CMS connector will allow CMS systems to extract information from a TempusServa system, and display it inline in other pages. Example: Data extracted from the Tempus Serva connector http://alpha.tempusserva.dk/TempusServa/cmsinterface?q=examdates The final result inside a page in our website http://tempusserva.dk/site/index.php/da/eksamensdatoer Notes on usage A CMS system is no requirement and static HTML files will work too. The TS backend will not be slowed because all content is cached in the connector (configurable) Connectors have NO influence on licensing Tempus Serva setup (provider) Frontend Make the request that suits your needs Filters and parameters Sorting / grouping Fields to display Fields to display Page size Save the view Click on the view and copy the parameters Backend Check that anonumous users have the right permissions Note the interface will only allow READ operations Go to "Integration" > "Content connector" Add new element Give the connector a unique name (CONNECTOR_NAME>) Choose solution and set command type (as seen in the "command" parameter in the URL) Paste alle parameters from the URL above Optionally add other settings like Language and Stylesheet Optionally define a variable that the "v" parameter will be mapped to (OPTIONAL_VARIABLE) Test the new connector URL format http://myserver.dk/TS/ cmsinterface?q= http://myserver.dk/TS/ cmsinterface?q= &v= Example URL's http://myserver.dk/TS/ cmsinterface?q=customerList&v=3 http://myserver.dk/TS/ cmsinterface?q=longActivityList&v=3 http://myserver.dk/TS/ cmsinterface?q=singleActivityById&v=782382386 Note that links between lists and single items will first be supported by Q2/2014. CMS system setup (consumer) Option: Client rendering The following procedure Make sure JQuery is available (normal JS can do the job) Insert content placeholder and Javascript code Note: The URL above reflects the use of a proxy script (see below). Option: Server side include Insert code that fetches the content echo file_get_contents("http://myserver.com/TS/cmsinterface?q=examdates") In some cases you might want to remove the wrapper, header etc. from normal pages. This is done by adding the AjaxMode parameter. echo file_get_contents("https://talentpiper.com/demo/mainpublic?command=dk.p2e.blanket.codeunit.common.PagePublicRecordsListAndShow&AjaxMode=1"); Note: The URL above reflects the direct use of interface. Overcoming CORS protection I cases where the TempusServa server and the CMS system is on different domains (ex. acme.shared.com and cms.acme.com), browsers will prevent pages from accessing content from other servers. Two options exist Use server side includes (ok, but not supported everywhere) Set up a mini proxyserver A mini proxyserver written i PHP is very simple (aspx/jsp will have similar features) and placed on the CMS side.