Retrieves the full set of information for the report. Includes the Report Header, Entry, Attendee, Itemization and Allocation details.
Some elements will appear only if the OAuth consumer has the Web Services Admin role. These include: The ReportKey element, the employee’s credit card information, and the employee’s bank account information, VAT information, Journal entries. Connectors that utilize this information go through a review process with SAP Concur that includes verification of secure data handling.
GET list of reports can be found here
| Parameter | Required/Optional | Description |
|---|---|---|
| reportId | required | The identifier for the desired report. |
Example: https://www.concursolutions.com/api/expense/expensereport/v2.0/report/{reportId}
URI Source: The ReportId is returned in the ReportId element of the Get List of Reports function
Authorization header with OAuth token for valid SAP Concur user. The OAuth consumer must have one of the following user roles in SAP Concur: Company Administrator or Web Services Administrator for Professional, or Can Administer for Standard. These roles allow the user to manage data for the entire company.
application/xml
application/xml
This request will return a ReportDetails parent element.
| Element | Description |
|---|---|
| UserLoginID | The user ID of the report owner. Maximum 128 characters. |
| EmployeeName | The name of the employee who created the report. Maximum 66 characters. |
| ReportID | The unique identifier for the report, which appears in the Concur Expense UI. Maximum 32 character varchar. |
| ReportKey | The unencrypted unique identifier for the report, that appears on the report header. The element appears only if the OAuth consumer has the Web Services Admin role in SAP Concur. Maximum 48 characters. |
| ReportName | The name of the report. Maximum 40 characters. |
| Purpose | The information from the Business Purpose field. |
| ReportDate | The date from the report header. Format: YYYY-MM-DDThh:mm:ss |
| CreationDate | The date the report was created. Format: YYYY-MM-DDThh:mm:ss |
| SubmitDate | The date the report was submitted. Maximum 10 characters. |
| PaidDate | The date the report was extracted for payment. This element has an attribute named i:nil. If the value for this element is null, the i:nil attribute will be set to true. Format: YYYY-MM-DDThh:mm:ss |
| CurrencyCode | The 3-letter ISO 4217 currency code for the expense report currency. The expense report currency is defined as the report creator’s default reimbursement currency. |
| ReportTotal | The total amount of the report. Maximum 23 characters. |
| PersonalExpenses | The total amount of expenses marked as personal. Maximum 23 characters. |
| AmountDueEmployee | The total amount due to the employee for the report. Maximum 23 characters. |
| AmountDueCompanyCard | The total amount due to the company card for the report. Maximum 23 characters. |
| TotalClaimedAmount | The total amount of all non-personal expenses in the report. Maximum 23 characters. |
| TotalApprovedAmount | The total amount of approved expenses in the report. Maximum 23 characters. |
| ApprovalStatusCode | The approval status code for the report. |
| ApprovalStatusName | The approval status name for the report. |
| PaymentStatusCode | The unique identifier for the payment status of the report. |
| PaymentStatusName | The payment status of the report. |
| OrgUnit1 through OrgUnit6 | The details from the Org Unit custom fields. These may not have data, depending on configuration. Maximum 48 characters for each field. |
| Custom1 through Custom20 | The details from the Custom fields. These may not have data, depending on configuration. If report owner information is stored in these fields, it may be outdated. Refer to the ReportOwner parent element for the current owner information. Refer to the Custom Fields Child Elements table for more information. |
| LedgerName | The name of the expense report ledger. Maximum 20 characters. |
| PolicyID | The unique identifier of the policy that applies to this report. Maximum 64 characters. |
| EverSentBack | Whether the report has ever been sent back to the employee. Format: Y/N |
| HasException | Whether the report has exceptions. Format: Y/N |
| WorkflowActionURL | The URL to post a workflow action to the report using the Post Report Workflow Action function. |
| ExpenseEntriesList | This parent element has an ExpenseEntry child element for each entry. Refer to the ExpenseEntry elements table for more information. |
| ReportImageURL | The URL to access the image associated with the report. This URL is valid for 30 minutes after the web service call. |
| Country | The report country. Maximum 2 characters. Format: The ISO 3166-1 alpha-2 country code. Example: United States is US. |
| CountrySubdivision | The report country subdivision. Format: ISO 3166-2:2007 country subdivision. |
| ProcessingPaymentDate | The date that the report completed all approvals and was ready to be extracted for payment. Format: YYYY-MM-DD |
| ReceiptsReceived | If Y, then this report has its receipt receipt confirmed by the Expense Processor. Format: Y/N |
| ReportOwner | This parent element includes details about the employee who is the report owner. It saves the caller from calling the Get User Information function to get employee information commonly used in accounting integration. The ReportOwner element includes the most recent information about the report owner, at the time the report is requested. |
| EmployeeBankAccount | This parent element includes the bank account data found on the Bank Information page in Profile. This data is used in Payment System integrations where the payment system reimburses the employee via this bank account. |
| Element | Description |
|---|---|
| ReportEntryID | The ID of the report entry. Maximum 13 characters. |
| ExpenseTypeID | The expense type ID for the expense entry. Expense Type IDs are returned in the ExpKey element by the Get Expense Group Configuration endpoint. |
| ExpenseTypeName | The expense type name. Maximum 64 characters. |
| SpendCategory | The spend category specified for this expense type. Varies by client, used in reporting. |
| PaymentTypeCode | The code for the payment type. Maximum 4 characters. |
| PaymentTypeName | The name for the payment type. Maximum 80 characters. |
| TransactionDate | The date of the expense entry. Maximum 10 characters. Format: YYYY-MM-DD |
| TransactionCurrencyName | The name of the transaction currency. Example: US, Dollar |
| ExchangeRate | The exchange rate that applies to the entry. Maximum 23 characters. |
| TransactionAmount | The amount of the expense entry in the original transaction currency. Maximum 23 characters. |
| PostedAmount | The amount of the expense entry in the user’s reimbursement currency. The user’s reimbursement currency is returned in the CrnCode element for the report. Maximum 23 characters. |
| ApprovedAmount | The approved amount of the expense entry in the user’s reimbursement currency.The user’s reimbursement currency is returned in the CrnCode element for the report. Maximum 23 characters. |
| BusinessPurpose | The text from the Business Purpose field of the entry. Maximum 64 characters. |
| VendorDescription | The vendor name of the expense entry, which can be entered manually by the user or imported from the card transaction Merchant Name field. Maximum 64 characters. |
| LocationName | The location for the expense entry, usually the city name. |
| LocationSubdivision | The location’s State, Province, or Country Subdivision. Maximum 6 characters. |
| LocationCountry | The location’s Country. Maximum 2 characters. |
| OrgUnit1 through OrgUnit6 | The details from the Org Unit custom fields. These may not have data, depending on configuration. Maximum 48 characters for each field. |
| Custom1 through Custom40 | The details from the Custom fields. These may not have data, depending on configuration. Refer to the Custom Fields elements table for more information. |
| FormID | The ID for the expense entry form. |
| EntryImageID | The unique identifier for the image associated with the entry. |
| HasVat | Whether the entry contains VAT data. Maximum 1 character. Format: Y/N |
| HasComments | Whether the expense entry has comments. Maximum 1 character. Format: Y/N |
| CommentCount | The number of comments associated with the expense entry. |
| IsItemized | Whether the expense entry is itemized. Maximum 1 character. Format: Y/N |
| HasExceptions | Whether the expense entry has exceptions. Maximum 1 character. Format: Y/N |
| IsPersonal | Whether the expense entry is marked as personal. Maximum 1 character. Format: Y/N |
| HasAttendees | Whether the expense entry has attendees. Maximum 1 character. Format: Y/N |
| HasAllocation | Defines the amount of allocations for the expense. Maximum 1 character. Possible values are: P, for partial allocation, F, for full allocation, or N, for no allocation. |
| IsCreditCardCharge | Whether the expense came from a credit card feed. Maximum 1 character. Format: Y/N |
| IsPersonalCardCharge | Whether the expense came from a personal card feed. Maximum 1 character. Format: Y/N |
| ReceiptRequired | Whether the original receipt is required for the entry. Maximum 1 character. Format: Y/N |
| ImageRequired | Whether a receipt image is required for the entry. Maximum 1 character. Format: Y/N |
| E-ReceiptID | The ID for the attached e-receipt, if available. |
| LastModifiedDate | The date the expense entry was last changed. Maximum 19 characters. Format: YYYY-MM-DDThh:mm:ss |
| ItemizationsList | The list of itemizations for the expense entry. This parent element will have at least one Itemization child element. If the expense entry is not itemized, the Itemization will contain the same values as the entry. If the expense entry has itemizations, there will be one Itemization child element for each itemization. Refer to the Itemization elements table for more information. NOTE: There are a few rare cases where the ItemizationsList will be null. This happens when a report entry has a payment type code that is not IBCP with offsets or CBCP and there is a Regular or Child expense entry with an Approved Amount equal to zero. The expense entry will have a Null ItemizationsList. |
| ReportEntryVendorName | Vendor name the employee selected from the Vendor list field. Maximum 64 characters. |
| ReportEntryReceiptReceived | If Y, then this entry has been marked as reviewed by a processor. Maximum 1 character. Format: Y/N |
| ReportEntryReceiptType | Maximum 1 character. One of these: T = tax receipt R= regular receipt N = no receipt |
| CardTransaction | This parent element includes the card transaction data found in the card transaction associated to this expense entry. This data is used in Payment System integrations where the payment system reimburses the card issuer for the indicated card account. Refer to the CardTransaction elements table. |
| ExpensePay | Whether the entry was paid using the Expense Pay service. This element has a value if the report has reached the Processing Payment workflow step. Format: Yes/No |
| Element | Description |
|---|---|
| ItemType | The type of itemization. If the expense entry does not have any itemizations, this will be set to Regular. If the expense entry contains itemizations, each one will be set to Child. |
| ItemizationID | The unique identifier for the itemization. Maximum 19 characters. |
| ExpenseTypeID | The expense type ID for the itemization. |
| ExpenseTypeName | The expense type for the itemization. Maximum 64 characters. |
| TransactionDate | The date of the transaction. Maximum 10 characters. Format: YYYY-MM-DD |
| TransactionAmount | The amount for the itemization in the expense currency. Maximum 23 characters. |
| PostedAmount | The amount for the itemization in the user’s reimbursement currency. The user’s reimbursement currency is returned in the CrnCode element for the report. Maximum 23 characters. |
| ApprovedAmount | The approved amount of the itemization in the user’s reimbursement currency. The user’s reimbursement currency is returned in the CrnCode element for the report. Maximum 23 characters. |
| BusinessPurpose | The business purpose field from the report header. |
| OrgUnit1 through OrgUnit6 | The details from the Org Unit custom fields. These may not have data, depending on configuration. Maximum 48 characters for each field. |
| Custom1 through Custom40 | The custom fields associated with the itemization. These may not have data, depending on your configuration. Refer to the Custom Fields elements table for more information. |
| Value | The value in the custom field. Maximum 48 characters. |
| Code | Custom list fields will include the list item code in this element. |
| HasComments | Whether the itemization has comments. Maximum 1 character. Format: Y/N |
| CommentCount | The number of comments associated with the itemization. |
| IsPersonal | Whether the itemization is personal. Maximum 1 character. Format: Y/N |
| LastModified | The UTC date when the itemization was last modified. Maximum 19 characters. Format: YYYY-MM-DDThh:mm:ss |
| AttendeesList | This parent element contains one Attendee element for each associated attendee. Refer to the Attendee elements table for more information. |
| AllocationsList | This parent element contains at least one Allocation element. It will contain multiple Allocation elements if there are multiple allocations for the itemization. Refer to the Allocation elements table. |
| Element | Description |
|---|---|
| AttendeeType | The type of attendee. Maximum 40 characters. |
| FirstName | The attendee’s first name. Maximum 50 characters. |
| LastName | The attendee’s last name. Maximum 132 characters. |
| Company | The attendee’s company name. Maximum 150 characters. |
| Title | The attendee’s title. Maximum 32 characters. |
| ExternalID | The unique identifier for the attendee, managed outside SAP Concur. Maximum 48 characters. |
| Custom1 through Custom20 | The details from the custom fields. These may not have data, depending on configuration. Refer to the Custom Fields elements table for more information. |
| HasExceptionsPrevYear | Whether the attendee has exceptions in the previous year, based on yearly total limits for attendees. Maximum 1 character. Format: Y/N |
| HasExceptionsYTD | Whether the attendee has exceptions in the current year, based on yearly total limits for attendees. Maximum 1 character. Format: Y/N |
| IsDeleted | Whether the attendee is marked as deleted. Maximum 1 character. Format: Y/N |
| OwnerName | The name of the employee that owns the attendee record. |
| TotalAmountPrevYear | The total amount spent on the attendee in the previous calendar year. |
| TotalAmountYTD | The total amount spent on the attendee in the current calendar year. |
| VersionNumber | The attendee’s version number. |
| AttendeeID | Attendee unique identifier within SAP Concur. |
| AttendeeTypeCode | The unique identifier for the attendee type. |
| AttendeeOwnerID | The unique identifier for the person or system that owns the attendee. |
| CurrencyCode | The 3-letter ISO 4217 currency code for attendee related amounts. |
| Element | Description |
|---|---|
| AllocationID | The unique alphanumeric identifier for the allocation. Maximum 13 characters. |
| Percentage | The percentage of the expense that is included in this allocation. Maximum 11 characters. |
| AccountCode1 | The primary accounting code assigned to the expense type associated with this allocation. Typically, expense types have only this primary account code. |
| AccountCode2 | The secondary or alternative accounting code assigned to the expense type associated with this allocation. In rare cases some expense types include this accounting code to handle special cases. One example of these special cases is when using travel allowance, where one expense would use the primary account code for the allowed amount, and the alternative account code for the overage. Another example is personal use of a company car. Refer to the Expense: Account Codes Setup Guide for more information on how Concur Expense determines which accounting codes to use. |
| Custom1 through Custom20 | The custom fields associated with the allocation. These may not have data, depending on your configuration. Refer to the Custom Fields elements table for more information. |
| JournalEntriesList | This parent element contains at least one JournalEntry child element. It contains multiple JournalEntry elements if the allocation has multiple journal entries. Refer to the JournalEntry elements table for more information. |
| VATDataList | This parent element contains one VATData element for each VAT line item. This element will be empty if there are no VAT line items. Refer to the VATData elements table for more information. |
| Element | Description |
|---|---|
| JournalID | Unique identifier for the journal entry. |
| PayerPaymentTypeName | Payer payment type. Maximum 64 characters. One of these: Company = Company Employee = Employee Payment Type for the Credit Card Payment Type |
| PayerPaymentTypeCode | Payment code name for the payer. Maximum 80 characters. |
| PayeePaymentTypeName | Payee payment type. Maximum 64 characters. One of these: Company = Company Employee = Employee Payment Type for the Credit Card Payment Type |
| PayeePaymentCode | Payment code name for the payee. Maximum 80 characters. |
| AccountCode | The account code Concur Expense determines should apply to this journal entry. For journal entries associated to an allocation, Concur Expense uses the business logic described in the Expense: Account Codes Setup Guide to determine whether the primary or secondary account code should apply. When there is no allocation associated to the journal entry, Concur Expense uses clearing account codes for Credit Card and Cash Advance for personal use of a company paid expense or a cash advance issued to an employee respectively. Maximum 48 characters. NOTE: The developer should almost always use this accounting code when creating financial transactions in financial systems. In some situations a developer may need to use the accounting codes in the Allocation parent element. |
| DebitOrCredit | Maximum 2 characters. Either: DR = Debit CR = Credit |
| Amount | Value, as credit or debit, of the amount to be exchanged between the payer and payee for this expense account code (not an absolute value) Maximum 23 characters. EXAMPLES: Value of zero, credit, or debit, as the following: 0 (Zero) “0” + (Plus / Debit) “+50.00” - (Minus / Credit) “-50.00” |
| JobRunKey | Either the unique identifier for job run for the accounting extract that processed this journal, or a static value indicating the journal was processed by Manual Pay, Expense Pay, or some other system. |
| Element | Description |
|---|---|
| TaxName | Tax authority name. Maximum 50 characters. |
| TaxAuthorityLabel | 5-digit code that appears on the expense entry pages. Maximum 5 characters. |
| TaxTransactionAmount | Calculated tax amount for this expense in the spend currency. Maximum 23 characters. |
| TaxPostedAmount | Calculated tax amount for this expense entry in the reimbursement currency. Maximum 23 characters. |
| Source | Specifies how the tax data was derived. Maximum 4 characters. One of these: CARD = Provided from company card USER = Entered by employee SYST = Calculated by system PROC = Entered by processor |
| TaxReclaimTransactionAmount | Calculated amount of tax eligible for reclaim in the spend currency. Maximum 23 characters. |
| TaxReclaimPostedAmount | Calculated amount of tax eligible for reclaim in the reimbursement currency. Maximum 23 characters. |
| Element | Description |
|---|---|
| AccountNumber | Credit card number used for this expense. This value is encrypted in the response. Maximum 255 characters. |
| CardDescription | The name on the credit card used for this expense. Maximum 255 characters. |
| CardTypeCode | Type of credit card. |
| TransactionReferenceNumber | Reference number from the credit card vendor. Maximum 64 characters. |
| TransactionCCTType | Transaction type supplied by card vendor. Maximum 3 characters. One of these: ANF = Annual Fees CAV = Cash Advance CCF = Cash and Check Fees CHG = Other Bank Charges and Fees FNC = Finance Charges LAF = Late Fees NSF = Insufficient Funds Check Fees PAY = Payment RPE = Credit Card Transaction |
| TransactionID | Calculated value assigned to this card entry during the import process. Maximum 32 characters. |
| TransactionAmount | Amount of the charge in the spend currency. Maximum 23 characters. |
| TaxAmount | Amount of tax on the transaction amount (if provided by card vendor). Maximum 23 characters. |
| TransactionAlphaCode | Currency code for the spend currency. Maximum 3 characters. Format: ISO 4217 3 digit alpha code |
| PostedAmount | Amount of the charge in the billing currency of the card. Maximum 23 characters. |
| PostedAlphaCode | Currency code for the card billing currency. Maximum 3 characters. Format: ISO 4217 3 digit alpha code |
| TransactionDate | Date the charge was made at the merchant. Maximum 10 characters. |
| PostedDate | Date the charge was posted to the credit card account. Maximum 10 characters. |
| Description | Description of the charge from the merchant. Maximum 42 characters. |
| MasterCardCode | Merchant code sent from the credit card vendor. Maximum 5 characters. |
| TransactionMerchantName | Name of the merchant. Maximum 50 characters. |
| MerchantCity | Merchant city. Maximum 40 characters. |
| MerchantState | Merchant State/Province. Maximum 32 characters. |
| MerchantCountryCode | Merchant country location code. Format: 2 digit alpha code |
| MerchantReferenceNumber | Merchant reference number passed from the merchant to the card. Maximum 15 characters. |
| ExchangeRateFromBillingToEmployeeCurrency | Currency exchange rate used between the credit card billing currency and the employee’s reimbursement currency. Maximum 23 characters. |
| BillingAmount | Amount due to the company card from the employee or company (depending on who is responsible for the bill) for this detail row. Maximum 23 characters. |
| AccountNumberLastSegment | The last 4 digits of the Card Account. |
| Element | Description |
|---|---|
| Type | The custom field type. Will be one of the following: Amount, Boolean, ConnectedList, Date, Integer, List, Number, Text |
| Value | The value in the custom field. Maximum 48 characters. |
| Code | Custom list fields will include the list item code in this element. |
| Element | Description |
|---|---|
| EmployeeCustom21 | The report owner’s group ID. Maximum 48 characters. |
| EmployeeID | Employee ID often also serves as the employee’s Vendor ID for AP system integrations or Payroll ID for Payroll integrations. Maximum 48 characters. |
| EmployeeOrgUnit1 through EmployeeOrgUnit6 | The report owner’s organizational unit information. Maximum 48 characters for each field. |
| FirstName | The report owner’s first name. Maximum 32 characters. |
| LastName | The report owner’s last name. Maximum 32 characters. |
| MiddleInitial | The report owner’s middle initial. Maximum 1 character. |
| ReimbursementMethodCode | The report owner’s reimbursement method code, as defined in the employee’s Profile. |
| Element | Description |
|---|---|
| BankNumber | The bank identification number entered on the Bank Information page. Maximum 11 characters. |
| BankName | The bank name entered on the Bank Information page. Maximum 48 characters. |
| BranchLocation | The branch location entered on the Bank Information page. Maximum 30 characters. |
| AccountNumber | The bank account number entered on the Bank Information page. Maximum 100 characters. |
| AccountName | The name on the account entered on the Bank Information page. |
| PostalAddressLine1 | The postal address line 1 entered on the Bank Information page. Maximum 48 characters. |
| PostalAddressLine2 | The postal address line 2 entered on the Bank Information page. Maximum 48 characters. |
| PostalAddressCity | The postal address city entered on the Bank Information page. Maximum 24 characters. |
| PostalAddressRegion | The postal address region entered on the Bank Information page. Maximum 24 characters. |
| PostalAddressCode | The postal address code entered on the Bank Information page. Maximum 20 characters. |
| PostalAddressCountry | The postal address country entered on the Bank Information page. Maximum 2 characters. Format: The ISO 3166-1 alpha-2 country code. Example: United States is US. |
GET https://www.concursolutions.com/api/expense/expensereport/v2.0/report/n6ujbuLd1Arwe45lT7As3ThJYJf2dAsrrEW HTTP/1.1
Authorization: OAuth {access token}
...


