JustOn uses filters to selectively narrow down the set of records included in bulk operations according to your business requirements.
A filter returns all objects that match the filter, it does not filter them out.
Filter Use Cases
Filter use cases indicate the supported operations. These include:
SubscriptionBuilderfor the subscription builder
Subscription filters are presented as radio buttons. If there is one subscription filter, it is always selected. If there are multiple subscription filters, users are prompted to select one of them for the invoice run.
Continuous Dailyfor the transaction builder
Transaction filters are presented as checkboxes. Users can select multiple (or no) transaction filters.
Genericfor the generic invoice run
Generic filters are presented as checkboxes. Users can select multiple (or no) generic filters.
AccountStatementfor the account statement run
Account statement filters are presented as values in a picklist. If there is one account statement filter, it is always selected. If there are multiple account statement filters, users are prompted to select one of them for the statement run.
empty for the regular invoice run
A filter group specifies an arbitrary criterion for grouping invoice run-relevant filters, used to narrow down large filter lists. Assigning a group to all filters for a specific context (business entity, region, etc.) allows for pre-selecting this group in the UI (New Invoice Run, New Invoice From Subscription), which then displays only the relevant filters, accelerating the invoice creation.
JustOn implements filters using the custom setting Filters. The following fields are available:
|Name||Specifies the filter name, will be available as an option value when triggering the operation. Must be unique.|
|Child Relation||Specifies the name of the child object.
Used by the subscription builder and the generic invoice run, required if you create subscription items or invoice line items based on the child records.
For master-detail relations, use the API name of the detail object. In case of standard Salesforce objects, you can use Workbench to find the correct name.
For parent-child relations, use the relationship name of the child object.
|Condition||Specifies a condition (SOQL WHERE clause) to restrict the set of included records.
For details, see SOQL SELECT Syntax in the Salesforce Help.
|Sequence||Determines the position of this filter in a filter list.|
|Target||Specifies the API name of the target object.
For JustOn objects/fields, do not append the namespace prefix
|Use Case||Specifies the specific filter use case. Possible values include
empty for the regular invoice run
|Transactional Suffix||Specifies a suffix for control fields when invoicing a record multiple times to different recipients.|
|Parent Relationships||Specifies a parent relationship of the target object, which is required when starting a generic invoice run from a parent of the actual source object. Is a JSON string map where keys are lookup fields (or formulas to return the ID) that point to the intended parent object, with the parent object type as their values. For example,
|Filter Group||Specifies an arbitrary criterion for grouping (invoice run-relevant) filters, used to narrow down large filter lists. Assigning a group to all filters for a specific context (business entity, region, etc.) allows for pre-selecting this group in the UI (New Invoice Run, New Invoice From Subscription), which then displays only the relevant filters, accelerating the invoice creation.|
Depending on your organization's requirements, you must define custom filters.
In Setup, open Custom Settings.
In Salesforce Lightning, navigate to Custom Code > Custom Settings.
In Salesforce Classic, navigate to Develop > Custom Settings.
Click Manage in the row of Filters.
- Click New to create a new filter, or Edit to modify an existing filter.
Specify the details as necessary.
For details, see Filters Information.
This makes the filter immediately available.