Lab Info

Lesson: Product Discount Data Management (Standalone Custom Form)

Target Audience: Certified Configuration Engineer

Requirements & Solution Author: Petr Rys

Solution Developer & Lab Author: Marcin Łuczakuczak

User Story / Requirements

Create a standalone Custom Form to help pricing managers manage Discounts, Product Groups and Families from one place.
Product Group is part of Product Master, Product Family is assigned per Product Group.

Each Product group belongs to 1 Product Family. (Product Family Mapping table)
Based on cumulative yearly revenue on the whole Product Family the customer has assigned Discount Level in Discount Level Definition Table.
Based on Product Group and Discount Level achieved by the Customer the sales agent has a "recommended discount" and a "maximum allowed discount" (Target Discount % and Max Discount %)

Details

Product Discount Data Management Custom Form allows users to perform these tasks:

Change Data → select a table and change values within the table without adding new rows.
Add new Product Group → add a new group, assign it to a product family, and assign all the required discounts for different levels. It is important that the discount for each additional level is greater than or equal to the discount for the previous level; otherwise, the validation process will fail.
Add a product family → reassign product groups to reflect a new product family.
Add new discount level to existing product family → create new discount levels for an existing product family. The levels must be continuous, starting from level 1 at 0 Min Revenue. Each additional level must have a minimum revenue greater than or equal to the previous level. Users can assign new discounts for these new levels, ensuring that the discount for each additional level is greater than or equal to the discount for the previous level; otherwise, the validation will fail.

Learning Outcomes

At the end of the Lab, you should be able to:

Create Standalone Custom Form, Custom Form Type
Utilize Input Matrix as Custom Form input
Understand Custom Forms Workflow

Provided resources

Logics:

(sCFO_ProductDiscountLib)

Company Parameters:

(ProductFamilyMapping, DiscountLevelDefinition, Discount)

Acceptance Criteria

User can access a standalone Custom Form within the Analytics section to complete tasks listed in the Details section.

User can select one of three options: Modify data, Create new Product Group, or Create new Product Family.

A separate form will be displayed for each option
Tables with calculation results are available in the Calculations section, located on the right panel.

It is recommended to highlight any changes made to tables for better visibility and clarity.

After the user submits the form, changes should be saved in the corresponding company parameter tables. If a workflow has been added to the form, the changes should be saved after approval.
Sample solution

To create a standalone custom form, go to the main menu.
Locate the 9 dots icon in the left upper corner of application. Click to open the drop down.
Go to Analytics > Product Discount Manager.
In the new dialogue window, click on Create New Product Discount Manager icon in the top right corner.
Fill in the label then click on the blue Add icon in the bottom right corner of the window.

You will get a confirmation message in green that the form has been added successfully.

In the following window, under Inputs, select the management option from the drop down menu.
Depending on your choice, continue filling out the remaining fields.
To assign new products, click on the box and choose where you want to assign from the drop-down menu.
Click on Add in the bottom left corner to add discount levels if applicable.

Note that you may have to check what values are assigned to each level. To avoid missing out any fields, the system displays warning icons which disappear once the field has been filled out.

You can add as many discount levels as you need. Check out our documentation to learn more about discounts.

Click on Recalculate in the upper right corner.
To see a more detailed view of the Calculations, use the arrow on the right side next to the reload icon to open the calculations window. Click on Show to learn more.
To close the dialogue window click on X in the top right corner.
Click Submit in blue in the upper right corner to send your form for approval. A confirmation message in green will appear at the top center of the window.
In the Workflow tab, if you have enough rights for the operation, you can approve the form by clicking on the green checkmark icon. You can also add a reason for both approvals or rejections.
Add your reason, then click Submit. You will get another confirmation message.

If you go to Company Parameters by clicking the third icon from the left in the top right corner, under Categories> Custom Form, you can check your newly created form.

Step-by-step solution

Develop the logic and test in Studio

Go to the Pricefx Studio and create the following logics.

a) sCFO_ProductDiscountDataMgmt

Pricefx -> Create Calculation Logic

Nature: Custom form header (customFormHeader)

Name: sCFO_ProductDiscountDataMgmt

Add two new elements to your logic:

Configurator
Calculation

b) sCFO_Workflow