AMAZING PEOPLE ARE MAKING AMAZING DESIGNS IN A FUN ENVIRONMENT.
When you work with us you are part of a team of committed collaborators. All aspects of our software development process are intergrated, interactive and agile.
Our approach unifies design, development and product management to create exceptional products.
We start each project by understanding your business goals, the user's needs and the product requirements.
Then we help translate them into effective elegant solutions.
Before we sign a contract or write a line of code our team will spend the necessary time needed to understand your product vision.
The outcome of this scoping session is a proposal or high-level statement of work.
based on your requirements, we can provide a complete offering or just the pieces you need.
Our design practice offers a full range of services including brand
strategy, interaction and visual design and user experience testing.
Throughout your project, our designers create and implement visual design and
workflows, solicit user feedback and work with you to make sure what gets built is
what is needed.
All engineers are fluent in the latest enterprise, mobile and web
development technologies.
They collaborate with your team to write, and
improve code on a daily basis, using proven practices such as test-driven
development and pair programming.
Planning and development is iterative. Because we are constantly
coding and testing, the products we build are always ready to go live.
This iterative process allows for changes as business requirements evolve.
Created a mosaic for "Culture Animations"
Created a web page for "Ontario Security"
Created a mosaic for "DreamWorks Animations"
Created a web app for "Stock Analytics"
Created a landing page for "Travel this way"
Created a web form for "Julia's Wordpress"
Created a web page for "Burned Bistro"
Created a web page for "Giraffe Restaurant"


