Setting Up Actions

FinancialForce Reporting does not provide Apex classes that can be configured as actions on dataviews. However, other FinancialForce products, for example Accounting, do provide Apex that can be configured as actions on dataviews. An example configuration for the Cash Matching action is given. Configuration details for other actions are shown in the table.

Note:

The following example is configured in Accounting.

Example: To configure the cash matching Apex class as an action

  1. Create a dataview that includes the codaTransaction__c object.
  2. Make sure the transaction Id field is added to the dataview. By default the field name for this field is codaTransaction__c.Record ID.
  3. Change this field name to 'TransactionId'.
  4. [Optional] Mark this field as the key to uniquely identify each row in the action view results.
  5. This field does not need to be selectable or presentable so leave those checkboxes deselected.
  6. [Optional] You might also want to include the Sales Invoice (codaInvoice__c), Cash Entry (codaCashEntry__c) and Sales Credit Note (codaCreditNote__c) objects via joins if you want to work with the different document types when matching, but you can work directly with the transactions.
  7. On the Actions tab, enter a name and description for the action (such as Cash Match) then choose OLIActionCashMatching from the Apex Class drop-down list. The Parameter field can be left blank.
  8. Create an inquiry template to use the dataview.

For information on using the actions, see Performing Actions From Action Views.

Action parameters

Undo Cash Matching action

This action uses the last matching reference on a transaction to unmatch all transactions with that reference.

Undo Cash Matching Action Parameters
Apex Class Object on Dataview Mandatory Field Rename Field As
OLIActionUndoCashMatching codaTransaction__c codaTransaction__c.Record ID TransactionId

Optionally, include the codaInvoice__c, codaCashEntry__c and codaCreditNote__c objects via joins if you want to work with the different document types when undoing a match, but you can work directly with the transactions.

Update Due Date action

Update Due Date Action Parameters
Apex Class Object on Dataview Mandatory Field Rename Field As
OLIActionUpdateInvoiceDueDate codaInvoice__c codaInvoice__c.Record ID InvoiceId

Amend Transaction action

This action enables you to update a document's description or the references on an invoice or credit note. You can amend the description on all document types except journals.

Amend Transaction Action Parameters
Apex Class Object on Dataview Mandatory Field Rename Field As
OLIActionAmendTransaction codaTransaction__c codaTransaction__c.Record ID TransactionId

Optionally, include the codaInvoice__c and codaPurchaseInvoice__c objects. Check that the document Description, Sales Customer Reference, Purchase Reference 1 and Purchase Reference 2 fields are presentable, so the user can see the effect of the changes he makes. These fields are on the following objects:

Fields
Field to be amended Object Source  Field Name
Description Transaction   DocumentDescription
Sales Customer Reference Transaction lookup Sales invoice and credit note CustomerReference
Purchase Reference 1 Transaction lookup Payable invoice and payable credit note Reference1
Purchase Reference 2 Transaction lookup Payable invoice and payable credit note Reference2