Partial Assetization of Product Attributes

You can set a technical product attribute as "not assetizable" so that Order Management doesn't store Personally Identifiable Information (PII) in OM internal technical inventory. In fact, OM doesn't store that information permanently at all.

Order Management gives you the option of assetizing some product attributes and not others. For example, you can create an order with Personally Identifiable Information (PII), such as customer name, phone number, and address. This information is required on a one-time basis to create a billing account, and then is no longer needed. You can define the PII attribute on one of the technical products and flag the PII attributes as Not Assetizable. Avoid creating a mapping for this attribute. Instead populate the value during orchestration instead. Doing so ensures that there's no impact in decomposition from this attribute so Order Management doesn't store PII in internal technical inventory or anywhere else on a permanent basis.

You can also use this feature to support transient or process variables, essentially data generated and used during orchestration, perhaps passed from one orchestration item to another, but not persisted after orchestration completes. For example, a customer orders Internet service. As part of the fulfillment process, a temporary password or activation code is generated and emailed to the customer. During fulfillment, you generate the password within one orchestration item and save it on the technical fulfillment request line, which is then passed to the next orchestration item that emails the password to the customer. However, at the end of the orchestration process, Internet service is assetized but the password is not assetized or persisted.

There is a difference between assetizing commercial products and technical products:

• Commercial assetization only stores the commercial products selected by the customer in Salesforce. This is a snapshot of the products to which the customer has subscribed. Partial assetization of attributes can only be used on technical products.

• Technical assetization stores the output of decomposition into the technical tables in Order Management.

You can control which attributes are assetized by checking the Not Assetizable field on technical product attributes. See Use Assetization and Encryption Options for Product Attributes.

For releases prior to Fall 2018, you can achieve the same results without using the not-assetizable attribute feature by controlling the value of the attribute using an auto-task. Before assetization, ensure the value of the attribute is empty so it does not become assetized.