Pricefx -> Create Workflow Logic

Nature: DEFAULT

Workflow Type: Custom Form (customform)

Name: customform

Add two new elements to your logic with the suggested code:

AbortOnInputGenerationExecution

if (api.isInputGenerationExecution()) {
    api.abortCalculation()
}

BuildStep

workflow.addWatcherStep("Sales Manager")
        .withUserWatchers("admin")
        .withReasons("Sales manager needs to approve this form")

workflow.addApprovalStep("Sales Manager")
        .withPostStepLogic("customform_WorkflowPostStep")
        .withApprovers("admin")
        .withReasons("Sales manager needs to approve this form")

This is a sample solution that you can customize according to your requirements. This logic contain two steps. Pay attention to line number 6, which is the name of the Post Step logic that you will create in the next step.

c) customform_WorkflowPostStep (This logic is executed after all steps in the sCFO_workflow logic have been approved.)

Pricefx -> Create Workflow Logic

Nature: Post step (wfStepLogic)

Name: customform_WorkflowPostStep

Add a new element to your logic with the suggested code:

UpdateData

if (workflowHistory.steps.findAll { it.approvalStep }.every { it.approved } || 
workflowHistory.activeStep?.isEmpty()) {
        //TODO: The logic that will be performed after the user approved all the steps.                                    
}

Pay attention to the condition. The first part checks if all steps have been approved. The second part checks if we have added any steps to our Workflow logic.

Proceed with deploying all created logics to your partition.
Access Administration → Custom Form Types from your partition. Create a new form type by clicking on the [+ New Form Type] button located at the top-right corner of the screen. Uncheck Embedded option and fill in the form:

If you miss [+ New Form Type] button, add Custom Forms rights to your user (admin) using User Admin.

Add the following code in the Configuration section.

Here's a breakdown of what each component represents:

"name": "Default CFO config" - this is the name of the configuration, which can be used for identification and reference purposes.
"steps": [ ... ] - this is an array of steps, where each step represents a tab in the CFO feature. In this example, there is only one step (with the name "step1").
- { ... } - this is the object representing the current step. In this example, it has three tabs (with the names "details", "workflow", and "actions").
  - "name": "details" - this is the name of the tab, which will be displayed in the user interface.
  - "icon": "dashboard" - this is the icon for the tab. In this example, the icon for the "details" tab is represented by the "dashboard" font awesome icon.
  - "name": "workflow" - this is the name of the second tab.
  - "name": "actions" - this is the name of the third tab.
  - "type": "details"/"workflow"/"actions" - this is the type of the tab. In this example, there are three different types of tabs ("details", "workflow", and "actions").
  - "translationKey": "Management options"/"Workflow"/"Todo list" - this is the key used for translation of the tab labels. These keys should be defined in a property file.
  - "translationKey": "Product Discount Data Management" - this is the key used for translation of the step label.

In this configuration, the first tab is named "details" and uses the "dashboard" icon. It has a name that can be translated using the "Management options" key. The second tab is named "workflow" and uses the "process" icon. It has a name that can be translated using the "Workflow" key. The third tab is named "actions" and uses the "file-check-alt" icon. It has a name that can be translated using the "Todo list" key. The step label itself is also translatable using the "Product Discount Data Management" key.

Pricefx Studio - Create Custom Form Type

Using the Create Custom Form Type feature in Pricefx Studio simplifies the process of creating a Custom Form Type as compared to manual creation through the user interface. To create a custom form type in Pricefx, please follow these steps:

Right-click on the project name and select "Pricefx", then choose "Create Custom Form Type".

Provide a name for the new custom form type.

Fill in the fields provided below in the General tab.

Property	Value

Property	Value
Name	ProductDiscountManager
Label	Product Discount Manager
Header Logic Name	sCFO_ProductDiscountDataMgmt
Workflow Logic Name	customform
Mode	Module
Module	ANALYTICS

Navigate to the Steps tab and fill out all the necessary information. Add three Step Tabs, and set Name, Type, Icon, and Translation Key for each.

Name	Type	Icon	Translation Key

Name	Type	Icon	Translation Key
dashboard	details	dashboard	Management otions
workflow	workflow	process	Workflow
actions	actions	file-check-alt	Todo list

