Get a transaction attribute (Deprecated)

get

/crmRestApi/resources/11.13.18.05/loyaltyPrograms/{LoyProgramId}/child/TransactionAttributes/{LoyAttrdefnBId}

Request

Path Parameters
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
  • The primary key to identify a program. Oracle Loyalty Cloud generates this attribute value during the creation of a program record. There is no default value, dependency, or limitation associated with this attribute.
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.

There's no request body for this operation.

Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : loyaltyPrograms-TransactionAttributes-item-response
Type: object
Show Source
  • Read Only: true
    Maximum Length: 30
    The transaction attribute account activity code. If this option is specified, points expire if there is no activity of the type within the period specified for the point type. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 1
    The boolean attribute that specifies whether the created transaction attribute is enabled for use or not. The default value is N. There is no dependency or limitation associated with this attribute.
  • Read Only: true
    The primary key value of the loyalty attribute definitions corresponding to attribute types like pointType, Member, Transaction, and so on. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 30
    The transaction attribute type code. This attribute reflects the type of attribute, for example, Field, Point Total, and so on. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 75
    The external business service that can be called in the promotion to evaluate the business criteria. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 30
    The specification of which action must be applied during a transaction cancellation. The accepted values are Leave As Is (if selected, the value of the attribute remains the same when a transaction is cancelled), Revert, and so on. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    The transaction attribute conflict identifier that Oracle Loyalty Cloud generates during the creation of a new transaction attribute. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    The cost for each point. If you want to allow the product to be redeemed for a combination of points and currency, then enter the amount of money assigned as the cash value of one point. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 64
    The loyalty user that created the transaction attribute. Oracle Loyalty Cloud generates this attribute value during the creation of a new transaction attribute. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    The date when the transaction attribute is created. Oracle Loyalty Cloud generates this attribute value during the creation of a new transaction attribute. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    The currency used in the transaction. The accepted values are INR, USD, and GBP. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    The date when the transaction attribute currency exchange takes place. This attribute displays the date of the currency exchange during transaction attributes creation. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 30
    The promotion attribute data type name indicates whether the attribute is a string, or number, and so on. During transaction cancellation, Oracle Loyalty Cloud determines whether certain cancel actions must be applied or not, based on the data type name. For example, the Cancel Change action is available only for the Number data type. The Revert action is only available for the String and Number data types, and the Leave As Is action is available for all data types. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 75
    The cost for each point. If you want to allow the product to be redeemed for a combination of points and currency, then enter the amount of money assigned as the cash value of one point. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 1000
    The currency used in the transaction. The accepted values are INR, USD, and GBP. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 1
    The boolean attribute that indicates whether the transaction attribute should be displayed or not, so that it can be used in the promotion criteria. The default value is Y. There is no dependency or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 30
    The transaction attribute display name that is displayed to the user. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 1
    The boolean attribute that indicates whether the transaction attribute value is calculated dynamically based on another attribute, and that is used by the promotion criteria. The criteria can compare an attribute to a value or compare an attribute to another attribute. The default value is N. There is no dependency or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 30
    The expiry alignment attribute provides the details pertaining to the calculation of the expiry of points. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 30
    The basis for point or voucher expiry. The accepted values are Period (expires after a period of time) or Date (expires on a specific date). There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 30
    The transaction expiry day attribute specifies the day of the month when the points expire if the expiry basis is Date. There is no default value or limitation associated with this attribute. Dependent on Expiry Basis Code.
  • Read Only: true
    Maximum Length: 30
    The transaction expiry month attribute specifies the month when the points expire if the expiry basis is Month. There is no default value or limitation associated with this attribute. Dependent on Expiry Basis Code.
  • Read Only: true
    Maximum Length: 30
    The transaction expiry period unit of measure (UOM) attribute is used to specify when points expire. For example, if the points expire after they are earned, UOM is Year. After the points expire, the member can no longer exchange the points for rewards. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    The transaction expiry period length attribute is used to specify a length of time after when points expire. For example, if the points expire two years after they are earned, then the length is set to 2. After the points expire, the member can no longer exchange them for rewards. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 75
    The transaction internal name. The accepted values are Date1 or Number1. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    The date when the transaction attribute is last updated. Oracle Loyalty Cloud generates this attribute value and updates it whenever changes to the transaction attribute occur. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 64
    The user that last updated the attribute. Oracle Loyalty Cloud generates this attribute value and updates it whenever any changes take place to the transaction attributes. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 32
    The login details of the user that last updated the attribute. Oracle Loyalty Cloud generates this attribute value and updates it whenever any changes take place to the transaction attributes. There is no default value, dependency, or limitation associated with this attribute.
  • Links
  • Read Only: true
    The primary key of loyalty attributes. Oracle Loyalty Cloud generates this attribute value. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 30
    The transaction merge action attribute specifies how the program handles the attribute during a member merge. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 75
    The method that is used in the calculation of the transaction attribute value that can be used in promotion criteria. For example, the ORA_CAL_METHOD_MONTH_NAME method returns the month name. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    The minimum points needed to reactivate the expired points so that they can be used for redemption. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    The numeric value that corresponds to the number of months during which points will expire. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 30
    The option to select values from entities such as Transaction, Member, Promotion and so on, when defining a promotion. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    The transaction attribute object version number. Oracle Loyalty Cloud sets this attribute. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 75
    The pick applet attribute is a field whose values are entered using a dialog box. When defining criteria and actions, the dialog box with the values for this field is displayed. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 75
    The pick field is the field whose value the user sees in the UI after selecting from the pick applet. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 75
    The pick field name attribute is the user readable string of the PickField attribute. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 75
    The transaction pick list attribute is enabled if the attribute is a field whose values are entered using a picklist. When defining criteria and actions, the picklist with the values for this field is displayed. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    The program formula identifier that is available for use by a promotion, but only if it is associated with the same program as the program for the promotion. The formula can be used in criteria for comparisons and in actions for assigning values or updating attributes with the formula value. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    The primary key of loyalty promotions. Oracle Loyalty Cloud generates this attribute value. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 1
    The transaction qualifying point attribute is a boolean attribute that indicates that the points accrued when the promotion gets applied count toward earning tier status, but cannot be redeemed for rewards. The default value is N. There is no dependency or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 1
    The reactivate flag attribute reactivates member's points after they have expired. The default value is N. There is no dependency or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 1
    The boolean attribute that specifies whether the transaction attribute is editable or not. The default value is N. There is no dependency or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 1
    The transaction effective start date identifier indicates the date when the attribute can be used in promotions. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    Maximum Length: 30
    The unit of measure (UOM) for the time period until the expired points can be reactivated. The accepted values are Years, Months, Days, and so on. For example, if the reactivation expiry period is one year then the UOM is Year and the expired points can be reactivated after a period of one year from the date of expiry. There is no default value or limitation associated with this attribute.
  • Read Only: true
    The time period when the expired points can be reactivated. For example, if the reactivation expiry period is one year, then the time period length is 1 and the expired points can be reactivated after a period of one year from the date of expiry. There is no default value or limitation associated with this attribute.
  • Read Only: true
    The primary attribute of the loyalty tier class, which indicates the class to which a specific tier belongs. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    The promotion attribute weight factor is used to determine which promotion must be applied to the transaction, if multiple promotions qualify. There is no default value, dependency, or limitation associated with this attribute.
  • Read Only: true
    The weight factor non-qualifying attribute is used to determine whether to generate qualifying or non-qualifying points of each type when the weight factor attribute is specified. This attribute has a dependency on the Weight Factor attribute. There is no default value or limitation associated with this attribute.
Back to Top