search

sashavmorozov / vlocity-epc-on-steroids

Vlocity EPC on Steroids allows boosting EPC configuration speed by uploading configuration from spreadsheets into Vlocity data model
5 stars 0 forks source link

[Feature] Support product specification extracting and loading #211

Closed sashavmorozov closed 3 years ago

sashavmorozov commented 3 years ago

This is to support the new concept of the Product Specification as it is introduced in Vlocity v232 (Summer'21). Ref to documentation: https://docs.vlocity.com/en/Offer-Specification.html

Requirements:

  1. Product can be tagged as Simple and Bundle (via the Specification Sub Type field)

  2. Product can be associated with a product specification (via the Product Spec lookup)

  3. Product can be linked to a product spec or an object type but not both at the same time

  4. Simple offer can be assigned to a product specification

  5. Bundle offer cannot be assigned to a product specification

  6. Products can be uploaded (from EOS to Org)

  7. Products can be downloaded (from Org to EOS)

Assumptions:

  1. The EPC on Steroids will not check if you are trying to add child records into a simple product
  2. The EPC on Steroids will not check if you are trying to add/link incompatible types of specs as children (e.g. link an offer with a service spec)
  3. No other validations are introduced at this moment
  4. All other validations are expected to be checked by the product designer before uploading records. If you try to upload records that do not pass data validation rules (https://docs.vlocity.com/en/Configuration-for-Offer-Specification-Realization.html) the upload process may fail (or may not, I don't know really)

/shrug

sashavmorozov commented 3 years ago

Here is what changed:

In the spreadsheet:

  1. We added a new column in the Offerings tab: Specification Sub Type
  2. We added a new column in the Offerings tab: Product Spec (you can only choose records that are tagged as Product, wow)
  3. We added a new column in the Offerings tab: Product Spec Code (formula for more accurate matching)
  4. The Specification Type column is now conditionally coloured
  5. If you populate both object type and product spec - they will be highlighted with red colour (no good!)

In the loader:

  1. You can now upload Specification Sub Type and Product Spec information from EOS to SFDC image

In the extractor:

  1. You can now extract Specification Sub Type and Product Spec information from SFDC to EOS

Additional notes:

  1. The tab is still called Offerings although you can define here offers, product specs, CFS and RFS specs. There is still an ongoing debate about the use of these artefacts, you may expect some changes in the future with regards of tab naming