Coutinho stars as Brazil outclass South Korea in Abu Dhabi friendly
by BeSoccerBrazil ended a run of five games without a win by easing to a 3-0 victory over South Korea in a friendly in Abu Dhabi on Tuesday with Philippe Coutinho scoring the pick of the goals.
Coutinho, currently on loan at Bayern Munich from Barcelona, curled a free-kick from 22 yards high into the net to put Brazil 2-0 up after 35 minutes.
Before that he had played a part in the opener, producing some delightful footwork to pick out Renan Lodi, whose cross from the left was headed in from close range by AC Milan midfielder Lucas Paqueta.
Atletico Madrid left-back Lodi, 21, also set up the third goal which arrived shortly after half-time, his low delivery picking out Danilo to score with a first-time drive from just outside the area.
It is a first victory in six friendly outings for the Selecao since their triumph at the Copa America on home soil in July.
All of those matches have been played on neutral ground, with this match coming after a 1-0 defeat at the hands of Argentina in Saudi Arabia last Friday.
Featured links
- Madrid now waits for Neymar
- The latest football transfers news and rumours
- Who has the most free-kicks goals: Messi or Cristiano?
- Luis Enrique returns to Spain national team
Five days after a 0-0 draw in Lebanon in a 2022 World Cup qualifier, South Korea were outclassed here, despite the presence of Tottenham Hotspur star Son Heung-min in their line-up.
Once again Neymar was absent for Brazil, with the world's most expensive player having stayed behind at Paris Saint-Germain to work on his fitness after suffering an injury playing for his country in a 1-1 draw with Nigeria in Singapore a month ago.
Perhaps his absence helped explain why the Mohammed bin Zayed Stadium was barely half full for the game.
Coach Tite made five changes to his starting line-up following the Argentina defeat, with Lodi and Coutinho coming into the side along with PSG centre-back Marquinhos, Liverpool midfielder Fabinho and Everton forward Richarlison.
Aston Villa's Douglas Luiz was handed his debut as a late substitute in what is a reassuring victory for Brazil before they start South American World Cup qualifying next March.