Replicate the process for the "Tabs" tab.

After you have provided all the necessary information, you can deploy the changes to your partition.
Access Administration → Custom Form Types from your partition. A new Custom Form Type should be visible on the list and in the Analytics menu.

In the image below, you will see two options for Product Discount Manager. The first one was manually created, and the second one was created in Pricefx Studio.

Verify if you have completed all the tasks correctly.

Go to Administration → Logics. Navigate to the left-hand panel and select "General Workflow Logic". You should see your customform logic on the list.
Go to Administration → Logics. Navigate to the left-hand panel and select "Workflow Post Step Logics". You should see your customform_WorkflowPostStep logic on the list.
Go to Administration → Logics. Navigate to the left-hand panel and select "Custom Forms". You should see your sCFO_ProductDiscountDataMgmt logic on the list.
Our newly created option should now appear on the left-hand side menu.

Go to the specified location and create a new form. Customize the label as per your choice, then click on the [Add] button to confirm your selection. If you don't assign a label to your form, the system will automatically set a default label.

You should see a view similar to this:

Compare the form with the code in Configuration section.

Fetch sCFO_ProductDiscountLib to your partition.

This logic contains two elements:

ConstConfig

Includes permanent parameters such as formatting elements, options description, table names, and other configuration elements.

CfoProductConfiguratorUtils

Includes some methods that may be helpful when creating a form.

Navigate to the sCFO_ProductDiscountDataMgmn logic and open the Configurator.groovy file. Once you have accessed the file, add the following code snippet to it.

Take a look at line 4 and the value of configuratorName, which will be created in the next step.

DEBUGGING

Make sure to set the proper CustomForm for your logic in the Inputs tab. Run and test the logic afterwards.

If you want to verify the results at each step, you can use the 'api.trace()' function.

Make sure that you receive values that are similar to these.

If everything appears to be in order, you may proceed with the next step.

Create sCFO_ProductDiscountHeader_Configurator logic.

Pricefx -> Create Calculation Logic

Nature: DEFAULT

Name: sCFO_ProductDiscountHeader_Configurator

Add new elements to your logic:

ConfiguratorEntry
OptionInput
ChangeDataInputs

a) add the following code snippet to ConfiguratorEntry.groovy.

In this step, we will create the configuratorEntry object and add a new hidden input with our custom form id to the configuratorEntry before returning it.

a) add the following code snippet to OptionInput.groovy.

In this step, we will add a header and a drop-down list with options for selecting individual forms to the configurator.

a) add the following code snippet to ChangeDataInputs.groovy.

In this step, we retrieve the option selected by the user and pass it as a parameter to the method that changes the form depending on the selected option.

EXPECTED RESULT

DEBUGGING

Open logic.json in sCFO_ProductDiscountHeader_Configurator.
Open Studio Editor.
Click on the Inputs tab.
Set the Context to CONFIGURATOR.
Generate Inputs.
Click on the Results tab and check output.

Your output should resemble the example given below.

The next step is to design forms for each of the three available options. Here are the expected results presented below.

Change data option. Three separate forms will be created based on the selected choice in the "Select table" dropdown.

a) Product Family Mapping

Requirements

"Select Product Group or Product Family" is a drop-down list with two options: Product Group, Product Family
“Select the value you want to change” is drop-down list with unique values from ProductGroup/Product Family colums
“New name” is input type of String
All fields are required.

b) Discount Level Definition

Requirements

"Select table" is a drop-down list with three options: Product Family Mapping, Discount Level Definition, and Discount.
After selecting the table we want to modify, a table should display the current data from the corresponding Company Parameters table. The table is not editable.
The user is permitted to modify only a single row of the table.
Use the drop-down list to set keys for each table.
All non-key fields must be updated with edited fields that correspond to their respective values.

For Discount Level Definition option:

For Product Family Mapping option:

For Discount option:

All fields are required.

Add new Product Group option

Requirements

“New Product Goup“ is an input type of String
“Assign Product Family” is a drop-down list with unique values of Product Familty colum in Discount Level Definition company parameter table.
The table for adding and deleting discount records should have identical columns as the Discount company parameters table, and provide a user-friendly way to add records.
“Product Group” column shoud have a drop-down list with newly added “New Product Group”. ColumnType: Option
“Discount Level” coulumn should have a drop-down list with list of numbers from 1 to 6. columnType: Option
“Traget Discount” and “Max Discount” are coulmns with columnType: Numeric
All fields are required.

