Newer Version Available
AppUsageAssignment
Salesforce application developers configure the AppUsageType metadata. Depending on the platform's requirements, some partners and system integrators may need to create AppUsageAssignments and assign them to records on their own. In other cases, the application is provided with flows used to assign app usage assignments to records in an org. For example, let's say you have a ShoppingCart application that provides commerce services with custom Shopping Cart fields on the order. When a user orders from the shopping cart application, the application has a flow that creates an order with a Shopping Cart app usage assignment. The assignment has an AppUsageType field with a value of ShoppingCart. This value represents the ShoppingCart metadata type that the flow configured for the app usage assignment.
Supported Calls
create(), delete(), describeLayout(), describeSObjects(), getDeleted(), getUpdated(), query(), retrieve(), undelete(), update(), upsert()
Fields
| Field | Details |
|---|---|
| AppUsageType |
|
| Name |
|
| RecordId |
|
Usage
This flowchart shows the record relationships in a sample AppUsageAssignment configuration. In this case, the org has two applications that provide additional features to orders, called "Industrial Orders" and "Healthcare Orders." When a sales rep makes an order, they set the order's Industry Type field to Industrial or Healthcare based on the order details. The Industrial Orders and Healthcare Orders applications both have flows that evaluate the order's Industry Type field, and then create and assign an app usage assignment accordingly. This flowchart shows an instance where a sales rep has created one Industrial order and two Healthcare orders.