@if($errors->any() && $errors->first() != 1)
{{$errors->first()}}
@endif
| Date process |
Buyer name |
Buyer email |
Process |
store name |
Price |
Commission Website |
current Balance website |
current Balance store |
@foreach($invoices as $invoice)
| {{$invoice->created_at}} |
{{$invoice->user_name}} |
{{$invoice->email}} |
Was purchased |
{{$invoice->store_name}} |
{{$invoice->amount}} |
{{$invoice->commissionweb}} |
amount*$invoice->commissionweb/100;?>
{{$balanceadmin}} |
amount-$balanceadmin;?>
{{$balancestore}} |
@endforeach
@include('admincp.footer')


This tutorial assumes that you are familiar with object oriented programing. It also helps to know html/css, which you can learn online on your own.
Though we only meet for 90 minutes a week, it will take many people at least 10 hours each week (for five weeks) to become famililar enough with these skills to pull a project off.
Whether this is your first stack or one of many, Django is a good stack to master for applications that work with data. Read more about pythons powerful data science libraries like NumPy, NLTK, SciPy, Pandas...


You’re scanning through Twitter, and you see an interesting headline - “7 Ways to Improve (insert desired result).” Perfect. This established company would definitely have some useful tips for your fledgeling marketing career. You click the link and prepare for awesomeness. “Before you learn about the 7 ways, please fill out this brief nine question form, and receive the free resource!” Seriously? I travelled across the interwebs for a crappy opt-in? Exit page — find gif to describe my displeasure.
This anecdote describes many of our experiences. You’ve been promised a valuable resource, and then bombarded with a Soviet Union-intensity-level signup form. Everything from an email address, to a phone number. Maybe a blood type? It was “free,” but we knew going into it that we would have to give something. Normally an email address suffices, but there comes a point where I feel like I’m signing up for a dating service.
We all know how it works: You give something (email address), you get something free (eBook, email course, etc.) But sometimes, it just gets ridiculous. If you don’t want to give away a lot of content, I totally understand. We are all trying to make a living, but don’t pose as the Good Samaritan if you’re planning on spamming me for the next decade. Promise a free resource, provide a free resource with minimal strings attached.
Promising a free “Complete Guide to the World’s Greatest Meatloaf,” and then asking for my mailing address, work position, and pet’s middle name is just going to cause frustration. Especially if you’ve promised the resource within an apparent “no strings attached” context. Who doesn’t want to make the world’s greatest meatloaf?
The numbers don’t lie when it comes to consumers getting fed up with lengthy signup forms. This post by Corey Eridon, cites an eMarketer report that suggested 88% of people have either left a field blank, or given false information when signing up through a form. She then goes on to say, “Whether it’s due to privacy concerns or frustration, online shoppers have higher standards than ever before for a sleek and simple registration process.”
If you do choose to go the FBI background check signup form route, your content needs to be awesome. Someone who hangs around long enough to fill out sixteen boxes worth of information is expecting to be blown away by the content their receiving in exchange.
You want to know a better way to get email addresses? A better way to get people to opt-in for your newsletter? Provide A TON of free stuff. Good stuff.  This establishes trust. Trust means that you build a following that will eventually take on a bigger commitment like a Content Upgrade, which Tim Soulo talks more about in this post.
Have you ever been to a career fair? Which table was cooler? The one that gave you a ton of boring paperwork (ins and outs of the job, starting pay, etc.), or the one that handed out koozies with the paperwork? KOOZIES. YES. The people weren’t just there to hand out the boilerplate documents that they had to hand out, they also wanted you to take something with you that would remind you of them. They wanted to leave a lasting impression. Are you leaving a lasting impression on the people who follow your brand, or are you just keeping score of email signups?
In my opinion, the less demanding you look, the better. If a user feels pressured to opt-in, or doesn’t want to divulge a lot of information, they’re either going to bounce or just provide you with a bunch of false information (as the Eridon post suggested). How useful is that? Rather, you should just focus on getting SOMETHING, even if it’s only an email address.
The hardcore business guy would probably speak against offering a lot of free content, but the hardcore business guy also wants to spam your phone with solicitations. People dig generosity way more than sharpness. Obviously there is a lot of bad free content out there, but there is just as much that’s amazing.
It’s the internet, people. The content you’re offering behind your 10 section opt-in form can probably be found way easier somewhere else.
So it’s obvious that your focus should be on the value of the content you offer. If you start there, you’ll be able to eventually monetize it because users will be interested in what you’re offering, and also interested in supporting you.
Let’s pretend that they did sign up for your fancy pants PDF. What now? Show your subscribers some love! They put in the work, filled out all of the required fields, and now they should not only get your resource, but a thank you. You should also consider giving them more than what they asked for. Simply getting a signup does not guarantee long term engagement. Instigator Blog talks about the role of long-term engagement in the onboarding process, and it’s definitely worth a read.
You also have the responsibility to not spam your subscribers with “sales” emails. Having their email address, and using it wisely are two completely different things. It’s clear that they want to hear from you, but they probably only want to hear about things that pertain to the topic that they signed up for.
If you offer content on multiple topics, consider dividing the email lists up into what topic the subscriber originally signed up for. This will show the customer that you’re considerate of their interests, and it could go a long way in keeping your unsubscribes down.
There are no silver bullets to creating the perfect signup form, but there are things that can make your process seem obnoxious to users. If you’re offering valuable content for free, make sure you offer it for FREE. If you want to collect information from your users, make it a simple (voluntary) process. Provide value, and watch your subscriptions increase.