Add new Product Family option

Requirements

“New Product Family“ is an input type of String
“Assign new Product Family to an already existing Product Group.” is a checkbox. Default: unchecked.
“Assign to:” is a drop-down list. This is a list of unique values from “Product Family” column in Discount Level Definition company parameters table. This filed will be visible if the “Assign new Product Family to an already existing Product Group” value is set to true (with the checkbox checked).
The table for adding and deleting new discount levels records should have identical columns as the Discount Level Definition company parameters table, and provide a user-friendly way to add records.
“Product Family” column shoud have a drop-down list with newly added “New Product Family”. ColumnType: Option
“Discount Level” and “Min Revenue” are coulmns with columnType: Numeric
All fields are required.

Solution

Go to ChangeDataInputs.groovy and look at the configuratorSwitch method. Implement methods for each option chosen by the user to create one of three forms. Each method returns the ConfiguratorEntry object.

getChangeDataConfiguratorEntry()

For Discount Level Definition option:

	label	name	type

	label	name	type
1	Discount Level Definition	`Discount Level Definition`	`InputType.INPUTMATRIX`
2	Select Product Family you want to change.	`productFamilyOption`	`InputType.OPTION`
3	Select Discount Level	`discountLevelsOption`	`InputType.OPTION`
4	New Min Revenue	`newMinRevenue`	`InputType.INTEGERUSERENTRY`

Discount Level Definition: data from DiscountLevelDefinition lookup table. Read-only table.
Select Product Family you want to change.: list distinct values found in the "Product Family" column from the DiscountLevelDefinition table.
Select Discount Level: Discount levels for selected Product Family.

For Product Family Mapping option:

	label	name	type

	label	name	type
1	Product Family Mapping	`Product Family Mapping`	`InputType.INPUTMATRIX`
2	Select Product Group or Product Family	`changeGroupOrFamily`	`InputType.OPTION`
3	Select the value you want to change.	`productGroupOption` `productFamilyOption`	`InputType.OPTION` `InputType.OPTION`
4	New name	`newName`	`InputType.STRINGUSERENTRY`

Product Family Mapping: data from ProductFamilyMapping lookup table. Read-only table.
Select Product Group or Product Family: two options [“Product Group“, “Product Family”]
productGroupOption or productFamilyOption : The items are shown according to the selection made in the changeGroupOrFamily option
productGroupOption : list of distinct values found in the "Product Group" column from the ProductFamilyMapping table.
productFamilyOption : list of distinct values found in the "Product Family" column from the ProductFamilyMapping table.

For Discount option:

	label	name	type

	label	name	type
1	Discount	`Discount`	`InputType.INPUTMATRIX`
2	Select the value you want to change.	`productGroupOption`	`InputType.OPTION`
3	Select Discount Level	`discountLevelsOption`	`InputType.OPTION`
4	New Target Discount %	`newTargetDiscountPct`	`InputType.INTEGERUSERENTRY`
5	New Max Discount %	`newMaxDiscountPct`	`InputType.INTEGERUSERENTRY`

Discount: data from Discount lookup table. Read-only table.
Select the value you want to change.: list distinct values found in the "Product Group" column from the Discount table.
Select Discount Level: Discount levels for selected Product Group.

getAddFamilyConfiguratorEntry()

	label	name	type

	label	name	type
1	New Product Family	`productFamilyInput`	`InputType.STRINGUSERENTRY`
2	Assign new Product Family to an already existing Product Group.	`assignToGroup`	`InputType.BOOLEAN`
3	Assign to	`assignProductGroup`	`InputType.OPTION`
4	New Discount Levels	`New Discount Levels`	`InputType.INPUTMATRIX`

Assign to: list of unique names from ProductFamilyMapping lookup table
New Discount Levels: user can add and delete rows.

getAddGroupConfiguratorEntry()

	label	name	type

	label	name	type
