In the Product Designer, you can flag attributes for technical products as not assetizable and encrypted. After these attribute metadata flags have been set on an object type and inherited by a product, you must create decomposition rules to map the attributes to the downstream fulfillment requests, which are the basis for the technical inventory.
Not Assetizable
The Not Assetizable attribute metadata flag is useful for transitory information that should not persist or does not need to persist beyond the completion of order processing where assetization would usually occur. This metadata flag is stored in Order Management, not in the Salesforce platform.
An example of transitory information is the initial password that a customer uses to log in to the provider's website for the first time. During fulfillment, the initial password is generated within an orchestration order item, then saved on the technical fulfillment request line, which is then passed to the next orchestration item that emails the password to the customer. The password does not need to persist at the end of order management. Other information that does not need to persist can be the result of back-end services connected to order items that do not become customer assets, such as a service needed to fulfill a customer’s order. As an example, there might be a check to see whether a required modem is in stock and on the delivery vehicle. This information is not needed after that check has been made.
Encrypted
The Encrypted attribute metadata flag is used to protect personally identifiable information (PII) and other data such as the customer name, phone number, social security number, and so on. These pieces of information can be captured as attributes and should be sent downstream only for legitimate purposes. You can use the encrypted flag to indicate the PII or other information must be stored securely.
Encrypted and Not Assetizable Settings
Not Assetizable and Encrypted are attribute metadata flags. You set these flags when an attribute is assigned to an object type in Unified Product Catalog. These flags can only be set when the Run-time Configurable flag is also set. Once the attribute is marked as Run-time Configurable, you can then set Not Assetizable or Encrypted or both.
If none are selected, attribute values will be stored in the technical inventory after decomposition. If both are selected, the attribute will be encrypted during processing and not stored with the inventory items. However, if you set the Encrypted flag to True, and Not Assetizable to False, the attribute is stored in the technical inventory, but the attribute will be encrypted. Technical assetization stores the output of decomposition into the technical tables in Order Management, not in the Salesforce platform.
Once assigned to the object type, every product that is created in that object type will inherit these metadata flags, along with the other attribute and metadata. Not Assetizable, Encrypted and Run-time Configurable are then non-overridable at the product level. This prevents any product manager or EPC administrator from removing these flags during product creation.
If you set these flags on existing attributes, it will not affect attributes already stored in existing technical inventory.
Not Assetizable and Encrypted metadata flags are intended to trigger functions in downstream order management systems, such as Order Management. There is no encryption to these attributes when used on commercial products in Industries CPQ or in Order Management, and the information will remain stored and accessible on the originating order. Consequently, these attribute flags are intended for use in technical products only.