/o//commerce-media/accounts/-1/images/18529250?download=true
enhanced DDL form
DXP App
The aim of the application is to enhance the capabilities of Dinamic Data List Form (DDL Form) provided by Liferay allowing the generation of a complex data entry form completely controlled by the user without the need of coding. In particular it's possible to define a sequence of DDLs and provide the possibility to list, edit, delete the data previously inserted.
Besides it is possible to configure the visibility of each metadata field based on role and/or user.
The application is composed by two portlets:
1. Asset Application: portlet that allows defining the data list and compilation sequence of the form.
2. Dynamic Data List FormCustom: portlet that allows the form compilation based on the application asset selected The aim of the application is to enhance the capabilities of Dinamic Data List Form (DDL Form) provided by Liferay allowing the generation of a complex data entry form completely controlled by the user without the need of coding. In particular it's possible to define a sequence of DDLs and provide the possibility to list, edit, delete the data previously inserted.
Besides it is possible to configure the visibility of each metadata field based on role and/or user.
The application is composed by two portlets:
1. Asset Application: portlet that allows defining the data list and compilation sequence of the form.
2. Dynamic Data List FormCustom: portlet that allows the form compilation based on the application asset selected
Besides it is possible to configure the visibility of each metadata field based on role and/or user.
The application is composed by two portlets:
1. Asset Application: portlet that allows defining the data list and compilation sequence of the form.
2. Dynamic Data List FormCustom: portlet that allows the form compilation based on the application asset selected The aim of the application is to enhance the capabilities of Dinamic Data List Form (DDL Form) provided by Liferay allowing the generation of a complex data entry form completely controlled by the user without the need of coding. In particular it's possible to define a sequence of DDLs and provide the possibility to list, edit, delete the data previously inserted.
Besides it is possible to configure the visibility of each metadata field based on role and/or user.
The application is composed by two portlets:
1. Asset Application: portlet that allows defining the data list and compilation sequence of the form.
2. Dynamic Data List FormCustom: portlet that allows the form compilation based on the application asset selected
DEVELOPER
S'ha produït un error mentre es processava la plantilla.
For "." left-hand operand: Expected a hash, but this has evaluated to a string (wrapper: f.t.SimpleScalar):
==> specifications [in template "3192443#3192485#null" at line 16, column 36]
----
FTL stack trace ("~" means nesting-related):
- Failed at: #if specifications?has_content && spe... [in template "3192443#3192485#null" at line 16, column 1]
----
1<#assign
2 channels = restClient.get("/headless-commerce-delivery-catalog/v1.0/channels")
3 channelId = ""
4/>
5
6<#list channels.items as channel>
7 <#if channel.name == "Marketplace Channel">
8 <#assign channelId = channel.id />
9 </#if>
10</#list>
11
12<#if (CPDefinition_cProductId.getData())??>
13 <#assign specifications = restClient.get("/headless-commerce-delivery-catalog/v1.0/channels/" + channelId + "/products/" + CPDefinition_cProductId.getData() + "/product-specifications") />
14</#if>
15
16<#if specifications?has_content && specifications.items?has_content>
17 <#list specifications.items as specification>
18 <#if specification.specificationKey?has_content && specification.specificationKey == "developer-name">
19 ${specification.value}
20 </#if>
21 </#list>
22</#if>
DEVELOPER
05/01/16 00:00
Published date
May 1, 2016
Published Date
05/01/16 00:00
SUPPORTED OFFERINGS
Self-Hosted, Self-Managed
Supported Versions
6.2
Resource Requirements
S'ha produït un error mentre es processava la plantilla.
For "." left-hand operand: Expected a hash, but this has evaluated to a string (wrapper: f.t.SimpleScalar):
==> specifications [in template "3192443#3192485#null" at line 17, column 36]
----
FTL stack trace ("~" means nesting-related):
- Failed at: #if specifications?has_content && spe... [in template "3192443#3192485#null" at line 17, column 1]
----
1<#assign
2 channelId=""
3 channels=restClient.get("/headless-commerce-delivery-catalog/v1.0/channels")
4 filteredSpecifications=[]
5/>
6
7<#list channels.items as channel>
8 <#if channel.name=="Marketplace Channel">
9 <#assign channelId = channel.id />
10 </#if>
11</#list>
12
13<#if (CPDefinition_cProductId.getData())??>
14 <#assign specifications = restClient.get("/headless-commerce-delivery-catalog/v1.0/channels/" + channelId + "/products/" + CPDefinition_cProductId.getData() + "/product-specifications") />
15</#if>
16
17<#if specifications?has_content && specifications.items?has_content>
18
19 <#assign
20 cpuQuantity = ""
21 memoryQuantity = ""
22 />
23
24 <#list specifications.items?sort_by("specificationKey") as specification>
25 <#if stringUtil.equals(specification.value, "cloud")>
26 <script>
27 var resourceRequirements = document.querySelector(".marketplace-resource-requirements")
28
29 resourceRequirements.classList.remove("d-none");
30 </script>
31 </#if>
32
33 <#if specification.specificationKey?has_content && (stringUtil.equals(specification.specificationKey, "cpu") || stringUtil.equals(specification.specificationKey, "ram"))>
34 <#if stringUtil.equals(specification.specificationKey, "cpu" )>
35 <#assign cpuQuantity = specification.value />
36
37 <#if cpuQuantity?has_content>
38 ${cpuQuantity}
39 <#if cpuQuantity?eval gt 1>
40 CPUS
41 </#if>
42 <#if cpuQuantity?eval lt 2>
43 CPU
44 </#if>
45 </#if>
46 </#if>
47
48 <#if stringUtil.equals(specification.specificationKey, "ram")>
49 <#assign memoryQuantity = specification.value />
50
51 <#if cpuQuantity?has_content && memoryQuantity?has_content >,</#if>
52 </#if>
53
54 <#if stringUtil.equals(specification.specificationKey, "ram")>
55 <#assign memoryQuantity = specification.value />
56
57 <#if memoryQuantity?has_content>
58 ${memoryQuantity} GB RAM
59 </#if>
60 </#if>
61 </#if>
62 </#list>
63</#if>
Edition
CE
PRICE
S'ha produït un error mentre es processava la plantilla.
For "." left-hand operand: Expected a hash, but this has evaluated to a string (wrapper: f.t.SimpleScalar):
==> specifications [in template "3192443#3192485#null" at line 16, column 36]
----
FTL stack trace ("~" means nesting-related):
- Failed at: #if specifications?has_content && spe... [in template "3192443#3192485#null" at line 16, column 1]
----
1<#assign
2 channelId=""
3 channels=restClient.get("/headless-commerce-delivery-catalog/v1.0/channels")
4 filteredSpecifications=[] />
5
6<#list channels.items as channel>
7 <#if channel.name=="Marketplace Channel">
8 <#assign channelId = channel.id />
9 </#if>
10</#list>
11
12<#if (CPDefinition_cProductId.getData())??>
13 <#assign specifications = restClient.get("/headless-commerce-delivery-catalog/v1.0/channels/" + channelId + "/products/" + CPDefinition_cProductId.getData() + "/product-specifications") />
14</#if>
15
16<#if specifications?has_content && specifications.items?has_content>
17 <#list specifications.items?sort_by("specificationKey") as specification>
18 <#if specification.specificationKey?has_content>
19 <#if stringUtil.equals(specification.specificationKey, "price-model" )>
20 <#assign priceModel = specification.value />
21 <#if priceModel?has_content>
22 ${priceModel}
23 </#if>
24 </#if>
25 </#if>
26 </#list>
27</#if>
help & support
Terms & Conditions
SHARE LINK
HTML Example
A paragraph is a self-contained unit of a discourse in writing dealing with a particular point or idea. Paragraphs are usually an expected part of formal writing, used to organize longer prose.