1	New Product Group	`productGroupInput`	`InputType.STRINGUSERENTRY`
2	Assign Product Family	`assignProductFamily`	`InputType.OPTION`
3	New Discount	`New Discount`	`InputType.INPUTMATRIX`

Assign Product Family: list of unique values from ProductFamilyMapping lookup table
New Discount: user can add and delete rows

Calculations

The results will be displayed as tables in the right panel. Only tables with changes will be shown as copies of parameter tables with updated values.

	Option	Tables that should be displayed

	Option	Tables that should be displayed
1	Change data → Product Family Mapping → Product Group	Discount Table Product Family Mapping
2	Change data → Product Family Mapping → Product Family	Product Family Mapping Discount Level Definition
3	Change data → Discount Level Definition	Discount Level Definition
4	Change data → Discount	Discount Table
5	Add new Product Group	Product Family Mapping Discount Level Definition
6	Add new Product Family	Product Family Mapping Discount Level Definition

Open the Calculation.groovy file, which is located in the sCFO_ProductDiscountDataMgmt logic. Once it's open, please add the following code to the file.

		Steps to follow

		Steps to follow
1	`Part-1`	Create a table with the following columns: `'Product Group',` `FieldFormatType.TEXT` `'Discount Level', FieldFormatType.NUMERIC` `'Target Discount %', FieldFormatType.PERCENT` `'Max Discount %'`, `FieldFormatType.PERCENT` Get data from `'Discount'` company parameter table. Add data from `'Discount'` to the newly created. Get data from `'New Discount'` table. This table has been created in getAddGroupConfiguratorEntry method. Add data from `'New Discount'` to the newly created with proper style Tables should use a distinct color for new values. Remember that you need to divide the percentages by 100. Add new table from point 1 to the customFormProcessor. Create a second table with the following columns: `"Product Group", FieldFormatType.TEXT` `"Product Family", FieldFormatType.TEXT` Get data from `'ProductFamilyMapping'` company parameter table. Add data from `'ProductFamilyMapping'` to the newly created. Get data from `productGroupInput` and `assignProductFamily` and add them to the newly created table. Remember to apply appropriate formatting. Add new table from point 7 to the customFormProcessor.
2	`Part-2`	Create a table with the following columns: `"Product Family", FieldFormatType.TEXT` `"Discount Level", FieldFormatType.INTEGER` `"Min Revenue", FieldFormatType.NUMERIC` Get data from `'DiscountLevelDefinition'` company parameter table. Add data from `'DiscountLevelDefinition'` to the newly created. Get data from `'New Discount Levels'` table. This table has been created in getAddFamilyConfiguratorEntry method. Add data from `'New Discount Levels'` to the newly created. Remember to apply appropriate formatting. Add new Table from point 1 to the customFormProcessor. Create a second table with the following columns: `"Product Group", FieldFormatType.TEXT` `"Product Family", FieldFormatType.TEXT` Get values from `assignProductGroup` and `productFamilyInput` Get data from `'ProductFamilyMapping'` company parameter table Iterate through `'ProductFamilyMapping'` data and change product family for product group. Ensure that only a single value is modified. Remember to apply appropriate formatting. Add new Table from point 7 to the customFormProcessor.
3	`Part-3`	Get the `changeGroupOrFamily` value. This is an input option from `changeDataSection`. Get the `newName` vaue. This is an input string entry from `changeDataSection` Get the `ppTableInput` value. This is an input option from `changeDataSection`
4	`Part-4`	Create a table with the following columns: `"Product Group", FieldFormatType.TEXT` `"Product Family", FieldFormatType.TEXT` Get data from `'ProductFamilyMapping'` company parameter table.
5	`Part-5`	Get the `productFamilyOption` value. Iterate through `'ProductFamilyMapping'`. If `productFamilyOption` equals product family add `newName` value to the row. Remember to apply appropriate formatting. Create a table with the following columns: `"Product Family", FieldFormatType.TEXT` `"Discount Level", FieldFormatType.INTEGER` `"Min Revenue", FieldFormatType.NUMERIC` Get data from `'DiscountLevelDefinition'` company parameter table. Add data from `'DiscountLevelDefinition'` to the newly created from point 3. Iterate through data `'DiscountLevelDefinition'` add and new product family. Remember to apply appropriate formatting. Add new table from point 3 to the customFormProcessor.
6	`Part-6`	Get the `productGroupOption` value. Iterate through `'ProductFamilyMapping'`. If `productFamilyOption` equals product group add `newName` value to the row. Remember to apply appropriate formatting. Create a table with the following columns: `'Product Group', FieldFormatType.TEXT` `'Discount Level', FieldFormatType.NUMERIC` `'Target Discount %', FieldFormatType.PERCENT` `'Max Discount %', FieldFormatType.PERCENT` Get data from `'Discount'` company parameter table. Add data from `'Discount'` to the newly created from point 3. Iterate through data `'Discount'` add and new product group. Remember to apply appropriate formatting. Add new table from point 3 to the customFormProcessor.
7	`Part-7`	Add new table from `Part-4` to the customFormProcessor.
8	`Part-8`	Create a table with the following columns: `"Product Family", FieldFormatType.TEXT` `"Discount Level", FieldFormatType.INTEGER` `"Min Revenue", FieldFormatType.NUMERIC` Get data from `'DiscountLevelDefinition'` company parameter table. Get the `discountLevelsOption` value. Get the `productFamilyOption` value. Add data from `'DiscountLevelDefinition'` to the newly created table. Iterate through data from `'DiscountLevelDefinition'`. If product family equals `productFamilyOption` and discount level equals `discountLevelsOption` change `newMinRevenue` for the row. Remember to apply appropriate formatting. Add new table from point 1 to the customFormProcessor.
9	`Part-9`	Create a table with the following columns: `'Product Group', FieldFormatType.TEXT` `'Discount Level', FieldFormatType.NUMERIC` `'Target Discount %', FieldFormatType.PERCENT` `'Max Discount %', FieldFormatType.PERCENT` Get data from `'Discount'` company parameter table. Get the `productGroupOption` value. Get the `discountLevelsOption` value. Add data from `'Discount'` to the newly created table. Iterate through data from `'Discount'`. If product group equals `productGroupOption` and discount level equals `discountLevelsOption` change max discount to `(newMaxDiscountPct`/100) and target discount to `(newTargetDiscountPct`/100). Remember to apply appropriate formatting. Add new table from point 1 to the customFormProcessor.