Theorem all_equal : forall x y : Empty_set, x = y. Theorem all_diff : forall x y : Empty_set, x <> y.


$ curl -H "Accept:application/atom+xml; charset=utf-8" "http://localhost:8080/wink/world" $ curl -H "Accept:application/atom+xml" "http://localhost:8080/wink/bookmarks" and much more. Please check the org.jpublish.module.wink.examples package for details.


Getting Started
Make sure you grab the lastest copy of Radio.js and include it in your project to get started.
Some basic samples to get the idea.
//create topic called changeTabEvent and subscribe myFunction radio('changeTabEvent').subscribe(myfunction); //publish to the topic changeTabEvent radio('changeTabEvent').broadcast(data); //unsubscribe myFunction from the topic changeTabEvent radio('changeTabEvent').unsubscribe(myFunction); //do all of the above in one line via chaining radio('changeTabEvent').subscribe(myFunction).broadcast(data).unsubscribe(myFunction);
radio()
Every radio call starts with the radio() method which accepts a string to set the current topic.
//creates and selects the topic to changeTabEvent radio('changeTabEvent');
.subscribe()
Add subscribers to a topic.
//subscribe callback radio('changeTabEvent').subscribe(callback); //subscribe callback with context radio('changeTabEvent').subscribe([callback,context]);
You can subscribe multiple callbacks at once.
//subscribe three callbacks at once radio('changeTabEvent').subscribe(callback, callback2, [callback3.init, callback3]); //subscribe it via chaining if you want radio('changeTabEvent').subscribe(callback).subscribe(callback2).subscribe([callback3.init, callback3]);
Callbacks with context
With Radio you can set the context of 'this' when your callback is invoked by adding your callback as an array with context. This is particularly useful if you are namespacing your project under one global object.
radio('changeTabEvent').subscribe([callback, context]);
Example that demonstrates why you may want to do this.
//your global namespaced application object var myApp = { init: function() { alert(this); this.run(); }, run: function() { //do something } } //first subscribe it without setting context //this will fail because 'this' is set to the window object radio('changeTabEvent').subscribe(myApp.init).broadcast(); //subscribe it with context. //this will work because value of 'this' is set to myApp radio('changeTabEvent').subscribe([myApp.init, myApp]).broadcast();
.broadcast()
Publish a message to all subscribers in a selected topic. All parameters get passed to the subscribers.
radio('changeTabEvent').subscribe(function(data1, data2) { //do something with data1 and data2 }); radio('changeTabEvent').broadcast(data1, data2);
.unsubscribe()
Remove subscribers from a topic.
//first subscribe a subscriber radio('changeTabEvent').subscribe(callback); //now unsubscribe it radio('changeTabEvent').unsubscribe(callback);
Remove multiples callback at once.
//unsubscribe multiple callbacks at once radio('changeTabEvent').unsubscribe(callback1, callback2, callback3);
Ender Integration
Radio support ender and provides an ender bridge. If you are using ender to consume Radio.js, just use the radio object like:
$.radio('changeTabEvent').subscribe(callback1).broadcast('test').unsubscribe(callback1);More samples can be found in the integration tests (thank you to rvagg).


This is the demo frontend for the Gamepad Recipe in the Crossbar.io IoT Cookbook.
| Connected to URL (protocol) | - |
| Joined as authid@realm | - |
| Addressing Pi with serial No.: | - |
| Pi component started (UTC) | - |
When button Left or Right Button is hit on the gamepad, this indicator is flashed.


This is the About Window of Johns Hope's FPlot. Here you can check the version of FPlot, donate money to Johns Hope Software via PayPal, or you can contact Johns Hope Software if you want to participate in the further development of Johns Hope's FPlot.
You can also instruct FPlot to check for updates regularly if you have an internet connection.


Run a function on DOMContentLoaded AKA on DOM Ready
DOMContentLoaded
Should be used to run some code that will manipulate DOM in the page
Code


Insidious: Chapter 2
Insidious: Chapter 2 is a movie starring Patrick Wilson, Rose Byrne, and Barbara Hershey. The Lamberts believe that they have defeated the spirits that have haunted their family, but they soon discover that evil is not beaten so...


Bleeding Edge Web: May 2017
Announcements
News From the Bleeding Edge
— Corey Butler (@goldglovecb)
Lightning Talk: Async Components in VueJS
— Ted Patrick (@__ted__)
The History & Future of Speaking with Machines
— Matt Buck (@techpeace)
News from the
Bleeding Edge
Browser Pop Quiz
Last check — April 26, 2017:
Browser Pop Quiz
As of May 24, 2017:
Chrome 58
Released April 19 (Same as last month)
Chrome 58 "ish":
What we missed:
Chrome Notifications
Firefox 53
Released April 19 — Release Notes (Same as last month)
Nothing major, lots of minor improvements.
Firefox 54 ships on June 13, 2017
Edge 15 (16188)
Released May 04 (Mostly Browsing Experience)
- PDF Improvements (Form Filling, Annotations, TOC)
- Application Guard (Windows Defender)
- Shared Memory & Atomics (aka Holy crap, are we're multithreading JS?)
Microsoft Edge: Motivating the Industry
Safari 10.1 (reminder... again)
Widely released March 27 — Release Notes
Translation: Minor bug fixes.
Libraries, Tools &
Frameworks
Help build your community!
A civic hackathon where we hack solutions to our community problems.
Community not your thing?
Help destroy your community!
Create an engaging visualization of how you see technology changing the future of conflict in the year 2030.
And now for something completely different...
Thanks!
←
→
/
#


{{sectionTitleLong[0]}}
The solution to the classical version of the single free particle Schrödinger equation
$$ \phi (t, \mathbf{x}) = \int \ d^3\mathbf{p} \ f(\mathbf{p}) \ e^{-iE(\mathbf{p})t + i\mathbf{p} \cdot \mathbf{x}} $$
Choose Gaussian profile
$$ f(\mathbf{p}) = \frac{1}{ (2 \pi \sigma^2)^{3/2} } e^{-\frac{(\mathbf{p} - \mathbf{\bar{p}})^2}{2 \sigma^2}} e^{-i\mathbf{p} \cdot \mathbf{\bar{x}} } $$
And Schrödinger dispersion relation
$$ E(\mathbf{p}) = \frac{ \mathbf{p}^2 }{2 m} $$
The group velocity is
$$ \mathbf{v}_g = \frac{ \mathbf{\bar{p}} }{m} $$
For $\sigma \ll 1$, the norm of the solution to the field is
$$ | \phi (t, \mathbf{x}) |^2 \simeq e^{- \sigma^2 | \mathbf{x} - \mathbf{\bar{x}} - \mathbf{v}_g t|^2} $$
The simulation is demonstrating this last equation.
Each orange dot represents a discretised point in space.
The size of the dot scales with the quantity $| \phi (t, \mathbf{x}) |^2$.
The symbols of the sliders are related to the equation by
$$\mathbf{\bar{x}} = (\bar{x}, \bar{y}) $$
$$\mathbf{\bar{p}} = (\bar{p}_x, \bar{p}_y) $$
{{sectionTitleLong[1]}}
We start with the one dimensional case: imagine having a chain of identical atoms. We then approximate their interactions to only be with nearest neighbours. We do this by saying that neighbouring atoms are connected by springs, all of which are identical.
The solution to this model is most easily dealt with when the infinite lattice approximation is made. This is where we approximate the solid size as much larger than the maximum displacement of individual atoms. This is physically acceptable as in reality, atom movements in solids are much smaller than the size of the solids. The most general solution is $$ u_n(t) = Re \sum_{k}\tilde{u}_k e^{i(nka-\omega_kt)} .$$ This is a sum of an arbitrary number of waves, each with their own wavevector. $u_n$ is the displacement of the $n^{th}$ atom from its equilibrium position and $k$ is the wavevector of the incoming wave.
Here we simulate for a single $k$: $$ u_n(t) = u_k \cos(nka-\omega_kt)$$ For any given $k$: $$ \omega_k = 2 \omega_D \left| \sin \left( \frac{k a}{2} \right) \right|$$ where $$ \omega_D = \sqrt{\frac{\kappa}{m}}$$ $\kappa$ is the spring constant, $m$ is the mass of a single atom, $a$ is the atomic spacing and $\omega_D$ is also known as the Debye frequency. Here, we assume $a = \omega_D = 1$ and $\tilde{u}_k$ has zero phase for simplicity.
$u_k$ is the amplitude of the response of the individual atoms to wave mode $k$. Notice that the overall motion is unaffected if $2n \pi$ for any integer $n$ is added to $k$. Mathematically, this is due to the factor $e^{i2n\pi} = 1$ in the general solution. Physically, it makes sense due to the given trigonometric dispersion relation for $\omega_k$ - $k + 2n\pi$ has the same energy as $k$. (Try adding integer multiple of 2 to the $r$ value!)
For the upcoming visualisations, we will ignore this redundancy by taking $-\pi \lt ka \leqslant \pi $, known as the first Brillouin Zone. This applies to components in the higher dimensions too.
Also notice that when $r \to \pm 1$, there are two standing waves. Neighbouring atoms move in anti-phase. (Reduce $u_k$ to see this effect better.)
{{sectionTitleLong[2]}}
The equation of motion for the field is $$ \ddot{\phi} = \nabla^2 \phi - m^2 \phi - \lambda \phi^3 $$
The dispersion relation is $$ E(p^2) = \sqrt{\mathbf{p} \cdot \mathbf{p} + m^2} $$ Its first derivative is given by $$ E'(p^2) = \frac{1}{2 \sqrt{\mathbf{p} \cdot \mathbf{p} + m^2}} $$
We use periodic boundary condtion. The initial conditions are $$ \phi_i (0, \mathbf{x}) = e^{i \mathbf{\bar{p}}_i \cdot (\mathbf{x} - \mathbf{\bar{x}}_i)} e^{- \frac{\sigma^2}{2} (\mathbf{x} - \mathbf{\bar{x}}_i)^2} $$ $$ \dot{\phi}_i (0, \mathbf{x}) = $$ $$ \phi_i (0, \mathbf{x}) \{2 \mathbf{\bar{p}}_i \cdot (\mathbf{x} - \mathbf{\bar{x}}_i) E'_i(p^2_i)[p^2_i - 2 \sigma(\mathbf{x} - \mathbf{\bar{x}}_i)^2] $$ $$ -i [E_i(p^2_i) - 2 p^2_i E'_i(p^2_i)] \} $$ where the subscript $i$ denotes the $i^{th}$ particle.
The field satisfies linearity $$ \phi = \Sigma_i \phi_i $$ $$ \dot{\phi} = \Sigma_i \dot{\phi_i} $$
We deploy Finite Difference method to compute the laplacian $\nabla^2 \phi$.


{{Infobox prepared food | name = Sago pudding | image = | caption = Sago pudding | alternate_name = | country = | region = | creator = | course = | type = Pudding | served = | main_ingredient = Sago, water or milk, sugar | variations = Sago gula melaka | calories = | other = }} Sago pudding is a sweet pudding made by boiling sago with either water or milk and adding sugar and sometimes additional flavourings. It is made in many cultures with varying styles, and may be produced in a variety of ways.
In Malaysia, sago gula melaka is a sago pudding made by boiling pearl sago in water and serving it with syrup of palm sugar (gula melaka) and coconut milk.<ref>{{cite web |url=http://www.mycookinghut.com/2010/05/23/sago-pudding-with-palm-sugar-sago-gula-melaka/ |title=Sago Pudding with Palm Sugar (Sago Gula Melaka) |publisher=mycookinghut.com |accessdate=9 March 2011}}</ref>
In the UK, "sago pudding" is generally made by boiling pearl sago and sugar in milk until the sago pearls become clear, and thickening it with eggs or cornflour. Depending on the proportions used it can range from a runny consistency to fairly thick, and can be similar to tapioca pudding or rice pudding.
{{reflist}}
{{Puddings}} {{dessert-stub}}


|
|||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
The purpose of this interface is to separate the interpretation algorithm
from the SCXMLExecutor
and therefore make it pluggable.
Semantics agnostic utility functions and common operators as defined in
UML can be found in the SCXMLHelper
or attached directly to
the SCXML model elements. Some of the possible semantic interpretations
are, for example:
Specific semantics can be created by subclassing
org.apache.commons.scxml.semantics.SCXMLSemanticsImpl
.
| Method Summary | |
void |
determineInitialStates(SCXML input,
Set states,
List entryList,
ErrorReporter errRep,
SCInstance scInstance)
Determining the initial state(s) for this state machine. |
void |
enumerateReachableTransitions(SCXML stateMachine,
Step step,
ErrorReporter errRep)
Enumerate all the reachable transitions. |
void |
executeActions(Step step,
SCXML stateMachine,
EventDispatcher evtDispatcher,
ErrorReporter errRep,
SCInstance scInstance)
Executes all OnExit/Transition/OnEntry transitional actions. |
void |
filterTransitionsSet(Step step,
EventDispatcher evtDispatcher,
ErrorReporter errRep,
SCInstance scInstance)
Filter the transitions set, eliminate those whose guard conditions are not satisfied. |
void |
followTransitions(Step step,
ErrorReporter errorReporter,
SCInstance scInstance)
Follow the candidate transitions for this execution Step, and update the lists of entered and exited states accordingly. |
void |
initiateInvokes(Step step,
ErrorReporter errRep,
SCInstance scInstance)
Initiate any new invoked activities. |
SCXML |
normalizeStateMachine(SCXML input,
ErrorReporter errRep)
Optional post processing immediately following Digester. |
void |
processInvokes(TriggerEvent[] events,
ErrorReporter errRep,
SCInstance scInstance)
Forward events to invoked activities, execute finalize handlers. |
void |
updateHistoryStates(Step step,
ErrorReporter errRep,
SCInstance scInstance)
Go over the exit list and update history information for relevant states. |
| Method Detail |
public SCXML normalizeStateMachine(SCXML input, ErrorReporter errRep)
input
- SCXML state machineerrRep
- ErrorReporter callback
public void determineInitialStates(SCXML input, Set states, List entryList, ErrorReporter errRep, SCInstance scInstance) throws ModelException
input
- SCXML state machinestates
- a set of States to populateentryList
- a list of States and Parallels to entererrRep
- ErrorReporter callbackscInstance
- The state chart instance
ModelException
- in case there is a fatal SCXML object model problem.public void executeActions(Step step, SCXML stateMachine, EventDispatcher evtDispatcher, ErrorReporter errRep, SCInstance scInstance) throws ModelException
step
- provides EntryList, TransitList, ExitList gets
updated its AfterStatus/EventsstateMachine
- state machine - SCXML instanceevtDispatcher
- the event dispatcher - EventDispatcher instanceerrRep
- error reporterscInstance
- The state chart instance
ModelException
- in case there is a fatal SCXML object model problem.public void enumerateReachableTransitions(SCXML stateMachine, Step step, ErrorReporter errRep)
stateMachine
- a state machine to traversestep
- with current status and list of transitions to populateerrRep
- ErrorReporter callbackpublic void filterTransitionsSet(Step step, EventDispatcher evtDispatcher, ErrorReporter errRep, SCInstance scInstance) throws ModelException
step
- with current statusevtDispatcher
- the event dispatcher - EventDispatcher instanceerrRep
- ErrorReporter callbackscInstance
- The state chart instance
ModelException
- in case there is a fatal SCXML object model problem.public void followTransitions(Step step, ErrorReporter errorReporter, SCInstance scInstance) throws ModelException
step
- The current SteperrorReporter
- The ErrorReporter for the current environmentscInstance
- The state chart instance
ModelException
- in case there is a fatal SCXML object model problem.public void updateHistoryStates(Step step, ErrorReporter errRep, SCInstance scInstance)
step
- The current SteperrRep
- ErrorReporter callbackscInstance
- The state chart instancepublic void processInvokes(TriggerEvent[] events, ErrorReporter errRep, SCInstance scInstance) throws ModelException
events
- The events to be forwardederrRep
- ErrorReporter callbackscInstance
- The state chart instance
ModelException
- in case there is a fatal SCXML object model problem.public void initiateInvokes(Step step, ErrorReporter errRep, SCInstance scInstance)
step
- The current SteperrRep
- ErrorReporter callbackscInstance
- The state chart instance
|
|||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |