Custom UI component save values to properties on a page (.pyWorkPage.MyPage)
Hi Guys,
I am trying to create a custom UI component (not an auto-generated one) in pega verison 7.3
I want to persist values of input fields upon save/submit into properties on a clipboard page (single page under pyWorkPage).
What I have done:
the custom UI component gets the page as a property when I reference it in the section.
I then access the page using the following code and save it in a variable:
<pega:save name="strPropertyName" ref="$this-name" />
then construct the reference for the properties I want to set with :
<% String labelProperty = tools.getSaveValue("strPropertyName") + "$ppyLabel";%>
And so looks my inputs:
<input name="<%=labelProperty%>" value="<pega:reference name='<%=labelProperty%>' mode='text'/>" type="text">
From what I see I am confident that this is a proper setup for setting and showing property values in a custom component in pega.
The problem is that I get a SECU0001 alert, because pega does not know that this property should be allowed to be modified.
My question is:
- what are the ways to tell pega that the page I am passing in, can be legally modified (so I do not get SECU0001 s)?
- if there is no option for the previous, how can I save (when save or submit is clicked) a property to a page form a custom UI component?
Thanks!
Hi Guys,
I am trying to create a custom UI component (not an auto-generated one) in pega verison 7.3
I want to persist values of input fields upon save/submit into properties on a clipboard page (single page under pyWorkPage).
What I have done:
the custom UI component gets the page as a property when I reference it in the section.
I then access the page using the following code and save it in a variable:
<pega:save name="strPropertyName" ref="$this-name" />
then construct the reference for the properties I want to set with :
<% String labelProperty = tools.getSaveValue("strPropertyName") + "$ppyLabel";%>
And so looks my inputs:
<input name="<%=labelProperty%>" value="<pega:reference name='<%=labelProperty%>' mode='text'/>" type="text">
From what I see I am confident that this is a proper setup for setting and showing property values in a custom component in pega.
The problem is that I get a SECU0001 alert, because pega does not know that this property should be allowed to be modified.
My question is:
- what are the ways to tell pega that the page I am passing in, can be legally modified (so I do not get SECU0001 s)?
- if there is no option for the previous, how can I save (when save or submit is clicked) a property to a page form a custom UI component?
Thanks!
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Pegasystems Inc.
US
Going back to your original business requirement or use case, "I want to persist values of input fields upon save/submit into properties on a clipboard page"
This is how OOTB controls work. Is there another reason you need to create a custom control here? Can you expand on this use case/requirement or correct us, if I am misinterpreting your statement.
Saltech Consulting
HU
Thanks for your reply!
I would like to use a custom control because I want to add additional functionality to it.
I wanted to create an address autocomplete control (something like https://developers.google.com/maps/documentation/javascript/examples/places-autocomplete-addressform).
I could do it with a speciality component (custom code section). Can this be done with a custom control too?
Pegasystems Inc.
US
Got it. Yeah, it's easy enough to do an onchange, data transform, refresh to pre-populate data like that. But if the specific feature you're going after is to match that geo location logic, that is going to need custom non-auto gen code for sure.
But regarding your original question you had after trying an implementation... this article describes a little more on the alert you were asking about. https://docs-previous.pega.com/secu0001-alert-unexpected-properties-received-http-request
Saltech Consulting
HU
Thanks!
I have seen that article, and also read that this check could be disabled.
I do not think it would be a good practice, so I went with creating a speciality component (custom section) to achieve this behaviour.
If someone is interested check out the article, followed by the tutorial, I wrote about creating this custom address autocomplete user interface element:
http://saltech-consulting.com/2017/10/24/custom-ui-elements-in-pega/
https://github.com/saltech-consulting/blog/tree/master/custom_ui_component
----
Regarding the original question, I still do not know how to create a custom control that binds to more than one property, because this is prevented by the SECU check mentioned before.