Code samples

Task	Sample Code

Task	Sample Code
Create a table
Get data from company parameter table
How to edit cell style in table
How to add new table to the customFormProcessor.

Saving changes to the tables

We need to ensure that changes in the target tables are displayed accurately. Once the user approves the changes, they should be saved. The customform_WorkflowPosStep logic is responsible for this process.

We need to revisit the logic that controls our Workflow. Our logic consists of two steps. Take a look at BuildStep.groovy

In line number 6, we see a reference to logic, which will be performed after the user approval. Open the UpdateData.groovy file in customform_WorkflowPosStep logic and add the code to consolidate data in the Company Parameters tables.

This task can be approached in various ways. You can either attempt to preserve the data or use the provided solution below.

	Steps to follow

	Steps to follow
`part-1`	Get user inputs from current item assign it to `inputs` variable Get individual field values from user `inputs`: `"managementOptionsInput"` - assign it to the `optionInput` variable `"changeGroupOrFamily"` - assign it to the `changeGroupOrFamily` variable `"ppTableInput"` - assign it to the `ppTableInput` variable `"newName"` - assign it to the `newName` variable
`part-2`	Get value of `"productGroupOption"` from user `inputs` and assign it to the `oldName` variable Get `"Discount"` lookup table Id assign it to the `discountID` variable. Create filters: `'ProductGroup'` equal `oldName` `'lookupTable.id'` equal `discountID` Update `"Discount"` lookup table. To obtain accurate data, make use of filters. Get `"ProductFamilyMapping"` lookup table Id assign it to the `productFamilyMappingID` variable. Create filters: `'name'` equal `oldName` `'lookupTable.id'` equal `productFamilyMappingID` Update `"ProductFamilyMapping"` lookup table. To obtain accurate data, make use of filters.
`part-3`	Get value of `"productGroupOption"` from user `inputs` and assign it to the `oldValue` variable Get `"DiscountLevelDefinition"` lookup table Id assign it to the `discountLevelDefinitionID` variable. Create filters: `'ProductFamily'` equal `oldValue` `'lookupTable.id'` equal `discountLevelDefinitionID` Update `"DiscountLevelDefinition"` lookup table. To obtain accurate data, make use of filters. Get `"ProductFamilyMapping"` lookup table Id assign it to the `productFamilyMappingID` variable. Create filters: `'value'` equal `oldValue` `'lookupTable.id'` equal `productFamilyMappingID` Update `"ProductFamilyMapping"` lookup table. To obtain accurate data, make use of filters.
`part-4`	Get individual field values from user `inputs`: `"productGroupOption"` - assign it to the `optionInput` variable `"discountLevelsOption"` - assign it to the `discountLevelsOption` variable `"newTargetDiscountPct"` - assign it to the `newTargetDiscountPct` variable `"newMaxDiscountPct"` - assign it to the `newMaxDiscountPct` variable Get `"Discount"` lookup table Id assign it to the `discountID` variable. Create filters: `'ProductGroup'` equal `productGroupOption` `'DiscountLevel'` equal `discountLevelsOption` `'lookupTable.id'` equal `discountID` Update `"Discount"` lookup table. To obtain accurate data, make use of filters.
`part-5`	Get individual field values from user `inputs`: `"newMinRevenue"` - assign it to the `newMinRevenue` variable `"productFamilyOption"` - assign it to the `productFamilyOption` variable `"discountLevelsOption"` - assign it to the `discountLevelsOption` variable Get `"DiscountLevelDefinition"` lookup table Id assign it to the `discountLevelDefinitionID` variable. Create filters: `'ProductFamily'` equal `productFamilyOption` `'DiscountLevel'` equal `discountLevelsOption` `'lookupTable.id'` equal `discountLevelDefinitionID` Update `"DiscountLevelDefinition"` lookup table. To obtain accurate data, make use of filters.
`part-6`	Get following tables outputs from current item: `"DiscountLevelDefinitionMatrix"` `"ProductFamilyMappingMatrix"` `"discountMatrix"` If output is null get an empty list Filter the rows in their respective tables based on the values of Map.
`part-7`	Get individual field values from user `inputs`: `"assignProductGroup"` - assign it to the `assignProductGroup` variable `"productFamilyInput"` - assign it to the `productFamilyInput` variable Get `"ProductFamilyMapping"` lookup table Id assign it to the `productFamilyMappingID` variable. Create filters: `'name'` equal `assignProductGroup` `'lookupTable.id'` equal `productFamilyMappingID` Update `"ProductFamilyMapping"` lookup table. To obtain accurate data, make use of filters. Use `discountLevelDefinitionEntries` and update `"DiscountLevelDefinition"` lookup table
`part-8`	Use `productFamilyMappingEntries` and update `"ProductFamilyMapping"` lookup table Use `discountEntries` and update `"Discount"` lookup table

