By Brian Hague • Friday, December 9
Monday, September 12
By Ekatarina Mitova • Friday, June 24
By Dale Ragan • Monday, June 20
By Concur Travel • Friday, April 1
By Sarra Loew • Friday, March 18
By Henry Yamamoto • Wednesday, March 16
By Concur Expense • Tuesday, March 15
Recently, the Concur Developer Center has gone through some significant UI changes. As the amount of developer content and resources has grown, the UI has become a more important component when delivering developer documentation. This holds true across other documentation sites as well. See how Stripe separates content from code in their 3-column layout, or how Firebase organizes their documentation by platform. In both instances, the UI plays a major role in effectively communicating ideas to developers.
Updates to Concur’s Receipts and Auth API
Expenses Analyzer for Concur that runs on SAP HANA Cloud Platform
Expenses Analyzer for Concur is a sample extension application for Concur written in Java, that runs on SAP HANA Cloud Platform and uses a HANA database. The purpose of the application is to show you analytical information about all expenses in your Concur company.
ContainerDays in Boston
As an “open space conference” for DevOps community, ContainerDays Boston mixed presentational sessions with many participant-driven idea sharing, project demos, workshops into two days “unconference” schedule. At ContainerDays, Dale, Campbell, and Weiteng had chances to exchange our experience of container technology and how we built immutable infrastructure at Concur Technologies with other participants. Dale also had an amazing interview with Beth Parizeau from TechTarget, because we took the opportunity to get on the stage in one of the open space sessions. The article of interview is (Tech firms roll out Kubernetes in production).
Travel Profile 1.0 Deprecated
Effective May 1, 2016, the Travel Profile 1.0 API will be deprecated. Issues will continue to be addressed for this API until Nov. 1, 2016. After that date, no new issues will be addressed and the API will be retired. Therefore, we encourage all current users to migrate to version 2.0 as soon as possible. Please note that after the API is in a retired state and there are three consecutive months of inactivity, the API will be decommissioned and no longer available.