Code samples

Task	Code samples

Task	Code samples
Get user inputs from current item assign it to `inputs` variable
Get individual field values from user `inputs`:
Get `"Discount"` lookup table Id assign it to the `discountID` variable.
Create filters: `'ProductGroup'` equal `oldName` `'lookupTable.id'` equal `discountID`
Update `"ProductFamilyMapping"` lookup table. To obtain accurate data, make use of filters.
Use `discountEntries` and update `"Discount"` lookup table
Get `"DiscountLevelDefinitionMatrix"` table outputs from current item
If output is null get an empty list
Filter the rows in their respective tables based on the values of Map.

Resources for Further Learning

References

Custom Forms (Reference)

Custom Forms Configuration How-To(s)

Documentation

Custom Forms

Custom Forms General Settings

Custom Forms Header Logics

Company Parameters

Groovy API

setConfigParameter

NOTE: If you have any inquiries regarding the content in this learning path, you can utilize the following online Pricefx forums: AskPricefx community or Pricefx GenAI chatbot.

Configuration Engineer Knowledge Base

Lab - Standalone Custom Form

Lab Info

User Story / Requirements

Details

Learning Outcomes

Provided resources

Acceptance Criteria

Step-by-step solution

Develop the logic and test in Studio

Pricefx Studio - Create Custom Form Type

Solution

Calculations

Saving changes to the tables

Resources for Further Learning

References

Documentation

Groovy API